[LIKELY JUNK]Preventing User decision steps execution from SBWP

[Dart, Jocelyn]

Askhay - Hey that's funky!   Any chance you could send through a UWL XML
code fragment? 
 
To stop the execution of the user decision step from SBWP you will need
to implement your own equivalent (i.e. delegated subtype of )
DECISION.PROCESS method.
I would suggest the easiest approach would be to include a container
element flag that tells you if SBWP execution is possible or not.  If
not all you have to do is raise an error message if direct execution is
attempted. 
As the user decisions are overridden with a different launch mechanism
in the UWL it will naturally bypass the error message.  
This is a technique used in standard SAP provided scenarios such as HCM
Workforce Process Management which also calls Adobe forms - although
they use their own method rather than the user decision step. 
 
Regards,
Jocelyn 

________________________________

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of akshay.bhagwat at wipro.com
Sent: Friday, 26 December 2008 3:36 AM
To: sap-wug at mit.edu
Subject: [LIKELY JUNK]Preventing User decision steps execution from SBWP


Hi All,
 
We are using UWL for accessing work items. Workflow has user decision
steps , which are launched as Interactive Forms using ABAP Web Dynpro
from UWL.
This is working fine. But I wanted to know that is there anything which
we can do so that user is not able to execute User decision step from
SBWP?
 
Thanks in advance
 
Regards,
Akshay

Please do not print this email unless it is absolutely necessary. 

The information contained in this electronic message and any attachments
to this message are intended for the exclusive use of the addressee(s)
and may contain proprietary, confidential or privileged information. If
you are not the intended recipient, you should not disseminate,
distribute or copy this e-mail. Please notify the sender immediately and
destroy all copies of this message and any attachments. 

WARNING: Computer viruses can be transmitted via email. The recipient
should check this email and any attachments for the presence of viruses.
The company accepts no liability for any damage caused by any virus
transmitted by this email. 

www.wipro.com 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20090106/7e8ab3ce/attachment.htm