Many thanks for your quick and precise answer .
I understand that by Operations you mean the following already by default supported operations:
500 (get pending)
516,serial,softwareToBeInstalled1,version1,url1,sw2,ver2,url2 , …
520,serial (upload your current configuration)
521,serial,url (download configuration)
We already implemented it and performed some tests:
However, we were not finding the way to properly link an operation coming from a device to fire up an action on a different device. I have just started checking the Analytics Builder you suggested to implement this logic and seems to provide the building blocks for the functionality wanted. We will test it asap. Many thanks . Could you please point us to a full implementation link or example?
To fully understand the logic and requirements, may you please confirm that once the Operation has been published by one device, everything could be properly configured on the Analytics Builder through its web interface (no code development is required on the Cumulocity side), and the platform will be able to automatically send the notifying message (would it be also be an Operations message?) to the different IoT device, as it was previously assigned on the Analytics Builder? Would there only be code development required on the receiving device to listen and interpret the notifying/fire up message coming from Cumulocity, so the wanted action is executed by the second device?.
Thanks, best regards, Alvaro