The Raise Error Activity is an activity with which the user can intentionally throw errors in the process. You can determine the following properties of the error:
The Error ID needs to be unique and will be written in the database in case this error has been thrown and ended the process.
You can choose between two error types: Business and Technical.
Technical errors are all errors that cannot be technically influenced by us, but we know that they can occur. An example of a Technical error would be failed logins due to expired credentials. The business analyst knows that this error can occur at a certain point in the process and checks for the error in the process flow to provide a meaningful error culture. In this way, errors of this type can be quickly identified and corrected by the responsible persons without dealing with long robot downtimes.
Business Errors are process limitations due to incomplete tasks or limitations of the implemented automation of special cases. An example of an incomplete task would be tickets with missing information or attachments. This task could also not be processed by humans and would require further clarification. Limitations in terms of the implemented automation can occur when, for example, the program must evaluate illegible handwriting and unstructured documents. In this case, the required information cannot be recognized. Targeted business errors provide the user and management with an overview of improvement potentials in the process flow and meaningful extensions of the process.
In a management summary in the Hyland RPA Manager (former AM Console), a brief can be created for the management over any period of time for any processes. In this summary, percentage shares of all modulations and further automation potentials become visible.
The error descriptions state the reason for the exception. It is also written into the database to provide an overview of all exceptions.