Class TaskExitVisitor

java.lang.Object
com.aquima.interactions.portal.model.process.TaskExitVisitor
All Implemented Interfaces:
IExitMappingVisitor

public final class TaskExitVisitor extends Object implements 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