Workflow Service Plugins(3.1)
- Jenni Wallin
A  workflow service executes in the background of a realtime workflow and shares the same life cycle as the workflow. The workflow service has access to the MIM tree and can thereby monitor workflow execution. A workflow service can not route any data into workflow. For general concepts, see Agent Plugins(3.1).
A workflow service is defined by inserting a class that extends the DRWorkflowServiceInspectable class into the code server. The server will then instantiate the class and extract the needed information about the workflow service.
The classes should be named as follows:
| Class | Description |
|---|---|
| The class holds the configuration data for the workflow service. It extends the class |
| This is the workflow service definition class that contains references to the user interface and executable implementations of the workflow service, as well as other information. This class must extend |
| This is the class responsible for the actual execution that implements the workflow service's runtime logic. The class should extend: |
| The workflow service user interface dialog, used to collect and display the template configuration data for the agent. It is defined in a class extending |