| Info |
|---|
The Workflow Import Queue supports multiple ways of conditionally modifying data based on different scenarios. This feature was introduced in 10.4.0. |
| Table of Contents |
|---|
...
ability to conditionally execute a Workflow Behavior was added in 10.4.0. |
| Table of Contents |
|---|
Overview
The ability to conditionally execute a Behavior allows administrators to simplify Workflow configuration in certain situations.
For instance, consider the scenario in which clicking a button on a Workflow should do three things:
Set a specific Attribute value
Send a notification
Execute a custom stored procedure, but only in certain circumstances
Prior to 10.4, this would need to be configured as two distinct Actions, each of which is conditionally visible or hidden based upon the “certain circumstances”. Each of the Actions would have identical configurations for the “Set an Attribute value” and “Send a notification” Behaviors, and one of the Actions would have an additional “Execute a custom procedure” Behavior.
In 10.4, this can be implemented as a single Action, where the “Execute a custom procedure” Behavior is conditionally executed. This results in less configuration duplication.
Conditional Behaviors in “Data Entry” Steps
As of 10.4, all Workflow types support Conditional Behaviors on “Data Entry” Steps.
When an Action is executed, all of the configured Behaviors are added to the “Behavior Queue”. The conditional rule is evaluated during queue processing and, if the configured rule is not met, the Behavior is skipped.
Skipped Behaviors are identified as such in the Behavior Log.
Conditional Behaviors in “Data Import” Steps
Data Import Steps are used by the Workflow Import Queue.
There are two similar, but distinct, scenarios in which Conditional Behaviors are useful in a data import context. One scenario occurs when uploading Activity Instance data, such as exam scores, and the other occurs when uploading Member Role data representing credentials or demographic data.
Although these represent different business scenarios, they are supported by the same two features:
The ability to conditionally execute Behaviors based on different criteria
...
Conditional Behaviors during Activity Instance upload
The canonical example for Activity Instance upload is exam scores: some of the rows in the uploaded file will represent “passing” scores, and others will represent “failing” scores.
...
To implement this scenario, use an “Update Workflow Instance” Behavior that is conditionally executed according to a Comparison Rule that targets an extrinsic Attribute representing the pass/fail status.
...
Conditional Behaviors during Member Role upload
Member Role upload has some unique use cases.
...