You can set a condition for each transition. This condition determines when the transition is executed.
How do you create conditions?
You have two options for creating conditions:
Option 1: Manual entry
You enter the condition directly.
Example:
{year}-{counter.belegnr:05d}
Option 2: STAR programming language
You store the condition in the STAR programming language.
STAR expression syntax
Important information on syntax
The conditions in workflow transitions use the syntax of STAR expressions (no longer the syntax for column filters).
Advantages of the STAR syntax
You can now also use functions
Existing conditions are migrated automatically
How does the condition check work?
Scopevisio Documents performs the following steps:
Check: The system checks whether the condition applies to the archived document
Selection: The system selects the appropriate subsequent status
Accessing sub-table values
How do you access sub-table values?
You can also access sub-table values in workflow transition conditions.
Syntax
You use the same syntax as in STAR code.
Ignore mandatory field check
What is this option?
You can activate the "Ignore mandatory field check" option for each workflow action.
What does this option do?
If you activate this option:
The system prevents the mandatory field check when changing from status A to status B
The status change can also take place if mandatory fields are not filled in
When do you use this option?
You use this option if a status change should also be possible without fully completed mandatory fields.
Summary
Element | Element Description |
Input methods | Manual or STAR programming language |
Syntax | STAR expressions |
Functions | Available |
Sub-tables | Access possible with STAR syntax |
Mandatory field check | Can optionally be ignored |