Workflow exit points
In a workflow exit point you can implement custom logic. The workflow in ION contains an activity to start that custom logic. The actual implementation is performed outside ION.
Use an exit point in these situations:
- You want to use logic that is more complex than what is possible in the expression of a Set Parameter activity.
- You require data from outside the workflow that is not provided as input for the workflow.
ION starts the custom logic for your exit point through a web service. An exit point uses a web service operation. The set of workflow parameters is used as input and output for the operation. You do not have to select the required parameters in ION. All available parameters are sent to the exit point. All workflow structures are also available as input data for the exit point. You cannot use the workflow structures as output of the workflow exits.
If you deploy the web service in your own servlet container, you can implement the exit point using the technology of your choice; for example, Java or .NET. If you deploy the web service in the ION Grid, you must write the exit point logic in Java.
- Web services that are created based on the web-service WSDL from ION 10.3 or 11.0
- The new workflow definitions from 11.1 that contain structures
In such a situation you must generate the web service proxies again according to the new WSDL from ION 11.1. This is required, even if the web services do not use the structures.
This table shows the compatibility matrix:
Workflow definition version | WSDL from ION 10.3 or 11.0 | WSDL from ION 11.1 |
---|---|---|
ION 10.3 or 11.0 (no structures) | Works | Works |
ION 11.1 without structures | Works | Works |
ION 11.1 with structures | Not compatible | Works |