transporting workflow overlaying previous information

[THOMAS MAUE JR]

transporting workflow overlaying previous informationLolanda,
 
Not sure how the link was lost in your scenario.  Sounds like the =
Workflow was already in production when another transport (role change) =
followed?
Reason I ask - to check if the agent assignment for the task was every =
done in production.
 
An activity group (AG) object is client-independent just as a standard =
task (TS) object.
 
The agent assignment (possible agents) for the task is a =
client-dependent change.  A popup for transport will or will not appear =
(depending on your system settings) for=20
this.  If this change is not assigned to a transport/moved then the =
agent assignment must be done manually in each environment.
 
A change to your client-independent Workflow should not have removed =
this link. =20
 
Procedure - I prefer to transport the client-dependent changes AFTER the =
client-independent because the objects must exist before relationships =
can be assigned. =20
 
Regards,=20
 
Thomas Maue
Workflow Consultant
  -----Original Message-----
  From: Mullens Lolanda - HRMS <lmullens at hrms.broward.k12.fl.us>
  To: SAP-WUG at MITVMA.MIT.EDU <SAP-WUG at MITVMA.MIT.EDU>
  Date: Tuesday, March 12, 2002 12:15 PM
  Subject: transporting workflow overlaying previous information
 
 
   An activity group was assigned to a specific task ts1000166 of =
workflow 1000045 . I was able to see the users attached to the task by =
viewing additional data. A transport was submitted to change the task =
from expression to a role. I noticed that the task lost the link to the =
activity group.
 
  What is the correct procedure? How can changes be done to the workflow =
and  prevent information from being overlaid?=20
 
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20020313/a6453e37/attachment.htm