In the root state machine of a generated process, transitions between states can be automatically, time triggered, or signal triggered. Time triggered and signal triggered transitions can be controlled via the Bridge Integration Platform, or the Bridge API and xUML Runtime API as described on xUML Service Interface.
Time Triggered Transitions and Settings
The xUML service implementing the process features settings to control time triggered transitions.
Setting
Description
Allowed Values
holdTime
Specify a period of time the process will reside in state Done after the process has been finished.
Alternatively, you can use the Bridge API to do this. This is described in more detail on xUML Service Interface. In short, send a GET to /services/xuml/{name}/settings to read all available settings, make your changes, and perform a PUT to write them.
Signal Triggered Transitions
The Persistent State tab of the Bridge lists all processes and their corresponding states.
Here, you can inspect the process and state details, and trigger available signals. In the screenshot above, you can see a process in Error state. You can trigger a retry by sending OrderApprovalRetry, or abort the process by sending OrderApprovalAbort.
Alternatively, you can use the xUML Runtime API to send those signals. This is described in more detail on xUML Service Interface. Regarding the example above, you could send a POST request to /pstate/classes/OrderApproval/objects/00000e8477.../signals/OrderApprovalAbort if you wanted to abort the process.