workflow definition - responsible agent

[Dart, Jocelyn]

Quick answer - easy testing
 
Detailed answer - hardly anyone uses that stuff in practice - we pretty
much always assign agents to either a rule (i.e. calculate the agents)
or an expression (i.e. use a list of agents we created/saved earlier,
such as the workflow initiator) , even for easy testing we usually use
the workflow initiator expression.
 
You should not leave the responsible agent blank but instead assign it
to an appropriate rule or expression. 
 
No-one uses workflow customizing much either... usually the changes you
want to make surpass the ability of workflow customizing. 
 
 

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 cool_dude2kin
Sent: Thursday, 09 November 2006 11:52 AM
To: sap-wug at mit.edu
Subject: workflow definition - responsible agent


Hi All,
  I have a really dumb question(rather, a clarification) about the usage
of 'Organizational Objects'(Organizational unit,position,job,workcenter
etc.) in the responsible  agents field in the STEP definition of a
workflow.
 I undestand that all the organizational objects form part of
application data which is client/system dependent.This means,when the
workflow is transported to other systems,the workflow may not work
correctly because these org objects may not exist in the target
system.So what's the point of specifying this application data in the
workflow definition ?! . I feel it's best to leave the values for
organization object as blank in DEV system, and then use 'Workflow
customizing' to assign the organization objects in the traget system.
 
Pls advice if you agree with me or excuse this ignorant fellow
workflower.........  
 
Thanks,
Kiran.

________________________________

Check out the all-new Yahoo! Mail
<http://us.rd.yahoo.com/evt=43257/*http://advision.webevents.yahoo.com/m
ailbeta>  - Fire up a more powerful email and get things done faster.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20061109/a9941dd2/attachment.htm