on 07-23-2007 9:59 AM
Hi
I'm working in a workflow project, based on ABAP OO instead of BOR.
I have created an ABAP OO method "Handling required", with a returning parameter, based on a data element/domain with two values "Handling Required" and "Handling Not Required".
Now it would like to "convert" these values to a result parameter, using the "add returned element" in the task container. This gives me the element WIRESULT, but somehow it wont give me the two outcomes that I need.
Any suggestions / help on this?
Regards
Morten Nielsen
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Mike
Thanks for your very quick reply (This is exactly why the SDN is the greatest invention since snote and the wheel ).
Normally I'll prefer to keep my workflows as slim as possible, i order to simplify the workflow support/administration task, that is I prefer resultparameters to additional condition steps. But I guess we all have our own preferred approach.
But if ABAP OO doesn't support result parameters for workflow, a container element and a condition step will do the trick
Anyway Thanks for your input
Regards
Morten Nielsen
I agree on the simplification principle, workflows should represent mostly business logic. But then again someone may come along and add a third state of "Unknown" to your domain without your knowledge and WF falls over due to unhandled outcomes. This happened more than once (granted, it was on larger sites with many developers).
Also, this is all just based on my own tests which may have failed due to a bug. If you're on NW04s it might be worthwhile asking OSS for an official response on whether it is supposed to work... (let us know if you do)
Cheers,
Mike
User | Count |
---|---|
90 | |
10 | |
10 | |
10 | |
7 | |
7 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.