Identifying Multiple Rotes out of a User Service in LC ES

Question

Hi
I'm not sure if this is a WorkSpace or WorkBench issue so please advise if in wrong forum.
We have created a number of LC ES processes that require 2 'routes' out of the user service at a number of stages in the process.
These routes are typically to 'Approve' or 'Reject' the form where if the form is rejected it goes back to the initiator, or previouse user, if it is approve it goes to the next person in the process - think expense claim, holiday request, etc.
This works in LC ES Process management as it displays 2 buttons - one to approve one to reject, on the Flex Wrapper.
However depending on which 'route' the user selects we need to verify different elements of the form - e.g if thet approve they must sign the form, but of they reject they don't need to, also if approved we need to allow the user to select the next recipient before the form is submitted.
In LC7 this could be done by trapping the AWS_CHOICE option selected under the AWS_SUBMIT button click event or the preSubmit event of the FSUBMIT_ button - however we can find no way to do this in LC ES.
Does anyone know if there is a way to trap the button clicked at the form level in LC ES ?
Stuart Mail. xDox.

Answer 1

Many thanks to you both for the very quick and helpful responses.
We have found a kludge solution by putting a check box on the form to to indicate if they wish to approve or reject (similar to drop down idea) and use the hidden button concept Jasmin describes to validate data accordingly.
However if you do this the two Approve / Reject buttons still show on the wrapper and if the user then clicks the wrong one the workflow routing is then of course wrong for the validations and pre-submit actions that have been done at the form level - and there is no way for us to trap for this error as we can't tell which button was clicked of course :-(
If we only have one 'route' out of the user, and hide the wrapper button, and then have a Decision Point after the user to decide the route of some item in the XPath data e.g. the check box value or AWS_Action, then the Audit Trail (Tracking) does not show if the user approved or rejected the form - which makes the tracking pretty useless for the users :-(
Just an thought / question - if we hide both Wrapper Buttons, then set AWS_Action to say the same value as one of the hidden wrapper buttons, would the AWS_Action selection / value then decide which of the hidden wrapper buttons get activated (e.g. clicked) ?
Failing this does anyone know when the next release is expected and if it will include the enhancement to be able to do this ?
Stuart