Open ChrisAtECLIPS opened 8 months ago
Hi,
We are internally discussing to have built API's for assets/modes/properties. Once the API is available we would support any CRUD operation on these objects. Currently we can reverse engineer and use inventory API to create these objects. But once the API is available we would recommed to use the API instead of any custom implementation and usage of the domain data model.
I'm assuming we could create, update, delete Asset hierarchy/models etc using the Managed Objects API. Is that correct?
Is there any documentation for JSON schema other than reverse engineering it from the sample https://github.com/SoftwareAG/cumulocity-digital-twin-manager/blob/main/samples/sample-asset-models-for-vaccum-factory or exported models
We'd like all of our changes in Cumulocity to be scriptable.