Launch Subscription on isConnected from thing shape level

Hi,

You don't have to duplicate RemoteThing, just create a new template that inherits from RemoteThing. Then you can achieve anything you want on isConnected directly on your new ThingTemplate.

If you want to do something on isConnected directly on the shape, it sounds complicated ... You can create the service on ThingShape and call this service in a subscription at ThingTemplate level. You just have to check that your current object has the shape on him.

Best Regards,

Guillaume

Hello,

The best would be to create a common template like MyRemoteThing, as @Rocko and @H0610 suggested.

Alternatively, you can do one of the following:

1. Create a subscription to another property, let's say "description". Export your ThingShape as XML, then modify the file by replacing Subscription > sourceProperty="description" by sourceProperty="isConnected". Import it -- et voila, you can use it in your Thing Templates. You can even still edit it in Composer without losing that manual change! Obviously, this is not documented and thus might stop working in any of the upcoming ThingWorx releases.
2. Subscribe to AnyDataChange event and check for the property name in subscription code. This will be slow.

This is just to fuel your imagination, if anything. Don't do it in a real app!

/ Constantine

Hi @H0610,

It appears that a response to this post answers your question. For the benefit of other Community Members who may have the same question, it would be great if you could designate it as the Accepted Solution.

In the event that this response did not answer your question, please post your current status so that we can continue to support.

Thanks for using the PTC Community!

Regards,

As the "isConnected" property is defined on a different TS, your TS does not know about it. So yes, you cannot subscribe to it.

To workaround this you can add a ThingStart subscription to your TS and in this subscription you can dynamically add a subscription to isConnected property:

// the ThingStart subscription code:

// todo maybe check if thing has property isConnected / is derived from RemoteThing to prevent errors before subscribing
me.AddDynamicSubscription({
	propertyName: "isConnected" /* STRING */ ,
	eventName: "DataChange" /* STRING */ ,
	thingName: me.name /* THINGNAME */ ,
	serviceName: "IsConnectedDataChangeTriggered" /* STRING */
});

// calls service "IsConnectedDataChangeTriggered" when the property changes. define service in TS. service can have normal parameters a normal subscription will have (eventData, source, sourceProperty)

To be honest I did not yet do this for isConnected but for other properties. I could imagine that it might not trigger 100% of the time as e.g. the subscription is added after isConnected has changed.

But I'm not clear if this can happen (but I assume so?). Depending on what you do in the subscription u can call it manually in the ThingStart subscription - so it is triggered for sure (but this might create logic errors when the subscription also triggers)?. Might want to check if it even happens before applying such changes.