Mike Pokraka wrote:
Your setup is exactly right. And your suspicions are too, you need a separate class for each outcome.
Hmm...That's too much of unnecessary work.
I find SAP's exception class implementation a bit incomplete, so I don't use it that much. For example it is lacking the capability to transfer any information back to workflow, so you cannot capture an error message in an exception outcome. So I find it better usually to return a status or a BAPI message structure and evaluate that in a subsequent condition node.
But by using a Condition, you can not display the outcome in the Result column of Workflow Log of that Activity step, can you? (unless we display the Condition step as well in the Log).
Also if the workflow is huge, too many condition steps won't look neat. May be I will do it the old way by declaring one Exception for each error and raise them.
Thanks again Mike.