a connector that throws an error event when it fails
a boundary catch error event that catches the error thrown by the connector
Now, when the connector fails, the boundary event will catch the error, and the task/activity will be archived, as a result of which the failed connector's exception message and stack trace will be lost from the portal (sure enough, they will have been logged in the server log file, but that is only accessible to the system administrator).
So,
Would it be somehow possible to use an Event Handler triggered by the CONNECTOR_INSTANCE_STATE_UPDATED event (or even the more general CONNECTOR_INSTANCE_UPDATED one) to catch the exception message and stack trace from the newly failed connector (before the connector is archived alongside the task/activity by the boundary event) and make it available to the portal user or administrator?
Bonitasoft empowers development teams with Bonita, the open-source and extensible platform to solve the most demanding process automation use cases. The Bonita platform accelerates delivery of complex applications with clear separation between capabilities for visual programming and for coding. Bonita integrates with existing solutions, orchestrates heterogeneous systems, and provides deep visibility into processes across the organization.