Non-Persistent Ontologies / Control Ontologies

Owned by DevPortal Editor (Unlicensed)
13/09/21
1 min read

Up until now, the concept of Ontology has represented Platform-managed Entities persisted in one of the Platform’s repositories.

In many scenarios, ontologies are used as "Control Ontologies" that allow us to trigger processes such as:

  • Triggering a Rule.

  • Execution of a Flow from the FlowEngine.

  • Execution of a DataFlow Pipeline.

  • Execution of a microservice.

  • Communication with Broker Kafka for insertion and notification.

  • (In the future) Execution of a function on FaaS support.

And there is no need to persist these ontologies that are only used to trigger this option.

For this purpose, we have created the concept of Non Persistent Ontology/Control Ontology, which will be an option of the Ontology and, when selected, the Platform will not persist this ontology but it will trigger all the processes that can be launched on the Platform after inserting an ontology.

You can create it in the Advanced Settings option:

 

Â