<div> <font face="Arial, Helvetica, sans-serif">Hi Abir,<br>
<br>
My understanding is that With Lotus Notes, you can only receive plain email. Any links need to be sent as attachments. Is this what you did?<br>
<br>
You can also test the standard functionality with report </font><span style="">SWN_TEST_VERI0<font face="Arial, Helvetica, sans-serif">1. Please see this link for more details: http://help.sap.com/saphelp_erp2005/helpdata/en/8e/bb9f4099852e54e10000000a1550b0/content.htm<br>
<br>
I used TCode SWNCONFIG and followed the instructions in the online help - http://help.sap.com/saphelp_erp2005/helpdata/en/27/9a793426cea749b18fa409565c3dee/content.htm<br>
<br>
</font></span></div>
<div style="clear: both;">Best Regards,<br>
Ramki Maley.</div>
<div> <br>
</div>
<div> <br>
</div>
-----Original Message-----<br>
From: Abir Kundu <abir.kundu@in.ibm.com><br>
To: sap-wug@mit.edu<br>
Cc: workflow99@aol.com<br>
Sent: Mon, 17 Dec 2007 12:05 am<br>
Subject: Re:Extended Notifications: Launching SAP Inbox from Lotus Notes<br>
<br>
<div id="AOLMsgPart_0_a3b1aeee-e19e-46d1-ab68-91f24164d5b7" style="margin: 0px; font-family: Tahoma,Verdana,Arial,Sans-Serif; font-size: 12px; color: rgb(0, 0, 0); background-color: rgb(255, 255, 255);">
<pre style="font-size: 9pt;"><tt>Hi Ramki,<br>
We are also on ECC 6.0 and trying to configure the extended<br>
notification with Lotus Notes. But we are one step behind than you now. We<br>
are receiving the Notifications(emails) at the Lotus inbox, but when trying<br>
to open the email, the Lotus notes is throwing an ugly error and crashing.<br>
Can you please send me the exact configurations that you maintained for the<br>
Extended notification on your system.<br>
<br>
Thanks and Best Regards,<br>
Abir Kundu<br>
<br>
<br>
<br>
<br>
sap-wug-request@m <br>
it.edu <br>
Sent by: To <br>
sap-wug-bounces@m <a href="mailto:sap-wug@mit.edu">sap-wug@mit.edu</a> <br>
it.edu cc <br>
<br>
Subject <br>
12/14/2007 07:53 SAP-WUG Digest, Vol 37, Issue 53 <br>
PM <br>
<br>
<br>
Please respond to <br>
<a href="mailto:sap-wug@mit.edu">sap-wug@mit.edu</a> <br>
<br>
<br>
<br>
<br>
<br>
<br>
Send SAP-WUG mailing list submissions to<br>
<a href="mailto:sap-wug@mit.edu">sap-wug@mit.edu</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="http://mailman.mit.edu/mailman/listinfo/sap-wug" target="_blank">http://mailman.mit.edu/mailman/listinfo/sap-wug</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:sap-wug-request@mit.edu">sap-wug-request@mit.edu</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:sap-wug-owner@mit.edu">sap-wug-owner@mit.edu</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of SAP-WUG digest..."<br>
Today's Topics:<br>
<br>
1. Re: Help please (ENRIQUE NUNEZ) (ENRIQUE NUNEZ)<br>
2. Joe Toledo is out of the office. (<a href="mailto:Joe_Toledo@capgroup.com">Joe_Toledo@capgroup.com</a>)<br>
3. RE: UWL and USERDECSIONHANDLER (Dart, Jocelyn)<br>
4. Extended Notifications: Launching SAP Inbox from Lotus Notes<br>
(<a href="mailto:workflow99@aol.com">workflow99@aol.com</a>)<br>
5. RE: UWL and USERDECSIONHANDLER (John A Haworth)<br>
<br>
<br>
----- Message from ENRIQUE NUNEZ <<a href="mailto:enrique_nunez_a@yahoo.com">enrique_nunez_a@yahoo.com</a>> on Thu, 13 Dec<br>
2007 08:53:18 -0800 (PST) -----<br>
<br>
To: <a href="mailto:sap-wug@mit.edu">sap-wug@mit.edu</a> <br>
<br>
Subject: Re: Help please (ENRIQUE NUNEZ) <br>
<br>
<br>
<br>
Message-ID:<br>
<<a href="mailto:961917140712120703g1f8d4883q3eb13839a454ab54@mail.gmail.com">961917140712120703g1f8d4883q3eb13839a454ab54@mail.gmail.com</a>><br>
<br>
<br>
hi Johri<br>
<br>
thanks for your answer.<br>
<br>
you are right about the parameter ID, i tray to read the material number<br>
from de message field but its don have the material number<br>
<br>
the code that i used is:<br>
<br>
Call TRANSACTION MM01.<br>
Get Parameter ID MAT field material.<br>
<br>
i don't used the call transaction with message table.<br>
<br>
Regards<br>
<br>
<br>
<br>
____________________________________________________________________________________<br>
<br>
Be a better friend, newshound, and<br>
know-it-all with Yahoo! Mobile. Try it now.<br>
<a href="http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ" target="_blank">http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ</a><br>
<br>
<br>
<br>
<br>
----- Message from <a href="mailto:Joe_Toledo@capgroup.com">Joe_Toledo@capgroup.com</a> on Thu, 13 Dec 2007 11:17:54<br>
-0800 -----<br>
<br>
To: "SAP Workflow Users' Group" <<a href="mailto:sap-wug@mit.edu">sap-wug@mit.edu</a>> <br>
<br>
Subject: Joe Toledo is out of the office. <br>
<br>
<br>
<br>
<br>
I will be out of the office starting 12/13/2007 and will not return until<br>
12/14/2007.<br>
<br>
If you have any issues that require immediate attention, please contact<br>
JERA.<br>
<br>
<br>
<br>
<br>
----- Message from "Dart, Jocelyn" <<a href="mailto:jocelyn.dart@sap.com">jocelyn.dart@sap.com</a>> on Fri, 14 Dec<br>
2007 11:49:22 +0800 -----<br>
<br>
To: "SAP Workflow Users' Group" <<a href="mailto:sap-wug@mit.edu">sap-wug@mit.edu</a>>, "SAP Workflow Users' <br>
Group" <<a href="mailto:sap-wug@mit.edu">sap-wug@mit.edu</a>> <br>
<br>
Subje RE: UWL and USERDECSIONHANDLER <br>
ct: <br>
<br>
<br>
<br>
Ah... So the point of this is to make the old SAP Inbox user decision work<br>
like the cool new UWL Inbox user decision with note?<br>
<br>
Not bad!... mind you I usually just legislate "UWL only" at my sites...<br>
does make support a lot easier.<br>
Regards,<br>
Jocelyn<br>
<br>
________________________________<br>
<br>
From: <a href="mailto:sap-wug-bounces@mit.edu">sap-wug-bounces@mit.edu</a> on behalf of Griffiths, Mark<br>
Sent: Thu 13/12/2007 9:06 PM<br>
To: SAP Workflow Users' Group<br>
Subject: RE: UWL and USERDECSIONHANDLER<br>
<br>
<br>
<br>
I'm just prototyping quite a neat solution to the below issue - it is<br>
slightly non-standard but works so far.<br>
<br>
I am using the userdecision handler as standard in the UWL to force the<br>
creation of a mandatory note. Once this was working with the standard<br>
decision process object method I then began the non-standard bit:<br>
<br>
I already had a copy of 8267 for my decision, so I created a new method<br>
ZPROCESSTRIP on a subtype of DECISION mimicking the interface of the<br>
standard method. My method calls the standard PROCESS method, and then<br>
depending on the result in the method call container (e.g. 0002 for<br>
reject) I then call the SOFM CREATE method. I also handled the 'cancel'<br>
outcome.<br>
<br>
This means that my workflow now just has one decision step. When called<br>
from the UWL the attach objects is populated by the userdecision<br>
handler, when called in SAPGUI if they press reject my new method forces<br>
the SOFM create which I then bind back to the workflow.<br>
<br>
If this passes more thorough testing it could be a very neat solution to<br>
this classic problem.<br>
<br>
<br>
-----Original Message-----<br>
From: <a href="mailto:sap-wug-bounces@mit.edu">sap-wug-bounces@mit.edu</a> [<a href="mailto:sap-wug-bounces@mit.edu?">mailto:sap-wug-bounces@mit.edu</a>] On Behalf<br>
Of Dart, Jocelyn<br>
Sent: Thursday, December 13, 2007 1:08 AM<br>
To: SAP Workflow Users' Group; SAP Workflow Users' Group<br>
Subject: RE: UWL and USERDECSIONHANDLER<br>
<br>
Paul, Although that works it is a pretty lousy approach from a usability<br>
perspective. As I have pointed out before on this forum, the best<br>
approach is to use the UWL XML config to configure additional actions<br>
(buttons) to call the application used in the subsequent step and pass<br>
back an appropriate event or container element to indicate the next step<br>
can be skipped. You can also configure a button which combines the<br>
update of the user decision with the call of the next step. From a<br>
user perspective the process is then seamless although obviously there<br>
is a little additional work for the workflow developer.<br>
<br>
John, yes you can use the Updating Container handler - you haven't<br>
defined it properly if that is the complete fragment. Suggest you<br>
check the help doco and the DTD again. Also you are missing the user<br>
decision key which passes back which button was pressed to the workflow<br>
from your user decision actions?! And you seem to be trying to define 2<br>
handlers for the same action (button) - I don't think that will work -<br>
one would cancel out the other. Why don't you just create two<br>
additional decisions "Approved from UWL" and "Rejected from UWL" with<br>
their own decision key numbers?<br>
<br>
Regards,<br>
Jocelyn<br>
<br>
<br>
<br>
<br>
________________________________<br>
<br>
From: <a href="mailto:sap-wug-bounces@mit.edu">sap-wug-bounces@mit.edu</a> on behalf of<br>
<a href="mailto:Paul.Bakker@osr.treasury.qld.gov.au">Paul.Bakker@osr.treasury.qld.gov.au</a><br>
Sent: Thu 13/12/2007 9:46 AM<br>
To: SAP Workflow Users' Group<br>
Subject: RE: UWL and USERDECSIONHANDLER<br>
<br>
<br>
<br>
Bob/John,<br>
<br>
FYI, there is a way around the vexing 'UWL / Advance with Dialog' issue.<br>
<br>
If you present the UWL approval workitem as a 'backend' workitem<br>
(in other words, it appears in the portal but looks like an SBWP<br>
workitem -<br>
I believe this is the default display option),<br>
then the 'advance with dialog' setting will cause the subsequent 'reason<br>
for rejection' popup to appear immediately.<br>
<br>
The disadvantage is that this workitem may look different to all your<br>
other<br>
UWL workitems - assuming you use IViews.<br>
<br>
Apologies if I don't have the terminology right! I don't mess around<br>
much<br>
with the UWL representation of workitems...<br>
<br>
cheers<br>
Paul<br>
<br>
<br>
<br>
<br>
<br>
<br>
"Schmidt, Bob"<br>
<br>
<<a href="mailto:bschmidt@ugs.com">bschmidt@ugs.com</a><br>
<br>
><br>
To<br>
Sent by: "SAP Workflow Users' Group"<br>
<br>
sap-wug-bounces@m <<a href="mailto:sap-wug@mit.edu">sap-wug@mit.edu</a>><br>
<br>
it.edu<br>
cc<br>
<br>
<br>
<br>
Subject<br>
13/12/2007 04:53 RE: UWL and USERDECSIONHANDLER<br>
<br>
<br>
<br>
<br>
<br>
Please respond to<br>
<br>
"SAP Workflow<br>
<br>
Users' Group"<br>
<br>
<<a href="mailto:sap-wug@mit.edu">sap-wug@mit.edu</a>><br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
John,<br>
<br>
We've been able to use the backend workflow for all cases but one.<br>
<br>
The one case is when a manager is Rejecting a Business Trip. In the<br>
backend workflow, the user clicks on the Reject button in a decision<br>
step<br>
(BO-Decision, Method-Process) and then immediately following a window<br>
appears where they are expected to enter the reason(BO-SOFM,<br>
Method-Compose). These are two separate tasks in the workflow.<br>
<br>
In the UWL, I can present the approval/rejection decision along with the<br>
reason for rejection text box in one view by entering in the XML<br>
configuration an override for the decision task. However, I need to<br>
skip<br>
the subsequent step that asks for user to enter a reason for rejection.<br>
This is the oft-mentioned "Advance with Dialog" issue in UWL.<br>
<br>
By and large, the workflow without modification, has functioned just<br>
fine<br>
in the UWL.<br>
<br>
Hope this helps...<br>
<br>
Bob<br>
<br>
From: <a href="mailto:sap-wug-bounces@mit.edu">sap-wug-bounces@mit.edu</a> [<a href="mailto:sap-wug-bounces@mit.edu?">mailto:sap-wug-bounces@mit.edu</a>] On Behalf<br>
Of<br>
John A Haworth<br>
Sent: Wednesday, December 12, 2007 11:49 AM<br>
To: SAP Workflow Users' Group<br>
Subject: Re: UWL and USERDECSIONHANDLER<br>
<br>
<br>
Hi<br>
<br>
I posted a request earlier regarding Trip Approval. Your post has raised<br>
a<br>
couple of questions. We also will be using Portal and SapGui as entry<br>
points.<br>
I am familiar with the workflow process in the backend R3 system but not<br>
touched the Portal side. I was assuming the workflow developed in the<br>
backend, would be the same one used if decision were made in Portal or<br>
SAPGUI, but it sounds from your post that there are restrictions, could<br>
you<br>
explain and point me to further documentation of what these are and how<br>
I<br>
overcome them, before I start the development.<br>
<br>
Many Thanks<br>
<br>
John<br>
<br>
CSC Computer Sciences Limited<br>
Registered Office: Royal Pavilion, Wellesley Road, Aldershot, Hampshire,<br>
GU11 1PZ, UK<br>
Registered in England No: 0963578<br>
<br>
------------------------------------------------------------------------<br>
------------------------------------------------------------------------<br>
----------------------------------------------------------------<br>
<br>
This is a PRIVATE message. If you are not the intended recipient, please<br>
delete without copying and kindly advise us by e-mail of the mistake in<br>
delivery.<br>
NOTE: Regardless of content, this e-mail shall not operate to bind CSC<br>
to<br>
any order or other contract unless pursuant to explicit written<br>
agreement<br>
or government initiative expressly permitting the use of e-mail for such<br>
purpose.<br>
------------------------------------------------------------------------<br>
------------------------------------------------------------------------<br>
----------------------------------------------------------------<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
"Schmidt, Bob" <<a href="mailto:bschmidt@ugs.com">bschmidt@ugs.com</a>><br>
<br>
Sent by: <a href="mailto:sap-wug-bounces@mit.edu">sap-wug-bounces@mit.edu</a><br>
<br>
<br>
<br>
<br>
To<br>
12/12/2007 16:03 <<a href="mailto:sap-wug@mit.edu">sap-wug@mit.edu</a>><br>
<br>
<br>
cc<br>
<br>
<br>
<br>
Subject<br>
UWL and<br>
<br>
USERDECSIONHANDLER<br>
<br>
Please respond to<br>
<br>
"SAP Workflow Users' Group"<br>
<br>
<<a href="mailto:sap-wug@mit.edu">sap-wug@mit.edu</a>><br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
We are rolling out Travel Management through ESS to our users on EP 7.0<br>
and<br>
ECC 6.0. We've had our own custom workflow for approval/rejection of<br>
Travel Management expenses which has been operational through the SAPGUI<br>
for years. Because of extensive role resolution logic in the backend<br>
workflow, I'd like to utilize the same workflow regardless of whether<br>
the<br>
decisions are processed through the SAPGUI or the Portal. However, I'd<br>
have to put some decisions in the workflow to test whether an approval<br>
was<br>
done via the UWL to bypass tasks with SOFM-Compose method. It should<br>
be<br>
easy.<br>
<br>
For the Approve/Reject in the UWL, the USERDECISIONHANDLER in the XML<br>
file,<br>
has worked fine. Specifying the UserDecisionNote as mandatory has<br>
allowed<br>
me to require text entry for a rejection as well.<br>
<br>
Now, to the crux of the issue. I need to get a value back to the<br>
workflow<br>
container to indicate that the decision task was performed in the UWL.<br>
The<br>
UPDATINGCONTAINERHANDLER would seem to fit the bill nicely. Yet, I<br>
can't<br>
make the UPDATINGCONTAINERHANDLER work with the USERDECISIONHANDLER.<br>
The<br>
XML is below. Is this possible?<br>
<br>
Or, should I just can it and get a custom iView created to do what I<br>
need?<br>
We've already started to go down that path...<br>
<br>
Thanks!<br>
Bob<br>
<br>
<br>
<Actions><br>
<Action name="1" groupAction="yes" userDecision="yes"<br>
handler="UserDecisionHandler"><br>
<Descriptions default="Approve"/><br>
</Action><br>
<Action name="2" groupAction="yes" userDecision="yes"<br>
handler="UserDecisionHandler"><br>
<Properties><br>
<Property name="UserDecisionNote" value="mandatory"/><br>
<Property name="UserDecisionTitle" value="Reject<br>
Reason"/><br>
</Properties><br>
<Descriptions default="Reject"/><br>
</Action><br>
<Action name="2" userDecision="no"<br>
handler="UpdatingContainerHandler"><br>
<Properties><br>
<Property name="UWL_Executed" value="Y"/><br>
</Properties><br>
</Action><br>
</Actions>_______________________________________________<br>
SAP-WUG mailing list<br>
<a href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</a><br>
<a href="http://mailman.mit.edu/mailman/listinfo/sap-wug" target="_blank">http://mailman.mit.edu/mailman/listinfo/sap-wug</a><br>
_______________________________________________<br>
SAP-WUG mailing list<br>
<a href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</a><br>
<a href="http://mailman.mit.edu/mailman/listinfo/sap-wug" target="_blank">http://mailman.mit.edu/mailman/listinfo/sap-wug</a><br>
<br>
************************************************************************<br>
************************************************************************<br>
******<br>
<br>
Only an individual or entity who is intended to be a recipient of this<br>
e-mail may access or use the information contained in this e-mail or any<br>
of its attachments. Opinions contained in this e-mail or any of its<br>
attachments do not necessarily reflect the opinions of Queensland<br>
Treasury.<br>
<br>
The contents of this e-mail and any attachments are confidential and may<br>
be legally privileged and the subject of copyright. If you have<br>
received this e-mail in error, please notify Queensland Treasury<br>
immediately and erase all copies of the e-mail and the attachments.<br>
Queensland Treasury uses virus scanning software. However, it is not<br>
liable for viruses present in this e-mail or in any attachment.<br>
<br>
************************************************************************<br>
************************************************************************<br>
******<br>
<br>
<br>
_______________________________________________<br>
SAP-WUG mailing list<br>
<a href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</a><br>
<a href="http://mailman.mit.edu/mailman/listinfo/sap-wug" target="_blank">http://mailman.mit.edu/mailman/listinfo/sap-wug</a><br>
<br>
<br>
<br>
_______________________________________________<br>
SAP-WUG mailing list<br>
<a href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</a><br>
<a href="http://mailman.mit.edu/mailman/listinfo/sap-wug" target="_blank">http://mailman.mit.edu/mailman/listinfo/sap-wug</a><br>
<br>
_______________________________________________<br>
SAP-WUG mailing list<br>
<a href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</a><br>
<a href="http://mailman.mit.edu/mailman/listinfo/sap-wug" target="_blank">http://mailman.mit.edu/mailman/listinfo/sap-wug</a><br>
<br>
<br>
<br>
<br>
<br>
<br>
----- Message from <a href="mailto:workflow99@aol.com">workflow99@aol.com</a> on Fri, 14 Dec 2007 07:09:58 -0500<br>
-----<br>
<br>
To: <a href="mailto:sap-wug@mit.edu">sap-wug@mit.edu</a> <br>
<br>
Subject: Extended Notifications: Launching SAP Inbox from Lotus Notes <br>
<br>
<br>
<br>
Hi all,<br>
<br>
In an ECC6 system, I configured the Extended Notifications to send a<br>
notification (plain email ) for each work item to Lotus Notes with a<br>
shortcut to SAP inbox as an attachment.<br>
<br>
When I open an attachment for the first time, if I am not logged on I am<br>
prompted for the Id/Password. However thereafter for subsequent items it<br>
does not use the same session --but creates separate sessions for each work<br>
item --is this the standard behavior?.<br>
<br>
Best Regards,<br>
Ramki Maley.<br>
More new features than ever. Check out the new AOL Mail!<br>
<br>
----- Message from John A Haworth <<a href="mailto:jhoworth@csc.com">jhoworth@csc.com</a>> on Fri, 14 Dec 2007<br>
14:22:17 +0000 -----<br>
<br>
To: "SAP Workflow Users' Group" <<a href="mailto:sap-wug@mit.edu">sap-wug@mit.edu</a>> <br>
<br>
Subject: RE: UWL and USERDECSIONHANDLER <br>
<br>
<br>
<br>
<br>
Thanks for that. Where would I start with the 'overide for the decision<br>
task in UWL XML configuration'<br>
<br>
John<br>
<br>
CSC Computer Sciences Limited<br>
Registered Office: Royal Pavilion, Wellesley Road, Aldershot, Hampshire,<br>
GU11 1PZ, UK<br>
Registered in England No: 0963578<br>
<br>
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------<br>
<br>
This is a PRIVATE message. If you are not the intended recipient, please<br>
delete without copying and kindly advise us by e-mail of the mistake in<br>
delivery.<br>
NOTE: Regardless of content, this e-mail shall not operate to bind CSC to<br>
any order or other contract unless pursuant to explicit written agreement<br>
or government initiative expressly permitting the use of e-mail for such<br>
purpose.<br>
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------<br>
<br>
<br>
<br>
<br>
"Schmidt, Bob" <<a href="mailto:bschmidt@ugs.com">bschmidt@ugs.com</a>> <br>
Sent by: <a href="mailto:sap-wug-bounces@mit.edu">sap-wug-bounces@mit.edu</a> <br>
To <br>
"SAP Workflow Users' Group" <br>
12/12/2007 18:53 <<a href="mailto:sap-wug@mit.edu">sap-wug@mit.edu</a>> <br>
cc <br>
<br>
Please respond to Subject <br>
"SAP Workflow Users' Group" RE: UWL and <br>
<<a href="mailto:sap-wug@mit.edu">sap-wug@mit.edu</a>> USERDECSIONHANDLER <br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
John,<br>
<br>
We’ve been able to use the backend workflow for all cases but one.<br>
<br>
The one case is when a manager is Rejecting a Business Trip. In the<br>
backend workflow, the user clicks on the Reject button in a decision step<br>
(BO-Decision, Method-Process) and then immediately following a window<br>
appears where they are expected to enter the reason(BO-SOFM,<br>
Method-Compose). These are two separate tasks in the workflow.<br>
<br>
In the UWL, I can present the approval/rejection decision along with the<br>
reason for rejection text box in one view by entering in the XML<br>
configuration an override for the decision task. However, I need to skip<br>
the subsequent step that asks for user to enter a reason for rejection.<br>
This is the oft-mentioned “Advance with Dialog” issue in UWL.<br>
<br>
By and large, the workflow without modification, has functioned just fine<br>
in the UWL.<br>
<br>
Hope this helps…<br>
<br>
Bob<br>
<br>
From: <a href="mailto:sap-wug-bounces@mit.edu">sap-wug-bounces@mit.edu</a> [<a href="mailto:sap-wug-bounces@mit.edu?">mailto:sap-wug-bounces@mit.edu</a>] On Behalf Of<br>
John A Haworth<br>
Sent: Wednesday, December 12, 2007 11:49 AM<br>
To: SAP Workflow Users' Group<br>
Subject: Re: UWL and USERDECSIONHANDLER<br>
<br>
<br>
Hi<br>
<br>
I posted a request earlier regarding Trip Approval. Your post has raised a<br>
couple of questions. We also will be using Portal and SapGui as entry<br>
points.<br>
I am familiar with the workflow process in the backend R3 system but not<br>
touched the Portal side. I was assuming the workflow developed in the<br>
backend, would be the same one used if decision were made in Portal or<br>
SAPGUI, but it sounds from your post that there are restrictions, could you<br>
explain and point me to further documentation of what these are and how I<br>
overcome them, before I start the development.<br>
<br>
Many Thanks<br>
<br>
John<br>
<br>
CSC Computer Sciences Limited<br>
Registered Office: Royal Pavilion, Wellesley Road, Aldershot, Hampshire,<br>
GU11 1PZ, UK<br>
Registered in England No: 0963578<br>
<br>
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------<br>
<br>
This is a PRIVATE message. If you are not the intended recipient, please<br>
delete without copying and kindly advise us by e-mail of the mistake in<br>
delivery.<br>
NOTE: Regardless of content, this e-mail shall not operate to bind CSC to<br>
any order or other contract unless pursuant to explicit written agreement<br>
or government initiative expressly permitting the use of e-mail for such<br>
purpose.<br>
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------<br>
<br>
<br>
<br>
<br>
<br>
"Schmidt, Bob" <<a href="mailto:bschmidt@ugs.com">bschmidt@ugs.com</a>> <br>
Sent by: <a href="mailto:sap-wug-bounces@mit.edu">sap-wug-bounces@mit.edu</a> <br>
<br>
To <br>
12/12/2007 16:03 <<a href="mailto:sap-wug@mit.edu">sap-wug@mit.edu</a>> <br>
cc <br>
<br>
Subject <br>
UWL and <br>
USERDECSIONHANDLER <br>
Please respond to <br>
"SAP Workflow Users' Group" <br>
<<a href="mailto:sap-wug@mit.edu">sap-wug@mit.edu</a>> <br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
We are rolling out Travel Management through ESS to our users on EP 7.0 and<br>
ECC 6.0. We’ve had our own custom workflow for approval/rejection of<br>
Travel Management expenses which has been operational through the SAPGUI<br>
for years. Because of extensive role resolution logic in the backend<br>
workflow, I’d like to utilize the same workflow regardless of whether the<br>
decisions are processed through the SAPGUI or the Portal. However, I’d<br>
have to put some decisions in the workflow to test whether an approval was<br>
done via the UWL to bypass tasks with SOFM-Compose method. It should be<br>
easy.<br>
<br>
For the Approve/Reject in the UWL, the USERDECISIONHANDLER in the XML file,<br>
has worked fine. Specifying the UserDecisionNote as mandatory has allowed<br>
me to require text entry for a rejection as well.<br>
<br>
Now, to the crux of the issue. I need to get a value back to the workflow<br>
container to indicate that the decision task was performed in the UWL. The<br>
UPDATINGCONTAINERHANDLER would seem to fit the bill nicely. Yet, I can’t<br>
make the UPDATINGCONTAINERHANDLER work with the USERDECISIONHANDLER. The<br>
XML is below. Is this possible?<br>
<br>
Or, should I just can it and get a custom iView created to do what I need?<br>
We’ve already started to go down that path…<br>
<br>
Thanks!<br>
Bob<br>
<br>
<br>
<Actions><br>
<Action name="1" groupAction="yes" userDecision="yes"<br>
handler="UserDecisionHandler"><br>
<Descriptions default="Approve"/><br>
</Action><br>
<Action name="2" groupAction="yes" userDecision="yes"<br>
handler="UserDecisionHandler"><br>
<Properties><br>
<Property name="UserDecisionNote" value="mandatory"/><br>
<Property name="UserDecisionTitle" value="Reject Reason"/><br>
</Properties><br>
<Descriptions default="Reject"/><br>
</Action><br>
<Action name="2" userDecision="no"<br>
handler="UpdatingContainerHandler"><br>
<Properties><br>
<Property name="UWL_Executed" value="Y"/><br>
</Properties><br>
</Action><br>
</Actions>_______________________________________________<br>
SAP-WUG mailing list<br>
<a href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</a><br>
<a href="http://mailman.mit.edu/mailman/listinfo/sap-wug" target="_blank">http://mailman.mit.edu/mailman/listinfo/sap-wug</a><br>
_______________________________________________<br>
SAP-WUG mailing list<br>
<a href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</a><br>
<a href="http://mailman.mit.edu/mailman/listinfo/sap-wug" target="_blank">http://mailman.mit.edu/mailman/listinfo/sap-wug</a><br>
_______________________________________________<br>
SAP-WUG mailing list<br>
<a href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</a><br>
<a href="http://mailman.mit.edu/mailman/listinfo/sap-wug" target="_blank">http://mailman.mit.edu/mailman/listinfo/sap-wug</a><br>
<br>
_______________________________________________<br>
SAP-WUG mailing list<br>
<a href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</a><br>
<a href="http://mailman.mit.edu/mailman/listinfo/sap-wug" target="_blank">http://mailman.mit.edu/mailman/listinfo/sap-wug</a>
</tt></pre>
</div>
<!-- end of AOLMsgPart_0_a3b1aeee-e19e-46d1-ab68-91f24164d5b7 -->
<div class="AOLPromoFooter">
<hr style="margin-top:10px;" />
More new features than ever. Check out the new <a href="http://o.aolcdn.com/cdn.webmail.aol.com/mailtour/aol/en-us/text.htm?ncid=aolcmp00050000000003" target="_blank">AOL Mail</a>!<br/>
</div>