Starting a workflow
This table shows methods to start workflows:
| Starting method | Description |
|---|---|
| Activation policies | Workflow instances can be started through Workflow Activation Policies. Activation policies can be compared with event monitors; they react on Sync documents and trigger workflow execution based on rules on data from these documents. The workflow response is sent back as a Process document message.
See Activation policies. |
| Workflow schedules | You can create a workflow schedule to start a workflow instance at regular intervals of
time. You can specify constant values for the workflow input parameters.
The workflow output parameters are ignored. Workflows that contain
structures cannot be started by a workflow schedule. See Workflow schedules. |
| Workflow activity in document flow | A workflow can be linked to an activity in a document flow. In that case, when a document arrives at this activity, the workflow is started. Data from the document is used as input for the workflow. When the workflow is completed, the output of the workflow is added to the document, and the document flow continues. If there is no next activity in the flow then the workflow output is ignored. |
| Process workflow | Workflow instances can be started by sending a Process Workflow Document directly to the Workflow component in ION. |
| Start Workflow from Alert | A workflow can be started by a user from an alert the user received. The workflow definition to be started and the workflow input parameters are defined in the monitor that generated the alert. |
| Start Workflow activity in a workflow | You can start a workflow from another workflow. You can start the workflow synchronously and wait for its results, or asynchronously and continue with the current flow. |
| Start Workflows homepage widget | A workflow can be started manually by a business user who has the
required workflow authorizations. For details about starting a workflow manually, see Workflow authorizations and the Infor Ming.le User Guide. |
| Start workflow from API | From version 12.0.34, the /workflow/start API method
has been added to the endpoint process/application in the ION Services suite that is exposed
in API Gateway. For technical details, see the
endpoint swagger documentation. |
Activation policies and workflow activities in a document flow are comparable. The workflow is triggered by any type of document and any type of connection point.
Any type of documents are:
ExpenseReportSalesOrderPlanningSchedule
Any type of connection points are:
- Application
- Database
- Web service
In both activation methods, also attributes from the document are mapped to the input parameters of the workflow. The output parameters of the workflow are mapped to attributes of the document again.
This table shows the differences between these two activation methods:
| Workflow Activity | Activation Policy |
|---|---|
| Modeled in the context of a document flow. Only matching BODs from the preceding step in the flow are used in the workflow activity. | The routing of BODs to the activation policy is not explicitly modeled. A matching document that enters ION from any connection point triggers the activation policy. |
| Unconditional. Note that filters or content-based routing can be used in the document flow. | The specified rule and conditions are evaluated. |
| When the workflow is completed, the message that triggered the workflow is enriched with the outcome of the workflow and sent to the next activity in the flow. | When the workflow is completed, to communicate the outcome of the workflow, a Process message is sent back to the connection point that published the Sync message. |
| The workflow can only be canceled by an administrator through ION. | An additional activation policy can be used to automatically cancel the workflow if it is no longer relevant. |
Multiple ways of starting a workflow can be combined for a single workflow
definition. For example, a workflow that has an activation policy can also be started
using a ProcessWorkflow BOD.