Reports
Process report screen
Errors and warnings
Errors (prevent the workflow from running)
General validations performed by the report generator:
A process must have at least a beginning and an end.
A process must have one single participant in the role of requester.
There can only be one
OTHERWISE
condition in the transitions of an action.If more than one transition exists between two actions, all of the transitions must be conditions.
All process data must be used in the action parameters or in the transition conditions.
Data used in a condition must be associated to an OUT or INOUT direction action parameter if no default value is set.
Action validations performed by the report generator:
All actions must have at least one next action or END.
If an action has a transition to an end of a process, the transition of the next actions must have a condition.
An action that loops must have a condition.
For an application or a sub-process, all the required parameters of an action must be defined.
Actions that include a transition with an
OTHERWISE
condition must have another transition with a condition that is not anOTHERWISE
condition.If the action comes from a synchronization, the By the action initiator assignment method is not possible.
If the action can be launched after an exception transition, the By the action initiator assignment method is not possible.
The Automatic to the action initiator assignment method is not allowed if the participant is not a requester and if the participant of the previous action is different.
The By the action initiator assignment method is not allowed if the action is called after an exception.
Ensure that all required application parameters for an action are defined.
Ensure that all the required action parameters for a sub-process are defined
Warnings (do not prevent the workflow from running)
Action validations performed by the report generator:
It is advised to use an exception transition if actions use the following assignment methods and if the username is retrieved from process data:
Automatic to the person who handled...
Manual by the person who handled...
Automatic to the person
It is advised to use an exception transition if actions use an automatic application (web proc, web service or asynchronous web proc).
It is advised to use an exception transition if actions use a sub-process.
All process data must be used.
Ensure that default and additional parameters used as OUT types are linked with data.
Automatic applications must use an exception.
Usage
General information
Participants
Data
Actions
Action sections have sub-sections that provide information about the following:
General
Required parameters
Additional parameters
Previous action
Next actions
Notifications
Additional notifications
Last updated