advance with dailog

Dart, Jocelyn jocelyn.dart at sap.com
Wed Sep 5 02:34:37 EDT 2007


Hi Yogesh, 
 
My suggestion is to change the behaviour on the UWL side for the "Change
document" answer to launch the edit document transaction directly
instead of returning the answer to the user decision step itself.  You
should only need to add a terminating event on the workflow side so that
after updating the document the user decision step is completed.  
 
Actually there is no need in this scenario to include the edit document
step in your workflow - unless you are supporting both the UWL and the
SAP Business Workplace inbox, in which case you would need to use the
terminating event to end both the decision step and the edit document
step. 
 
The delete step would use the normal user decision behaviour. 
 

Regards, 
Jocelyn Dart 
Senior Consultant 
SAP Australia Pty Ltd. 
Level 1/168 Walker St. 
North Sydney 
NSW, 2060 
Australia 
T   +61 412 390 267 
M   + 61 412 390 267 
E   jocelyn.dart at sap.com 
http://www.sap.com <http://www.sap.com/>  

The information contained in or attached to this electronic transmission
is confidential and may be legally privileged. It is intended only for
the person or entity to which it is addressed. If you are not the
intended recipient, you are hereby notified that any distribution,
copying, review, retransmission, dissemination or other use of this
electronic transmission or the information contained in it is strictly
prohibited. If you have received this electronic transmission in error,
please immediately contact the sender to arrange for the return of the
original documents. 

Electronic transmission cannot be guaranteed to be secure and
accordingly, the sender does not accept liability for any such data
corruption, interception, unauthorized amendment, viruses, delays or the
consequences thereof.

Any views expressed in this electronic transmission are those of the
individual sender, except where the message states otherwise and the
sender is authorized to state them to be the views of SAP AG or any of
its subsidiaries. SAP AG, its subsidiaries, and their directors,
officers and employees make no representation nor accept any liability
for the accuracy or completeness of the views or information contained
herein. Please be aware that the furnishing of any pricing information/
business proposal herein is indicative only, is subject to change and
shall not be construed as an offer or as constituting a binding
agreement on the part of SAP AG or any of its subsidiaries to enter into
any relationship, unless otherwise expressly stated. 

 

________________________________

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Yogesh Patil
Sent: Saturday, 01 September 2007 6:39 AM
To: SAP Workflow Users' Group
Subject: RE: advance with dailog


Jocelyn,
            Here is  what i am doing in my workflow :
 
   1) a decison box with  two buttons :
            i) change and re-submit document
            ii) delete document
 
This decison goes to the requestor when the approver rejects the
document.
 
when the user (requestor) selects change and re-submit ,the next dailog
workitem (advance with dailog step)  is executed which opens the
standard sap transaction to edit the document.
 
and when user selects delete , a background step is called which deletes
the document.
 
it works perfectly in SAP but the same does not happen in UWL as i read
the note which says advance with dailog not possible in Portal/UWL.
 
is the below solution you suggested much on the UWL /portal side or on
the workflow side..
 
 
any suggestions?
 
Thanks,
 
 
 Yogesh Patil| SAP Workflow Consultant | Fujitsu Consulting  |Cell (302)
384-2858 | yogesh.patil at us.fujitsu.com
<mailto:yogesh.patil at us.fujitsu.com>  | yogesh.patil at jm.com
<mailto:yogesh.patil at jm.com> 

________________________________

From: sap-wug-bounces at mit.edu on behalf of Dart, Jocelyn
Sent: Thu 8/30/2007 2:20 AM
To: SAP Workflow Users' Group
Subject: RE: advance with dailog


Don't do it Yogesh!  It's not worth the losses in features and
functionality. 
 
BUT... there is a BETTER WAY.... 
 
Using UWL XML Configuration you can configure additional buttons for
your user decision using the <Action> tag. 
You can also adjust the decision actions however you want. 
So you can combine your user decision and follow on transaction into one
step.  This is only possible with the UWL!
 
So this way you can e.g. Have buttons something like the following:
 
a) Approve only - updates the user decision step with the chosen key
b) Approve and Change PO - takes you straight into the SAP transaction. 
 
To complete the circuit you need to of course be able to recognise that
your user has gone straight to the SAP transaction and that the answer
to the decision step is implied. 
 
You could do this by listening for an appropriate terminating event or
by wrapping your transaction call in something else such as a function
module or a wrapper transaction - but a terminating event is easier.
i.e. This way you have a user decision plus a wait for terminating
event, rather than a user decision plus a call transaction step. 
 

Regards, 
Jocelyn Dart 
Senior Consultant 
SAP Australia Pty Ltd. 
Level 1/168 Walker St. 
North Sydney 
NSW, 2060 
Australia 
T   +61 412 390 267 
M   + 61 412 390 267 
E   jocelyn.dart at sap.com 
http://www.sap.com <http://www.sap.com/>  

The information contained in or attached to this electronic transmission
is confidential and may be legally privileged. It is intended only for
the person or entity to which it is addressed. If you are not the
intended recipient, you are hereby notified that any distribution,
copying, review, retransmission, dissemination or other use of this
electronic transmission or the information contained in it is strictly
prohibited. If you have received this electronic transmission in error,
please immediately contact the sender to arrange for the return of the
original documents. 

Electronic transmission cannot be guaranteed to be secure and
accordingly, the sender does not accept liability for any such data
corruption, interception, unauthorized amendment, viruses, delays or the
consequences thereof.

Any views expressed in this electronic transmission are those of the
individual sender, except where the message states otherwise and the
sender is authorized to state them to be the views of SAP AG or any of
its subsidiaries. SAP AG, its subsidiaries, and their directors,
officers and employees make no representation nor accept any liability
for the accuracy or completeness of the views or information contained
herein. Please be aware that the furnishing of any pricing information/
business proposal herein is indicative only, is subject to change and
shall not be construed as an offer or as constituting a binding
agreement on the part of SAP AG or any of its subsidiaries to enter into
any relationship, unless otherwise expressly stated. 

 

________________________________

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Yogesh Patil
Sent: Thursday, 30 August 2007 3:21 PM
To: SAP-WUG at mit.edu
Subject: advance with dailog


Hi,
 
can anyone let me know how does advance with dailog work in UWL /portal
i have a decision work item and a standard sap transaction workitem in
advance with dailog...it works fine in SAP GUI but when i try to do the
same in  UWL/portal there is  delay...does enabling the decision box as
a webtransaction solve this problem in UWL/portal.any inputs on this is
appreciated.
 
Thanks!
Yogesh
 
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20070905/3e6f8bd1/attachment.htm


More information about the SAP-WUG mailing list