Server extensibility example scenarios - HxGN SDx - Update 61 - Administration & Configuration - Hexagon

HxGN SDx Extensibility

Search by Category
Administration & Configuration
SmartPlant Foundation / SDx Version

Server extensibility enables external applications to perform tasks based upon events happening within the HxGN SDx system. The following are examples of tasks based on events:


Using the event payload, you can monitor what actions users are performing, such as create or delete.


When an event is received, the EventType property of the event payload is checked for the action of interest, such as OnCreated. If there is a match then the user value and object data is recorded.


You can listen for when a file is created and then upload a duplicate of the new file as a backup to another file store.


When an event is received, it checks for the Types array property for ISPFFolder and the EventType is OnCreated to copy to the backup file store.


You can capture the events so that you can see how often certain actions are being performed.


Store events as they are received into a database. This allows you to make queries and reports that will give you insights in how your SmartPlant Foundation or HxGN SDx system is being used.

Multiple Event Subscribers

You can have multiple event subscribers depending on whether you have setup your broker with either:

  • A topic (multicast), which gives each subscriber a copy of the event

  • A queue (anycast), which operates on a first come first served basis


You can send an email every time a type of object is created.


Inspect the Types and EventType property of the event payload as the event is received. If the properties match, then it sends an email.

Overriding Default Server Behaviour

Extensibility allows you to send OData requests back to the HxGN SDx system in reaction to events to change the data of an object.


Listen for the appropriate event. For example, the EventType is OnCreated and the Type is ISPFDesignDocVersion which sends an PATCH OData request back to the HxGN SDx system to update the object that was created.


If you have the same file in multiple locations, such as HxGN SDx, you can listen to the file update event and automatically update the file accordingly.


Look for DocVersionType and OnUpdated EventType in the event payloads. When this event is received, it makes a OData request to HxGN SDx system to locate and update the file using the relevant DocVersion client API.


You can set up custom workflow process steps to perform actions when that step of the workflow is reached.


When your custom process step is reached within your workflow, an event is sent with the name of the custom workflow process step used as the Types value. When you receive these events, you can react and perform the tasks as required.