Workflow structures
Similar to workflow parameters, workflow structures are definitions of complex data structures that can be used to pass input data into the workflow. The workflow structures cannot be used as output. A workflow structure is by default required input, so when triggering the workflow, values must be passed over for structures.
A workflow structure is a collection of levels and fields. Each level can have one or more children that are fields or sublevels. There is no limit in the degree of nesting or the number of children allowed for each level.
The fields in a structure are values that can have these data-types:
- Boolean
- Decimal
- Integer
- String
- Date
- Date and Time
Each level in a structure may be repeating an indefinite number of times; each field is single occurrence.
When starting a workflow through workflow activation policies or from document flows, use structures to map data from business documents while preserving the nested structure. When a workflow is started through a Process.Workflow BOD, structures are used to pass complex input data to workflow. This data is displayed as a nested structure in the workflow Tasks and Notifications.
Workflows that contain structures cannot be started on demand from Infor Ming.le. They also cannot be started from alerts.
In a workflow definition, structures can be used in these types of steps:
- Tasks and Notifications, including the e-mail notifications
- Tasks generated by steps of type Task Chain and Parallel Task
- Workflow exit (input only)
- Set Parameter (read only)
Workflow structures can be used in the details of Tasks and Notifications and can be sent as input to the workflow exits. With a step of type Set Parameter, data can be extracted from the structures and assigned into workflow parameters for further calculations or decisions. For details, see the "Procedures" section about specifying details for each kind of step.