on 05-03-2016 5:19 PM
Dear Workflowers,
we have implemented our own exception class ZCX_BO_TEMPORARY (subclass of CX_BO_TEMPORARY) in order to set our own error message in the work item in case the exception is raised. We have followed the instructions in the excellent blog of Florin Wach; "Use Exceptions in ABAP-OO Workflow with custom text in workflow log" (Variant 2 - Using exception with message class).
The own error message is set correctly in the work item (asynchronous background step) and is available as long as the batch job SWWERRE has not completed its three tries. After the batch job SWWERRE has performed its 3rd try in order to restart the work item after error, the own error message disappears and gets replaced by the standard error message WL038 (Work item set to error following 03 failed attempts).
Any ideas on how to prevent the own error message to be replaced by the standard message generated by SWWERRE?
With best regards
Viveka Schwartz
While not an in-your-face bug, this sounds deficient enough that I would certainly raise this with OSS.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
86 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.