21b. Intro to the Robotic Enterprise Framework - System and Business Exception Handling
In the previous videos we've learned about how the exception handling and logging mechanisms are set up in the framework.
This video illustrates how system exception handling, business exception handling, and logging work. Furthermore, we'll see how a process responds if it encounters the maximum number of consecutive errors. Additionally, we'll see what happens if the parameter ShouldMarkJobAsFaulted is set to TRUE.
Automated processes running in production rely on the execution log to evaluate processing results and diagnose issues. We'll also learn how to check the results in Orchestrator.
Okay, so, how do we generate the exceptions?
For system exceptions, we'll use the built-in crash mechanism in UIDemo.
We'll check the Enable crash simulation option and set the error occurrence to Often. This checks that our demo app will throw a system exception when running.
We can now close the app as the settings are automatically saved and ready for use when the Robot opens it.
For Business Exceptions, we have already implemented a rule in the Process workflow. We compute the sum of the values stored in a transaction item.
And if the sum is greater than the threshold defined in the Config file, ... then we used a Throw Activity to generate a Business Rule Exception.