<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>transporting workflow overlaying previous =
information</TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dwindows-1252">
<META content=3D"MSHTML 5.50.4134.600" name=3DGENERATOR></HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT size=3D2>Lolanda,</FONT></DIV>
<DIV><FONT size=3D2></FONT> </DIV>
<DIV><FONT size=3D2>Not sure how the link was lost in your =
scenario. Sounds=20
like the Workflow was already in production when another=20
transport (role change) followed?</FONT></DIV>
<DIV><FONT size=3D2>Reason I ask - to check if the agent assignment for =
the task=20
was every done in production.</FONT></DIV>
<DIV><FONT size=3D2></FONT> </DIV>
<DIV><FONT size=3D2>An activity group (AG) object is client-independent =
just as a=20
standard task (TS) object.</FONT></DIV>
<DIV><FONT size=3D2></FONT> </DIV>
<DIV><FONT size=3D2>The agent assignment (possible agents) for the =
task is a=20
client-dependent change. A popup for transport <FONT =
size=3D2>will or=20
will not appear (d</FONT>epending on your system settings) for =
</FONT></DIV>
<DIV><FONT size=3D2>this. If this change is not assigned to a =
transport/moved then the agent assignment must be done manually in each=20
environment.</FONT></DIV>
<DIV><FONT size=3D2></FONT> </DIV>
<DIV><FONT size=3D2>A change to your client-independent Workflow should =
not have=20
removed this link. </FONT></DIV>
<DIV><FONT size=3D2></FONT> </DIV>
<DIV><FONT size=3D2>Procedure - I prefer to transport the=20
client-dependent changes AFTER the client-independent because =
the=20
objects must exist before relationships can be=20
assigned. </FONT></DIV>
<DIV><FONT size=3D2></FONT> </DIV>
<DIV><FONT size=3D2>Regards, </FONT></DIV>
<DIV><FONT size=3D2></FONT> </DIV>
<DIV><FONT size=3D2>Thomas Maue</FONT></DIV>
<DIV><FONT size=3D2>Workflow Consultant</FONT></DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px =
solid; MARGIN-RIGHT: 0px">
<DIV><FONT face=3DArial size=3D2><B>-----Original =
Message-----</B><BR><B>From:=20
</B>Mullens Lolanda - HRMS <<A=20
=
href=3D"mailto:lmullens@hrms.broward.k12.fl.us">lmullens@hrms.broward.k12=
.fl.us</A>><BR><B>To:=20
</B><A =
href=3D"mailto:SAP-WUG@MITVMA.MIT.EDU">SAP-WUG@MITVMA.MIT.EDU</A> <<A =
=
href=3D"mailto:SAP-WUG@MITVMA.MIT.EDU">SAP-WUG@MITVMA.MIT.EDU</A>><BR>=
<B>Date:=20
</B>Tuesday, March 12, 2002 12:15 PM<BR><B>Subject: </B>transporting =
workflow=20
overlaying previous information<BR><BR></DIV></FONT>
<P><FONT face=3DArial size=3D2> An activity group was assigned to =
a specific=20
task ts1000166 of workflow 1000045 . I was able to see the users =
attached to=20
the task by viewing additional data. A transport was submitted to =
change the=20
task from expression to a role. I noticed that the task lost the link =
to the=20
activity group.</FONT></P>
<P><FONT face=3DArial size=3D2>What is the correct procedure? How can =
changes be=20
done to the workflow and prevent information from being =
overlaid?</FONT>=20
</P></BLOCKQUOTE></BODY></HTML>