on ‎2009 Jun 04 7:32 AM
We have used the BLOCK task type in our workflow to catch all runtime exceptions. I want the exception details (that gets thrown automatically by the system at runtime) to be sent as part of a notification/mail task type to our administrator.
1. How do I access these exception details in the mail task type? Is it possible to do this?
2. For what cases a runtime exception is thrown?
Is this a valid case - A non existant position specified as receiver of a notification?
Regards,
Vikrant
Request clarification before answering.
-
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I think you have to populate the exception type in a container element in the Workflow and use it accordingly.
A runtime exception can be thrown for lots of reason like locking etc.
Specifying a Non existant Position will result into error if you are using Agent Assignment in the step as Poistion will result into error in the Workflow Builder only. If you use agent assignment as Expression and then Populate position the error will be in Workflow Log.
Thanks
Arghadip
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Dear Vikrant,
Just try it out....
Exceptions are triggered using the step u201CProcess Controlu201D. Define a new step u201CProcess Controlu201D in the normal branch. Enter the step name and the outcome name. Select u201CThrow Exceptionu201D in the function. In the event name, select the exception name defined earlier .
Uncheck u201CStep not in workflow logu201D if you would like to see this step in the workflow log.
Define a mail step in the exception branch of the block (for testing purpose u2013 to ensure that this exception branch is taken, when the exception is triggered).
Regards,
Geet
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
| User | Count |
|---|---|
| 12 | |
| 9 | |
| 6 | |
| 4 | |
| 4 | |
| 4 | |
| 3 | |
| 3 | |
| 2 | |
| 2 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.