Work item sent to multiple workflow inboxes after deadline

Deanna Wong deanna.wong at alcatel.com
Thu Sep 15 09:23:43 EDT 2005


Thank you all for your help - unfortunately, we are still at 4.6C so we will
have to go with Jeffrey's suggestion.  But I will definitely keep yours in
my back pocket when we upgrade.
 
  _____  

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of
Dart, Jocelyn
Sent: Thursday, September 15, 2005 3:27 AM
To: SAP Workflow Users' Group
Subject: RE: Work item sent to multiple workflow inboxes after deadline


Hi Deanna,
Yes Jeffrey's suggestion will work fine. 
 
But if you are on a Basis 6.20 (e.g. R/3 4.7 or above) then there's an even
easier/better way:
 
* In the basic data (look for the "hat" icon in the workflow builder) you
can set up an event for the whole workflow, e.g. "updateagents" - mark it as
having the effect "re-evaluate rules on active work items"
 
* Before your step, save the original agent into a multiline container
element of type wfsyst-agent (or similar)
 
* In your step, assign the agents of your step as an expression pointing to
your multiline container element
 
* When the deadline occurs, raise a deadline event, e.g. "Latest end
reached" and in the deadline path, add your new agent to the multiline
container element, then fire off your "update agents" event. 
 
Very, very effective, quite easy, and has exactly the affect you are after -
plus you keep a more accurate record of the time taken to action the work
item because you still have the original work item and therefore the
original work item creation date/time.  
 

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
Jeff Rappaport
Sent: Thursday, 15 September 2005 2:57 AM
To: sap-wug at mit.edu
Subject: Re: Work item sent to multiple workflow inboxes after deadline



Deanna,

    You were on the right track with Option 2, but after the DM, have a New
work item go to the Mgr & Mgr's Boss. A question would be does the Boss need
to actually execute this item, or do they just need to be notified? If so,
you can keep the work item in the Mgr's inbox & just send a message to the
Boss. Hope that helps.

-- 
Jeffrey A. Rappaport
Business Workflow, LLC
www.Business-Workflow.com


Quoting Deanna Wong:

> Hi:
>
> I hope you can help.
>
> We currently have a time approval workflow set-up to run as follows:
>
> 1. Employee submits time and the workflow sents a work item to the
> employee's manager for approval.
> 2. After 3 days, the workflow removes the work item from the employee's
> manager's workflow inbox and sends a new work item to the manager's
> manager's workflow inbox.
>
> The business now wants to change the escalation process to the following
> instead:
>
> 1. Employee submits time and the workflow sents a work item to the
> employee's manager for approval.
> 2. After 3 days, the manager's manager should have a work item in their
> workflow inbox as well, without removing the original work item from the
> employee's manager.
>
> I am not sure how this can be done but I have thought of 2 options:
> Option 1:
> Don't make the work item in the employee's manager workflow inbox obsolete
> after the deadline and create a new work item to be sent to the manager's
> manager's workflow inbox - problem with this is that we can to probably
make
> sure that when one of the approvers picks up the work item to work on, the
> other approver should not have the work item in their workflow inbox as
> well.  We probably have to take care of the replace functionality as well
as
> the resubmission i.e. it should go back to the other approver's workflow
> inbox after replace or resubmit is executed.
> Option 2:
> Somehow after the deadline, add the manager's manager as the agent for the
> same work item that is currently in the employee's manager's workflow
inbox
> (I do not even know if this is possible).  Hopefully, this will resolve
the
> replace and resubmission functionality questions.
>
> Am I over thinking this?  Is there a better way of doing this?  Has anyone
> done this before?
>
> Cheers,
> d.
>
>


 


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20050915/8f9ab4c2/attachment.htm


More information about the SAP-WUG mailing list