In our March release we have added NRL based workflow automation. This allows you to automatically allocate, assign and label exceptions.
Defining workflow rules
You can define workflow rules by visiting the new workflow rules settings page. These will be evaluated on any exceptions present in the latest run:
We have added a number of new operators to help you write workflow rules. These include the ability to:
- Allocate the exception to a group and assign it to a user
- Allocate the exception to a group
- Set the exception status to a particular status (unreviewed, under review, pending, closed)
- Label the exception with a label
- Set the exception start date
To enable you to decide what actions you want to take on an exception, we have also added a number of operators to check information about the exception:
- what the exception's status is
- what its match status is
- who it's been allocated and assigned to
- whether it's been labelled
- what its breaking fields are
- what its age is
In addition to this, all of the usual operator information is available for workflow rules including match fields, reported fields and calculated results.
Workflow rules evaluation
Workflow rules are evaluated in order. This means that
- If several rules act on exception (e.g. several rules assign the exception to different users), actions on later rules will overwrite earlier rules.
- You can refer to earlier actions in later (e.g. if you labelled an exception in earlier rules, you can write a rule which uses that information: "if the exception is labelled, assign it to someone).
Workflow rules are evaluated after we copy the exception state over from exceptions in earlier runs (if you have auto-close of exceptions switched on). This means that you can refer to existing pending exceptions and age and base logic on this. This can be useful if you want to escalate exceptions after they reach a certain age or if you want to move items out of "pending" after they reach a certain age.