UWL and USERDECSIONHANDLER

Dart, Jocelyn jocelyn.dart at sap.com
Thu Dec 13 22:49:22 EST 2007


Ah... So the point of this is to make the old SAP Inbox user decision work like the cool new UWL Inbox user decision with note?   
 
Not bad!... mind you I usually just legislate "UWL only" at my sites... does make support a lot easier. 
Regards,
Jocelyn 

________________________________

From: sap-wug-bounces at mit.edu on behalf of Griffiths, Mark
Sent: Thu 13/12/2007 9:06 PM
To: SAP Workflow Users' Group
Subject: RE: UWL and USERDECSIONHANDLER



I'm just prototyping quite a neat solution to the below issue - it is
slightly non-standard but works so far.

I am using the userdecision handler as standard in the UWL to force the
creation of a mandatory note.  Once this was working with the standard
decision process object method I then began the non-standard bit:

I already had a copy of 8267 for my decision, so I created a new method
ZPROCESSTRIP on a subtype of DECISION mimicking the interface of the
standard method.  My method calls the standard PROCESS method, and then
depending on the result in the method call container (e.g. 0002 for
reject) I then call the SOFM CREATE method. I also handled the 'cancel'
outcome.

This means that my workflow now just has one decision step.  When called
from the UWL the attach objects is populated by the userdecision
handler, when called in SAPGUI if they press reject my new method forces
the SOFM create which I then bind back to the workflow.

If this passes more thorough testing it could be a very neat solution to
this classic problem.


-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Dart, Jocelyn
Sent: Thursday, December 13, 2007 1:08 AM
To: SAP Workflow Users' Group; SAP Workflow Users' Group
Subject: RE: UWL and USERDECSIONHANDLER

Paul, Although that works it is a pretty lousy approach from a usability
perspective.  As I have pointed out before on this forum, the best
approach is to use the UWL XML config to configure additional actions
(buttons) to call the application used in the subsequent step and pass
back an appropriate event or container element to indicate the next step
can be skipped.   You can also configure a button which combines the
update of the user decision with the call of the next step.   From a
user perspective the process is then seamless although obviously there
is  a little additional work for the workflow developer.

John, yes you can use the Updating Container handler - you haven't
defined it properly if that is the complete fragment.   Suggest you
check the help doco and the DTD again.    Also you are missing the user
decision key which passes back which button was pressed to the workflow
from your user decision actions?! And you seem to be trying to define 2
handlers for the same action (button) - I don't think that will work -
one would cancel out the other.  Why don't you just create two
additional decisions "Approved from UWL" and "Rejected from UWL" with
their own decision key numbers?   

Regards,
Jocelyn




________________________________

From: sap-wug-bounces at mit.edu on behalf of
Paul.Bakker at osr.treasury.qld.gov.au
Sent: Thu 13/12/2007 9:46 AM
To: SAP Workflow Users' Group
Subject: RE: UWL and USERDECSIONHANDLER



Bob/John,

FYI, there is a way around the vexing 'UWL / Advance with Dialog' issue.

If you present the UWL approval workitem as a 'backend' workitem
(in other words, it appears in the portal but looks like an SBWP
workitem -
I believe this is the default display option),
then the 'advance with dialog' setting will cause the subsequent 'reason
for rejection' popup to appear immediately.

The disadvantage is that this workitem may look different to all your
other
UWL workitems - assuming you use IViews.

Apologies if I don't have the terminology right! I don't mess around
much
with the UWL representation of workitems...

cheers
Paul






             "Schmidt, Bob"

             <bschmidt at ugs.com

             >
To
             Sent by:                  "SAP Workflow Users' Group"

             sap-wug-bounces at m         <sap-wug at mit.edu>

             it.edu
cc



Subject
             13/12/2007 04:53          RE: UWL and USERDECSIONHANDLER





             Please respond to

               "SAP Workflow

               Users' Group"

             <sap-wug at mit.edu>









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




To
 12/12/2007 16:03                                     <sap-wug at mit.edu>


cc



Subject
                                                      UWL and

                                                      USERDECSIONHANDLER

             Please respond to

        "SAP Workflow Users' Group"

             <sap-wug at mit.edu>




















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
_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug

************************************************************************
************************************************************************
******

Only an individual or entity who is intended to be a recipient of this
e-mail may access or use the information contained in this e-mail or any
of its attachments.  Opinions contained in this e-mail or any of its
attachments do not necessarily reflect the opinions of Queensland
Treasury.

The contents of this e-mail and any attachments are confidential and may
be legally privileged and the subject of copyright.  If you have
received this e-mail in error, please notify Queensland Treasury
immediately and erase all copies of the e-mail and the attachments.
Queensland Treasury uses virus scanning software.  However, it is not
liable for viruses present in this e-mail or in any attachment.

************************************************************************
************************************************************************
******


_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug



_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug

_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug






More information about the SAP-WUG mailing list