cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

RE : How to create a workflow to automatically promote a<br /> EPMDoc

Newbie

RE : How to create a workflow to automatically promote a<br /> EPMDoc

In the WTPart workflow, use an "expression robot" which navigate the
buildlink (active link between WTPart and EPMDoc) and store the linked
EPMDoc in a global workflow parameter (of type "wt.epm.EPMDocument").
You can now use this "linked EPM parameter" in a "Synch Robot" (use
object synchronization, not class synchronization for performance issue)
and listen STATE_CHANGE event on your EPMDoc to promote or demote your
WTPart.

You can do exactly the same to manage the EPMDoc, and then Released
WTPart only if the EPM is released and more ...

It's just more difficult to administer these "synchronous objects" in
case of errors in workflows ...

We are actually in Windchill Foundation 6.2.6 and You have also to set
correct properties in wt.properties in order to have correct behaviour
with synch robot Because they inherit of the ObjectSubscription,and the
default behaviour when you synchronise on an object is to be transferred
when it revise (maybe correct for mail notification subscription, but
bug for a sych robot, but PTC was quick responsive when we log this
problem ...) so you listen the "wrong" revision (example : WTPart
version A listen EPM version A, EPM revise , its B revision is now
linked with a WTPart version B, but workflow of WTPart A now listen EPM
B, and not the A ...)

It will be probably OK in PDMLink 8.0, but I haven't test it yet, and
the "6.2.6 fix properties" is not yet present ...

Regards
Gregory

Announcements
LiveWorx Call For Papers Happening Now!