Flow Step Status Conditions
The main idea of this condition is to check the following:
- Process has instances, which have specified step with selected status - at least one instance, or all
- These instances match some additional Query conditions (5, see below)
To configure these conditions:
- Select condition of Flow Step Status type
Select values for the following settings:
- Process - Name of the Process which step status you want to check in conditions
- Version - Version of that Process
- Step - Step which status you want to check in conditions
- Status - Status to be checked
You can select one or several step statuses. If you select more than one status, system will check specified step for all of them and step will be considered matching conditions if it has ANY of these statuses. E.g., if user selects "In Progress" and "Pending", step will match conditions if it has Status = "In Progress" OR "Pending".
A "Not Exist" value in Status picklist means that specified step does not exist in flow instances at all.
This can be in 2 situations:
- No flow instances matching query conditions (5) exist
- Flow instances that match query conditions exist, but do not have this step
So, if user checks Flow Step Status conditions with Status = "Not Exist", system will consider these conditions matched when no existing flow instances of this process, that match query conditions, contain this step.
If user select "Not Exist" together with other step status(es), system will consider specified step matching conditions if it has ANY of these statuses. E.g., if user selects "Not Started" and "Not Exist", step will match conditions if there is no flow instances with that step at all OR they exist, but step is not started.
Note that if there are no instances matching Query conditions (5) at all, system will consider this situation like "not found proper step in requested status". This may confuse user in some cases like configuring of Validation Rules, where conditions that return true will make validation message shown and block further proceeding.
E.g., if user makes conditions with "not started" step status check, system will show validation message if there is an instance with this not started step, but will not show message if there are no instances at all. In this case user can select "Not Started" and "Not Exist" statuses together to tune validation behavior.
Logic:
- "All must" - means that selected step should have one of the selecte statuses in all process instances matching Query conditions (5)
- "At least one" - means that selected step should be in one of the specified statuses at least in one process instance
Add Query Conditions (5) to filter records.
User needs to select conditions to identify which data source records should be checked by the Flow Step Status. Since Flow Step Status can check objects other than the context object data source, user needs to narrow down records he wants to check the Step status on by providing the appropriate conditions.
Configuring of these conditions is the same as of other conditions with Query type.
0 Comments
Add your comment