When business process steps (task) is not all line up in a straight line in the Workflow diagrams, 'Split setting' is required. There are three types of Splitting that is; 1. only one path is selected, 2. more than one route is selected, 3. all the route is selected.
Split Method
| By Task | - Split into multiple paths from a task.
- Only one path is selected.
| User decides the path.
| - User can decide a path by selecting a “button” when he/she operating a task.
- The condition names are applied to the button names. The buttons by an increment of paths are placed on the task execution screen.
|
|---|
| The path is decided according to the input data. | - Same specifications as XOR-Split.
|
| By Gateway | - Split through Gateway
- It depends on the kind of Gateway which paths are selected.
| Exclusive Gateway (XOR) 
| - Only one path is selected.
- Only the path that satisfies a condition first is selected.
(If any condition is not satisfied, the path of “default flow” will be selected.)
|
|---|
Inclusive Gateway (OR) 
| - Multiple paths are selected.
- Paths that satisfy any conditions are selected, by comparing each condition to all paths.
(If any condition is not satisfied, the path of “default flow” will be selected.)
|
Parallel Gateway (AND) 
| |
(*) default flow: the path selected when any conditions are not satisfied.
<By Task> <By Gateway>
Setting Condition Data
Components to Set
| Name | Description |
|---|
Name
(Button Name) | - It represents condition name. Condition names are shown in Process Diagrams.
- Condition names are applied to the button names on the task execution screen, when a user decides the path in “split Task”.
|
| Conditional Expression | - In “XOR Gateway” and “OR Gateway”, the condition to decide paths is represented as equation.
- Available style of condition depends on the type of data items used to judge the condition. Details are in next section.
- In setting a conditional equation, you can arrange multiple conditions with “AND conjunction”.
|
| Destination | - Destinations when the condition is satisfied or is selected the path to the destination.
- Indicates the access points in Process Diagram.
|
| Order | - The order to judge conditions in “XOR Gateway”. Judging will begin at the top condition.
|
Conditional Expressions vary according to Data Type
| Data Type | Description |
|---|
| String | Judging based on existence of any input data or on comparison with input data (e.g. contains [string of condition]). - exists
- doesn't exist
- contains [string of condition]
- starts with [string of condition]
- ends with [string of condition]
|
| Numeric | Judging based on existence of any input data or on comparison with input data (e.g. less than [numeric of condition]). - equal to [numeric of condition]
- not equal to [numeric of condition]
- less than or equal to [numeric of condition]
- less than [numeric of condition]
- greater than or equal to [numeric of condition]
- greater than [numeric of condition]
- exists
- doesn't exist
|
Select [Radio Button]
[Select Box]
[Search Select Box] | Judging based on comparison with the chosen value (e.g. equal to [choice of condition]). - equal to [choice of condition]
- not equal to [choice of condition]
※Enter 'value of Choices' in string as [arbitrary choices], when the choice is defined by 'Specify choices via HTTP' or 'Specify by string type process data'. |
Select [Check Box] | Judging based on comparison with the chosen value(s) (e.g. contains [choice of condition]). - contains [choice of condition]
- doesn't contain [choice of condition]
※Enter 'value of Choices' in string as [arbitrary choices], when the choice is defined by 'Specify choices via HTTP' or 'Specify by string type process data'. |
Date DateTime User | Judging based on existence of any input data. |
| File | Judging based on existence of any input data or on comparison with strings of file name (e.g. contains [string of condition]). - exists
- doesn't exist
- contains [string of condition] in file name
|
| Discussion | Judging based on existence of any input data or on comparison with input data (e.g. contains [string of condition]). - exists
- doesn't exist
- contains [string of condition]
|
