<font size=2 face="sans-serif">Hi All,</font>
<br>
<br><font size=2 face="sans-serif">Thank you for your valuable suggestions.</font>
<br><font size=2 face="sans-serif">I will check and let you know.</font>
<br>
<br><font size=2 face="sans-serif">Thanks and regards,</font>
<br><font size=2 face="sans-serif">SNJY</font>
<br><font size=2 face="sans-serif"><br>
Sanjay Pal<br>
SAP Workflow Consultant<br>
Tata Consultancy Services<br>
Mailto: sanjay9.p@tcs.com<br>
Website: </font><a href=http://www.tcs.com/><font size=2 face="sans-serif">http://www.tcs.com</font></a><font size=2 face="sans-serif"><br>
____________________________________________<br>
Experience certainty. IT Services<br>
Business Solutions<br>
Outsourcing<br>
____________________________________________</font>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td><font size=1 color=#5f5f5f face="sans-serif">From:</font>
<td><font size=1 face="sans-serif">gautammaini@gmail.com</font>
<tr valign=top>
<td><font size=1 color=#5f5f5f face="sans-serif">To:</font>
<td><font size=1 face="sans-serif">sap-wug@mit.edu</font>
<tr valign=top>
<td><font size=1 color=#5f5f5f face="sans-serif">Date:</font>
<td><font size=1 face="sans-serif">12/06/2011 08:28 AM</font>
<tr valign=top>
<td><font size=1 color=#5f5f5f face="sans-serif">Subject:</font>
<td><font size=1 face="sans-serif">Re: General Task Issue</font>
<tr valign=top>
<td><font size=1 color=#5f5f5f face="sans-serif">Sent by:</font>
<td><font size=1 face="sans-serif">sap-wug-bounces@mit.edu</font></table>
<br>
<hr noshade>
<br>
<br>
<br><tt><font size=2>Hi,<br>
<br>
"General Task" issue can be handled by using default agent .
You can assign them in the default rule section in the Task.<br>
<br>
The workflow initially starts agent determination at the step level evaluating
expressions etc... However if it doesn't find anyone , it evaluates default
rules... <br>
<br>
So I guess you can try this one...<br>
<br>
Regards<br>
Gautam Maini<br>
<br>
Sent on my BlackBerry® from Vodafone<br>
<br>
-----Original Message-----<br>
From: sap-wug-request@mit.edu<br>
Sender: sap-wug-bounces@mit.edu<br>
Date: Mon, 05 Dec 2011 17:40:34 <br>
To: <sap-wug@mit.edu><br>
Reply-To: sap-wug@mit.edu<br>
Subject: SAP-WUG Digest, Vol 85, Issue 11<br>
<br>
Send SAP-WUG mailing list submissions to<br>
sap-wug@mit.edu<br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
</font></tt><a href="http://mailman.mit.edu/mailman/listinfo/sap-wug"><tt><font size=2>http://mailman.mit.edu/mailman/listinfo/sap-wug</font></tt></a><tt><font size=2><br>
or, via email, send a message with subject or body 'help' to<br>
sap-wug-request@mit.edu<br>
<br>
You can reach the person managing the list at<br>
sap-wug-owner@mit.edu<br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of SAP-WUG digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Re: General Task Issue (Rick Bakker)<br>
2. RE: Status does not change from status 'New' to 'In Progress'<br>
in
UWL
[Scanned] (Dart, Jocelyn)<br>
3. RE: General Task Issue (Dart, Jocelyn)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Tue, 6 Dec 2011 07:29:02 +1100<br>
From: Rick Bakker <rbakker@gmail.com><br>
Subject: Re: General Task Issue<br>
To: "SAP Workflow Users' Group" <sap-wug@mit.edu><br>
Message-ID:<br>
<CAGSLasQrmJ+2qVR-=2GU0PTL9c=Wcd1qCekZtXVL4wrqzTsXxg@mail.gmail.com><br>
Content-Type: text/plain; charset="iso-8859-1"<br>
<br>
Hello,<br>
<br>
Usually you would program the agent determination method to return an error<br>
if it can't find an agent.<br>
You should also set up the system to automatically email the wf admin when<br>
there is a workflow error.<br>
<br>
regards<br>
Rick Bakker<br>
hanabi technology<br>
<br>
On Tue, Dec 6, 2011 at 12:25 AM, Nat 4 Govender <ngovender4@toyota.co.za>wrote:<br>
<br>
><br>
> Hi Sanjay,<br>
><br>
><br>
> Now my questions ...<br>
> 1. How we can stop to broadcast the workflow
to all sap users when<br>
> no user found ?<br>
> 2. What is the best way to handle the no
user situation for<br>
> "General Task"<br>
> 3. How we can be notified that workflow
is unable to determine the<br>
> agent ?<br>
><br>
><br>
> Perform the agent determination prior
to the dialog step and then<br>
> check if there is an agent.<br>
> If there is none then it should route
to your workflow<br>
> administrator to determine why no agent was found and then fix if
possible<br>
> and restart the agent determination process.<br>
><br>
><br>
><br>
><br>
> *<br>
> Regards*<br>
> Nat Govender<br>
> Toyota South Africa<br>
> IT - SAP Workflow<br>
> Internal Ext. : 32645<br>
> Direct Line : +27 031 910 2645<br>
> Fax : 086 607
0414<br>
> E-mail : *ngovender4@toyota.co.za*
<ngovender4@toyota.co.za><br>
> *<br>
> If you tell the truth, you don't have to remember anything. *<br>
><br>
><br>
> *Sanjay9 P <sanjay9.p@tcs.com>*<br>
> Sent by: sap-wug-bounces@mit.edu<br>
><br>
> 2011/12/05 03:14 PM<br>
> Please respond to<br>
> "SAP Workflow Users' Group" <sap-wug@mit.edu><br>
><br>
> To<br>
> "SAP Workflow Users' Group" <sap-wug@mit.edu><br>
> cc<br>
> "SAP Workflow Users' Group" <sap-wug@mit.edu><br>
> Subject<br>
> General Task Issue<br>
><br>
><br>
><br>
><br>
><br>
> Hi Experts,<br>
><br>
> I am using "General Task" attribute of Task Properties.
Its working fine<br>
> but it creates an embarrassing situation in PROD.<br>
> If no agent found then this task is broadcasted to all sap users which<br>
> must not be. A custom method is used to determine the responsible
agents.<br>
><br>
> Now my questions ...<br>
> 1. How we can stop to broadcast the workflow to all sap users when
no user<br>
> found ?<br>
> 2. What is the best way to handle the no user situation for "General
Task"<br>
> 3. How we can be notified that workflow is unable to determine the
agent ?<br>
><br>
> Probable Solution :<br>
> For Question 1:<br>
> I have changed the workflow design. If no user found the workflow
will<br>
> bypass the dialog step.<br>
> Is there any better solution ?<br>
><br>
> We can not make "General Forwarding Allowed" as we need
to maintained<br>
> possible agents at task level.<br>
><br>
><br>
> Thanks and regards,<br>
> SNJY<br>
><br>
><br>
> Sanjay Pal<br>
> SAP Workflow Consultant<br>
> Tata Consultancy Services<br>
> Mailto: sanjay9.p@tcs.com<br>
> Website: *http://www.tcs.com* <</font></tt><a href=http://www.tcs.com/><tt><font size=2>http://www.tcs.com/</font></tt></a><tt><font size=2>><br>
> ____________________________________________<br>
> Experience certainty. IT Services<br>
>
Business Solutions<br>
>
Outsourcing<br>
> ____________________________________________<br>
> =====-----=====-----=====<br>
> Notice: The information contained in this e-mail<br>
> message and/or attachments to it may contain<br>
> confidential or privileged information. If you are<br>
> not the intended recipient, any dissemination, use,<br>
> review, distribution, printing or copying of the<br>
> information contained in this e-mail message<br>
> and/or attachments to it are strictly prohibited. If<br>
> you have received this communication in error,<br>
> please notify us by reply e-mail or telephone and<br>
> immediately and permanently delete the message<br>
> and any attachments. Thank you<br>
><br>
> _______________________________________________<br>
> SAP-WUG mailing list<br>
> SAP-WUG@mit.edu<br>
> </font></tt><a href="http://mailman.mit.edu/mailman/listinfo/sap-wug"><tt><font size=2>http://mailman.mit.edu/mailman/listinfo/sap-wug</font></tt></a><tt><font size=2><br>
><br>
><br>
> ***** This e-mail is a privileged and private communication and may
be<br>
> read, copied and used only by the intended recipient(s). If you are
not an<br>
> intended recipient, please inform the sender by return e-mail with
the<br>
> subject heading "Received in error". Please then delete
the e-mail; destroy<br>
> any copies of it and do not disclose its contents to any person or
entity.<br>
> If you are not the intended recipient, note that any disclosure, copying,<br>
> distribution or any action taken or omitted to be taken in reliance
on it,<br>
> is strictly prohibited and may be unlawful. Neither the sender nor
Toyota<br>
> South Africa Motors (Pty) Ltd accepts any liability whatsoever as
a result<br>
> of the further dissemination of this e-mail. Toyota South Africa Motors<br>
> (Pty) Ltd does not guarantee that e-mail communications are secure
or<br>
> error-free, as information could be intercepted, corrupted, amended,
lost,<br>
> destroyed, arrive late or incomplete, or contain viruses. *****<br>
> _______________________________________________<br>
> SAP-WUG mailing list<br>
> SAP-WUG@mit.edu<br>
> </font></tt><a href="http://mailman.mit.edu/mailman/listinfo/sap-wug"><tt><font size=2>http://mailman.mit.edu/mailman/listinfo/sap-wug</font></tt></a><tt><font size=2><br>
><br>
><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: </font></tt><a href="http://mailman.mit.edu/pipermail/sap-wug/attachments/20111206/e77ffa17/attachment-0001.htm"><tt><font size=2>http://mailman.mit.edu/pipermail/sap-wug/attachments/20111206/e77ffa17/attachment-0001.htm</font></tt></a><tt><font size=2><br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Mon, 5 Dec 2011 23:38:23 +0100<br>
From: "Dart, Jocelyn" <jocelyn.dart@sap.com><br>
Subject: RE: Status does not change from status 'New' to 'In Progress'<br>
in
UWL
[Scanned]<br>
To: "SAP Workflow Users' Group" <sap-wug@mit.edu><br>
Message-ID:<br>
<8C507B5E0BA5114E933C3C6E2E9729E00764F25C32@DEWDFECCR01.wdf.sap.corp><br>
Content-Type: text/plain; charset="us-ascii"<br>
<br>
Hi VJ,<br>
Ok well did your BSP application change the status of the work item?<br>
To change to "In Progress" as a minimum the work item needs
to be reserved to that user.<br>
One way to do this is to use the function module SAP_WAPI_RESERVE_WORKITEM
.<br>
This will not happen automatically for BSP applications - it needs to be
coded in.<br>
Regards,<br>
Jocelyn<br>
<br>
From: sap-wug-bounces@mit.edu [</font></tt><a href="mailto:sap-wug-bounces@mit.edu"><tt><font size=2>mailto:sap-wug-bounces@mit.edu</font></tt></a><tt><font size=2>]
On Behalf Of Vijayendra Rao (Absoft)<br>
Sent: Monday, 5 December 2011 11:57 PM<br>
To: 'SAP Workflow Users' Group'<br>
Subject: Status does not change from status 'New' to 'In Progress' in UWL
[Scanned]<br>
<br>
Hi,<br>
<br>
We have an issue with the work item status changes in UWL. The work items
in our systems are linked to a BSP page. So when the user executes the
work item it opens up a BSP page. If the user opens the BSP page by executing
the work item but simply closes the BSP page without carrying out any activity
on the BSP page we were expecting that the work item will now go into 'In
Progress' status as it does when you execute the same work item via SBWP.<br>
<br>
In UWL the status is still 'New' any idea what I am missing?<br>
<br>
Regards,<br>
VJ<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: </font></tt><a href="http://mailman.mit.edu/pipermail/sap-wug/attachments/20111205/7fdf3db8/attachment-0001.htm"><tt><font size=2>http://mailman.mit.edu/pipermail/sap-wug/attachments/20111205/7fdf3db8/attachment-0001.htm</font></tt></a><tt><font size=2><br>
<br>
------------------------------<br>
<br>
Message: 3<br>
Date: Mon, 5 Dec 2011 23:40:25 +0100<br>
From: "Dart, Jocelyn" <jocelyn.dart@sap.com><br>
Subject: RE: General Task Issue<br>
To: "SAP Workflow Users' Group" <sap-wug@mit.edu><br>
Message-ID:<br>
<8C507B5E0BA5114E933C3C6E2E9729E00764F25C37@DEWDFECCR01.wdf.sap.corp><br>
Content-Type: text/plain; charset="us-ascii"<br>
<br>
Hi Sanjay,<br>
Also please consult the SAP Notes ... there is a setting in table T77S0
(one of the WFLOW settings) that automatically prevents this problem if
the agent assignment is via a rule.<br>
What it does is leave the work item without an agent and the administrator
can then find these using transaction SWI2_ADM1.<br>
Regards<br>
Jocelyn<br>
<br>
From: sap-wug-bounces@mit.edu [</font></tt><a href="mailto:sap-wug-bounces@mit.edu"><tt><font size=2>mailto:sap-wug-bounces@mit.edu</font></tt></a><tt><font size=2>]
On Behalf Of Rick Bakker<br>
Sent: Tuesday, 6 December 2011 7:29 AM<br>
To: SAP Workflow Users' Group<br>
Subject: Re: General Task Issue<br>
<br>
Hello,<br>
<br>
Usually you would program the agent determination method to return an error
if it can't find an agent.<br>
You should also set up the system to automatically email the wf admin when
there is a workflow error.<br>
<br>
regards<br>
Rick Bakker<br>
hanabi technology<br>
On Tue, Dec 6, 2011 at 12:25 AM, Nat 4 Govender <ngovender4@toyota.co.za<</font></tt><a href=mailto:ngovender4@toyota.co.za><tt><font size=2>mailto:ngovender4@toyota.co.za</font></tt></a><tt><font size=2>>>
wrote:<br>
<br>
Hi Sanjay,<br>
<br>
<br>
Now my questions ...<br>
1. How we can stop to broadcast the workflow
to all sap users when no user found ?<br>
2. What is the best way to handle the no user
situation for "General Task"<br>
3. How we can be notified that workflow is unable
to determine the agent ?<br>
<br>
Perform the agent determination prior to the
dialog step and then check if there is an agent.<br>
If there is none then it should route to your
workflow administrator to determine why no agent was found and then fix
if possible and restart the agent determination process.<br>
<br>
<br>
<br>
<br>
<br>
Regards<br>
Nat Govender<br>
Toyota South Africa<br>
IT - SAP Workflow<br>
Internal Ext. : 32645<br>
Direct Line : +27 031 910 2645<tel:%2B27%20031%20910%202645><br>
Fax : 086 607 0414<br>
E-mail : ngovender4@toyota.co.za<</font></tt><a href=mailto:ngovender4@toyota.co.za><tt><font size=2>mailto:ngovender4@toyota.co.za</font></tt></a><tt><font size=2>><br>
<br>
If you tell the truth, you don't have to remember anything.<br>
<br>
Sanjay9 P <sanjay9.p@tcs.com<</font></tt><a href=mailto:sanjay9.p@tcs.com><tt><font size=2>mailto:sanjay9.p@tcs.com</font></tt></a><tt><font size=2>>><br>
Sent by: sap-wug-bounces@mit.edu<</font></tt><a href="mailto:sap-wug-bounces@mit.edu"><tt><font size=2>mailto:sap-wug-bounces@mit.edu</font></tt></a><tt><font size=2>><br>
<br>
2011/12/05 03:14 PM<br>
Please respond to<br>
"SAP Workflow Users' Group" <sap-wug@mit.edu<</font></tt><a href="mailto:sap-wug@mit.edu"><tt><font size=2>mailto:sap-wug@mit.edu</font></tt></a><tt><font size=2>>><br>
<br>
<br>
To<br>
<br>
"SAP Workflow Users' Group" <sap-wug@mit.edu<</font></tt><a href="mailto:sap-wug@mit.edu"><tt><font size=2>mailto:sap-wug@mit.edu</font></tt></a><tt><font size=2>>><br>
<br>
cc<br>
<br>
"SAP Workflow Users' Group" <sap-wug@mit.edu<</font></tt><a href="mailto:sap-wug@mit.edu"><tt><font size=2>mailto:sap-wug@mit.edu</font></tt></a><tt><font size=2>>><br>
<br>
Subject<br>
<br>
General Task Issue<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
Hi Experts,<br>
<br>
I am using "General Task" attribute of Task Properties. Its working
fine but it creates an embarrassing situation in PROD.<br>
If no agent found then this task is broadcasted to all sap users which
must not be. A custom method is used to determine the responsible agents.<br>
<br>
Now my questions ...<br>
1. How we can stop to broadcast the workflow to all sap users when no user
found ?<br>
2. What is the best way to handle the no user situation for "General
Task"<br>
3. How we can be notified that workflow is unable to determine the agent
?<br>
<br>
Probable Solution :<br>
For Question 1:<br>
I have changed the workflow design. If no user found the workflow will
bypass the dialog step.<br>
Is there any better solution ?<br>
<br>
We can not make "General Forwarding Allowed" as we need to maintained
possible agents at task level.<br>
<br>
<br>
Thanks and regards,<br>
SNJY<br>
<br>
<br>
Sanjay Pal<br>
SAP Workflow Consultant<br>
Tata Consultancy Services<br>
Mailto: sanjay9.p@tcs.com<</font></tt><a href=mailto:sanjay9.p@tcs.com><tt><font size=2>mailto:sanjay9.p@tcs.com</font></tt></a><tt><font size=2>><br>
Website: </font></tt><a href=http://www.tcs.com/><tt><font size=2>http://www.tcs.com</font></tt></a><tt><font size=2><</font></tt><a href=http://www.tcs.com/><tt><font size=2>http://www.tcs.com/</font></tt></a><tt><font size=2>><br>
____________________________________________<br>
Experience certainty. IT Services<br>
Business Solutions<br>
Outsourcing<br>
____________________________________________<br>
=====-----=====-----=====<br>
Notice: The information contained in this e-mail<br>
message and/or attachments to it may contain<br>
confidential or privileged information. If you are<br>
not the intended recipient, any dissemination, use,<br>
review, distribution, printing or copying of the<br>
information contained in this e-mail message<br>
and/or attachments to it are strictly prohibited. If<br>
you have received this communication in error,<br>
please notify us by reply e-mail or telephone and<br>
immediately and permanently delete the message<br>
and any attachments. Thank you<br>
_______________________________________________<br>
SAP-WUG mailing list<br>
SAP-WUG@mit.edu<</font></tt><a href="mailto:SAP-WUG@mit.edu"><tt><font size=2>mailto:SAP-WUG@mit.edu</font></tt></a><tt><font size=2>><br>
</font></tt><a href="http://mailman.mit.edu/mailman/listinfo/sap-wug"><tt><font size=2>http://mailman.mit.edu/mailman/listinfo/sap-wug</font></tt></a><tt><font size=2><br>
<br>
<br>
***** This e-mail is a privileged and private communication and may be
read, copied and used only by the intended recipient(s). If you are not
an intended recipient, please inform the sender by return e-mail with the
subject heading "Received in error". Please then delete the e-mail;
destroy any copies of it and do not disclose its contents to any person
or entity. If you are not the intended recipient, note that any disclosure,
copying, distribution or any action taken or omitted to be taken in reliance
on it, is strictly prohibited and may be unlawful. Neither the sender nor
Toyota South Africa Motors (Pty) Ltd accepts any liability whatsoever as
a result of the further dissemination of this e-mail. Toyota South Africa
Motors (Pty) Ltd does not guarantee that e-mail communications are secure
or error-free, as information could be intercepted, corrupted, amended,
lost, destroyed, arrive late or incomplete, or contain viruses. *****<br>
_______________________________________________<br>
SAP-WUG mailing list<br>
SAP-WUG@mit.edu<</font></tt><a href="mailto:SAP-WUG@mit.edu"><tt><font size=2>mailto:SAP-WUG@mit.edu</font></tt></a><tt><font size=2>><br>
</font></tt><a href="http://mailman.mit.edu/mailman/listinfo/sap-wug"><tt><font size=2>http://mailman.mit.edu/mailman/listinfo/sap-wug</font></tt></a><tt><font size=2><br>
<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: </font></tt><a href="http://mailman.mit.edu/pipermail/sap-wug/attachments/20111205/d43e8ca4/attachment.htm"><tt><font size=2>http://mailman.mit.edu/pipermail/sap-wug/attachments/20111205/d43e8ca4/attachment.htm</font></tt></a><tt><font size=2><br>
<br>
------------------------------<br>
<br>
_______________________________________________<br>
SAP-WUG mailing list<br>
SAP-WUG@mit.edu<br>
</font></tt><a href="http://mailman.mit.edu/mailman/listinfo/sap-wug"><tt><font size=2>http://mailman.mit.edu/mailman/listinfo/sap-wug</font></tt></a><tt><font size=2><br>
<br>
<br>
End of SAP-WUG Digest, Vol 85, Issue 11<br>
***************************************<br>
<br>
_______________________________________________<br>
SAP-WUG mailing list<br>
SAP-WUG@mit.edu<br>
</font></tt><a href="http://mailman.mit.edu/mailman/listinfo/sap-wug"><tt><font size=2>http://mailman.mit.edu/mailman/listinfo/sap-wug</font></tt></a><tt><font size=2><br>
</font></tt>
<br>
<br>