UWL and USERDECSIONHANDLER

[Schmidt, Bob]

John,

 

We’ve been able to use the backend workflow for all cases but one.  

 

The one case is when a manager is Rejecting a Business Trip.  In the backend workflow, the user clicks on the Reject button in a decision step (BO-Decision, Method-Process) and then immediately following a window appears where they are expected to enter the reason(BO-SOFM, Method-Compose).  These are two separate tasks in the workflow.  

 

In the UWL, I can present the approval/rejection decision along with the reason for rejection text box in one view by entering in the XML configuration an override for the decision task.  However, I need to skip the subsequent step that asks for user to enter a reason for rejection.  This is the oft-mentioned “Advance with Dialog” issue in UWL.



By and large, the workflow without modification, has functioned just fine in the UWL.

 

Hope this helps…

 

Bob

 

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of John A Haworth
Sent: Wednesday, December 12, 2007 11:49 AM
To: SAP Workflow Users' Group
Subject: Re: UWL and USERDECSIONHANDLER

 


Hi 

I posted a request earlier regarding Trip Approval. Your post has raised a couple of questions. We also will be using Portal and SapGui as entry points. 
I am familiar with the workflow process in the backend R3 system but not touched the Portal side. I was assuming the workflow developed in the backend, would be the same one used if decision were made in Portal or SAPGUI, but it sounds from your post that there are restrictions, could you explain and point me to further documentation of what these are and how I overcome them, before I start the development. 

Many Thanks 

John

CSC Computer Sciences Limited
Registered Office: Royal Pavilion, Wellesley Road, Aldershot, Hampshire, GU11 1PZ, UK
Registered in England No: 0963578

----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
This is a PRIVATE message. If you are not the intended recipient, please delete without copying and kindly advise us by e-mail of the mistake in delivery. 
NOTE: Regardless of content, this e-mail shall not operate to bind CSC to any order or other contract unless pursuant to explicit written agreement or government initiative expressly permitting the use of e-mail for such purpose.
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------




"Schmidt, Bob" <bschmidt at ugs.com> 
Sent by: sap-wug-bounces at mit.edu 

12/12/2007 16:03 

Please respond to
"SAP Workflow Users' Group" <sap-wug at mit.edu>

To

<sap-wug at mit.edu> 

cc

	
Subject

UWL and USERDECSIONHANDLER

 

		




We are rolling out Travel Management through ESS to our users on EP 7.0 and ECC 6.0.  We’ve had our own custom workflow for approval/rejection of Travel Management expenses which has been operational through the SAPGUI for years.  Because of extensive role resolution logic in the backend workflow, I’d like to utilize the same workflow regardless of whether the decisions are processed through the SAPGUI or the Portal.  However, I’d have to put some decisions in the workflow to test whether an approval was done via the UWL to bypass tasks with SOFM-Compose method.   It should be easy. 
  
For the Approve/Reject in the UWL, the USERDECISIONHANDLER in the XML file, has worked fine.  Specifying the UserDecisionNote as mandatory has allowed me to require text entry for a rejection as well.     
  
Now, to the crux of the issue.  I need to get a value back to the workflow container to indicate that the decision task was performed in the UWL.  The UPDATINGCONTAINERHANDLER would seem to fit the bill nicely.  Yet, I can’t make the  UPDATINGCONTAINERHANDLER work with the USERDECISIONHANDLER.  The XML is below.  Is this possible? 
  
Or, should I just can it and get a custom iView created to do what I need?  We’ve already started to go down that path… 
  
Thanks! 
Bob 
  
  
      <Actions> 
         <Action name="1" groupAction="yes" userDecision="yes" handler="UserDecisionHandler"> 
           <Descriptions default="Approve"/> 
         </Action> 
         <Action name="2" groupAction="yes" userDecision="yes" handler="UserDecisionHandler"> 
           <Properties> 
                <Property name="UserDecisionNote" value="mandatory"/> 
                <Property name="UserDecisionTitle" value="Reject Reason"/> 
           </Properties> 
           <Descriptions default="Reject"/> 
         </Action> 
         <Action name="2" userDecision="no" handler="UpdatingContainerHandler"> 
           <Properties> 
                <Property name="UWL_Executed" value="Y"/> 
           </Properties> 
         </Action> 
      </Actions>_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug

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