Purpose of closure control

Closure Control determines the rules when a BPEM Case can or cannot be closed. When an agent attempts to close the case, the rule will be assessed to determine if the case can be closed.
If the condition has not been met, the case cannot be closed and the user will be prompted with an error message. If the condition has been satisfied, the case will close as expected.

A batch job will be made available for the business to process as per their requirements. This uses the same rules and checks the BPEM cases. Again determining if the condition has not been met, no changes will be made to the cases. If the condition is satisfied, the cases will be mass completed. The results of the job can be viewed in a report providing full visibility of what has been mass closed or untouched.

The rules can be enforced either as a warning or an error. Check with a warning means the the user will receive a pop up message and this can be overridden. However, check with error is a hard stop and will prevent the case from being closed.

For example you may wish to use a check with error if under no circumstances should a case be closed if the condition is not met i.e. if a user is attempting to complete a BPEM case for an implausible reading the rule to be enforced is if an implausible reading has not been reversed or released prevent the closure of the case. However, you may want a user to check if a bill block has been removed. In this instance you can use the check with warning to prompt the user to check for a bill block.

Feedback

Was this helpful?

Yes No
You indicated this topic was not helpful to you ...
Could you please leave a comment telling us why? Thank you!
Thanks for your feedback.

Post your comment on this topic.

Please do not use this for support questions.
For customer support, please contact us here.

Post Comment