General Task Issue
Ramki Maley
rmaley at erpworkflow.com
Tue Dec 6 11:04:43 EST 2011
Anyone know which property/setting Jocelyn is referring to? I was not
successful in finding an OSS note.
Thanks,
Ramki.
On 12/5/11 5:40 PM, Dart, Jocelyn wrote:
>
> Hi Sanjay,
>
> 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.
>
> What it does is leave the work item without an agent and the
> administrator can then find these using transaction SWI2_ADM1.
>
> Regards
>
> Jocelyn
>
> *From:*sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] *On
> Behalf Of *Rick Bakker
> *Sent:* Tuesday, 6 December 2011 7:29 AM
> *To:* SAP Workflow Users' Group
> *Subject:* Re: General Task Issue
>
> Hello,
>
> Usually you would program the agent determination method to return an
> error if it can't find an agent.
>
> You should also set up the system to automatically email the wf admin
> when there is a workflow error.
>
> regards
>
> Rick Bakker
>
> hanabi technology
>
> On Tue, Dec 6, 2011 at 12:25 AM, Nat 4 Govender
> <ngovender4 at toyota.co.za <mailto:ngovender4 at toyota.co.za>> wrote:
>
>
> Hi Sanjay,
>
>
>
> Now my questions ...
> 1. How we can stop to broadcast the workflow to all sap users
> when no user found ?
> 2. What is the best way to handle the no user situation for
> "General Task"
> 3. How we can be notified that workflow is unable to determine
> the agent ?
>
> Perform the agent determination prior to the dialog step and
> then check if there is an agent.
> 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.
>
>
>
>
> *
> Regards*
> Nat Govender
> Toyota South Africa
> IT - SAP Workflow
> Internal Ext. : 32645
> Direct Line : +27 031 910 2645 <tel:%2B27%20031%20910%202645>
> Fax : 086 607 0414
> E-mail : ngovender4 at toyota.co.za
> <mailto:ngovender4 at toyota.co.za>
> *
> If you tell the truth, you don't have to remember anything. *
>
> *Sanjay9 P <sanjay9.p at tcs.com <mailto:sanjay9.p at tcs.com>>*
> Sent by: sap-wug-bounces at mit.edu <mailto:sap-wug-bounces at mit.edu>
>
> 2011/12/05 03:14 PM
>
> Please respond to
> "SAP Workflow Users' Group" <sap-wug at mit.edu <mailto:sap-wug at mit.edu>>
>
>
>
> To
>
>
>
> "SAP Workflow Users' Group" <sap-wug at mit.edu <mailto:sap-wug at mit.edu>>
>
> cc
>
>
>
> "SAP Workflow Users' Group" <sap-wug at mit.edu <mailto:sap-wug at mit.edu>>
>
> Subject
>
>
>
> General Task Issue
>
>
>
>
>
>
>
>
>
> Hi Experts,
>
> I am using "General Task" attribute of Task Properties. Its working
> fine but it creates an embarrassing situation in PROD.
> 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.
>
> Now my questions ...
> 1. How we can stop to broadcast the workflow to all sap users when no
> user found ?
> 2. What is the best way to handle the no user situation for "General
> Task"
> 3. How we can be notified that workflow is unable to determine the
> agent ?
>
> Probable Solution :
> For Question 1:
> I have changed the workflow design. If no user found the workflow will
> bypass the dialog step.
> Is there any better solution ?
>
> We can not make "General Forwarding Allowed" as we need to maintained
> possible agents at task level.
>
>
> Thanks and regards,
> SNJY
>
>
> Sanjay Pal
> SAP Workflow Consultant
> Tata Consultancy Services
> Mailto: sanjay9.p at tcs.com <mailto:sanjay9.p at tcs.com>
> Website: http://www.tcs.com <http://www.tcs.com/>
> ____________________________________________
> Experience certainty. IT Services
> Business Solutions
> Outsourcing
> ____________________________________________
> =====-----=====-----=====
> Notice: The information contained in this e-mail
> message and/or attachments to it may contain
> confidential or privileged information. If you are
> not the intended recipient, any dissemination, use,
> review, distribution, printing or copying of the
> information contained in this e-mail message
> and/or attachments to it are strictly prohibited. If
> you have received this communication in error,
> please notify us by reply e-mail or telephone and
> immediately and permanently delete the message
> and any attachments. Thank you
>
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu <mailto:SAP-WUG at mit.edu>
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>
>
> ***** 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. *****
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu <mailto: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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20111206/75979e2f/attachment.htm
More information about the SAP-WUG
mailing list