How to combine Exception Rules and Requires Approval rules together in EP5
If there is a case where a client would like to combine an exception rule to a transaction type, say for a non-billable number, but still needs to have the transaction amount over a certain value approved first before it exports to billing, both rules can be used together.
In this example, the client would like any transaction assigned to matter 999999 marked as an exception, but also wants any postage transaction over $20.00 approved first. Therefore, the transaction should first have to be corrected by the end user (to an appropriate matter), then the transaction needs to be approved by a manager (for being over the $20 threshold).
- If there is an exception rule for the matter 999999 under ANY TYPE transaction, you need to remove it.
- Then create the exception rule under EACH transaction type, using a different name for each instance, i.e. Fax Exception 999999, Copy Exception 999999, etc.
- Now, under the transaction type that requires approval, highlight the new exception rule and move it to Priority 1. Then set the Requires Approval rule to Priority 2 or lower.
- What will happen now is that any Postage transaction with matter 999999 and over $20.00 will first be marked as an Exception and have to be corrected to a valid matter number. It will then move from Exceptions to Requires Approval and need to be approved to Valid by a manager before it can be exported.