Persist Logged Exceptions to Database

When the workflow is triggered or when the user submits the activity, or when the workflow engine sends an alert about an activity, the action may fail and thus also the workflow. It becomes necessary for the users to understand the main cause for the failure of the workflow so that they can modify/handle it and thus improve the process life cycle.

In the previous version of the AVEVA Work Tasks product, exceptions were stored in the log file, logged to the Event Viewer and sending an email based on the configuration. However, to troubleshoot any issue, it was more difficult for users to track the exact exception message, based on the Execution ID (say).

To help the users to trace the exact exception message, all the exceptions and warnings can be persisted in the database. So, the users can now see all the exceptions occurred for that workflow by selecting the "View Exceptions" from the workflow item context menu. This pops up a window which lists all the exceptions occurred for that particular workflow.