Generic exception handler in ccBPM

[Former Member]

All,

we have a ccBPM process which has multiple steps in it. We have defined some exceptions based on some business rules (like if the status return from a system is -1 etc). And we have exception handlers for these scenarios, that provide a clean end and status to the teams on the execution of the ccBPM.

How do we handle errors that come from other places (like a mapping exception or a network failure) - is there a way to handle all the unhandled errors through a generic exception branch/handler. (something like last catch block in a try..catch)

Thanks.

[henrique_pinto · Accepted solution]

you have to explictely define exception for all blocks in which you want to handle them (send and transformation steps).

Also, you cant handle different system errors. For each step, the system error is always considered as the same (no matter the reason), thus refering to a single exception handler. For application errors (in send steps), in the other hand, you can have several fault messages, each one refering to a different exception handler.

Regards,

Henrique.