Parallel processing with dynamic user selection

[Dart, Jocelyn]

Just a suggestion:
Extend your event with an additional parameter indicating the work item id to be closed (not the user id ... because of substitutes, forwarding, et al. )  Add a check function module to your terminating event (yes it is possible!) to check the parameter. 
 
 

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 May, Kevin
Sent: Friday, 30 June 2006 6:37 AM
To: SAP Workflow Users' Group
Subject: RE: Parallel processing with dynamic user selection


Hi George, I'm currently doing something similar on 4.7.  I have an unknown amount of agents to whom we need to send the same workitem.  I've done this using a multi-line element which contains the agent id.  In the task the agent expression is assigned to the index of the multi-line element [&_WF_PARFOREACH_INDEX&] then on the 'Other' tab the multiline element is assigned.  This works well in the sense that each agent receives a unique view of the same work item, i.e. each work item has a separate work item id.  The problem I'm currently facing is the termination of the work item.  I'm terminating it with an event.  This works however it terminates all the work items regardless of the work item id.  Sorry I couldn't give you a completely positive answer.
 
Kevin 

	-----Original Message-----
	From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of Knoske, George
	Sent: Thursday, June 29, 2006 4:21 PM
	To: sap-wug at mit.edu
	Subject: Parallel processing with dynamic user selection
	
	

	Hi All,

	

	We're on ECC6.

	

	I would like to trigger parallel processing of the same task by multiple users.  Each user would make an approve/reject decision on their own.  After all users have responded the workflow will continue down different paths based on "all approve" or "partial approve" summation.  I've read the archives and see references regarding the usage of multi-line elements within container operations as a possible option.  Is this the best method available?  If so can the users that receive the workitems be identified dynamically, and if so exactly how do you populate the multi-line element at the workflow step level at run-time?  We plan to use the ORG structure to identify users.  Of course the user-ids assigned to the ORG structure roles can and will change over time.  Thus, if the user assignment changes the workflow is smart enough to generate a workitem for the new user.  Again, each user must receive the workitem, and each must act on it independently.

	

	Any help is appreciated.

	

	-------------------

	George Knoske

	Analyst

	Information Technology 

	Services and Solutions

	

	Kao Brands Company

	2535 Spring Grove Ave. Cincinnati, OH 45214

	

 
________________________________

  
This email communication is intended as a private communication for the sole use of the primary addressee and those individuals listed for copies in the original message. The information contained in this email is private and confidential and If you are not an intended recipient you are hereby notified that copying, forwarding or other dissemination or distribution of this communication by any means is prohibited.  If you are not specifically authorized to receive this email and if you believe that you received it in error please notify the original sender immediately.  We honour similar requests relating to the privacy of email communications. 

 

Cette communication par courrier électronique est une communication privée à l'usage exclusif du destinataire principal ainsi que des personnes dont les noms figurent en copie.  Les renseignements contenus dans ce courriel sont confidentiels et si vous n'êtes pas le destinataire prévu, vous êtes avisé, par les présentes que toute reproduction, transfert ou autre forme de diffusion de cette communication par quelque moyen que ce soit est interdite.  Si vous n'êtes pas spécifiquement autorisé à recevoir ce courriel ou si vous croyez l'avoir reçu par erreur, veuillez en aviser l'expéditeur original immédiatement.  Nous respectons les demandes similaires qui touchent la confidentialité des communications par courrier électronique. 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20060704/6697c14d/attachment.htm