Class TaskExitVisitor
java.lang.Object
com.aquima.interactions.portal.model.process.TaskExitVisitor
- All Implemented Interfaces:
IExitMappingVisitor
This class initializes and validates the mapping between flow exits and task exits.
The following rules apply when mapping flow exits to task exits:
- If the task has multiple continue exits, at least one continue task exit needs to be mapped.
- If the task has multiple continue exits, any unmapped flow exit will be treated as an abort.
- If the task has only one continue exit, all flow complete exits will map to this one.
- The event of the task will determine the action (abort of continue), regardless of the event type of the flow.
- Each flow exit may be mapped to exactly one task exit.
- Not every task exit needs to be mapped to a flow exit.
- If the task has multiple continue exits, each flow exit must have a name (regardless of type).
- Since:
- 7.1
- Author:
- O. Kerpershoek
-
Method Summary
Modifier and TypeMethodDescriptionprocess
(ITaskMappingDS datasource, IProcessTaskDefinition taskDef, FlowNode flow) void
This method should be invoked for each exit of the flow to map it to one of the exits of the task.
-
Method Details
-
process
protected static Map<String,TaskExit> process(ITaskMappingDS datasource, IProcessTaskDefinition taskDef, FlowNode flow) -
register
Description copied from interface:IExitMappingVisitor
This method should be invoked for each exit of the flow to map it to one of the exits of the task.- Specified by:
register
in interfaceIExitMappingVisitor
- Parameters:
flowExit
- The name of the flow exit.taskExitName
- The name of the task exit.
-