Skip to content

Event Sub Process Activity

The Event Sub Process activity enables the creation of event-driven sub-processes within a larger workflow. It activates in response to various events, such as message, error, signal, timer, or compensation events. The system establishes a subscription to the start event when its hosting scope is created and removes it upon scope termination.

Field Description Requirement
Exclusive Configures the sub-process to process jobs sequentially when triggered by a specific process instance. Optional
Execution Listeners Defines a collection of listeners that trigger at the start and end of the activity's execution. Optional

Action Types & Examples

Start Event

  • Format: string
  • Example Result: "start"

End Event

  • Format: string
  • Example Result: "end"

Take Event

  • Format: string
  • Example Result: "take"

Implementation Examples

Field Setup - Exclusive: true - Execution Listeners: - Event: start - Script: log.info("Workflow process started."); - Event: take - Script: data.update("transition_count", data.get("transition_count") + 1); - Event: end - Script: notification.send("Process finished successfully.");

Execution Parameters - Event Name: messageEvent_OrderReceived - Payload: { "orderId": "12345", "customer": "Acme Corp" } - Correlation Key: orderId_12345

Technical Notes

The Event Sub Process activity can be added at both the main process level and within any sub-process. The system establishes a subscription to the activity's start event upon the creation of its hosting scope (process instance or sub-process). This subscription is automatically removed when the hosting scope terminates.