Post Release Tasks?? - Change Notice and Promotion Request

[lhoogeveen]

We need certain tasks/notifications to happen AFTER the state of the objects change:

• For buy parts, purchasing to send released drawings to suppliers (with updated watermark that reflects the new released state)
• For make parts, manufacturing program any CNC files, etc.

How do people handle these post release tasks/notifications? Custom workflow? Almost seems like there should be post release tasks in the Change Notice Implementation Plan. Seems like this would be pretty common?

[JHall]

@lhoogeveen 

This is what we did before:

1. First task on the Engineering Notice we shift the Lifecycle State to Released.
2. Information on those Released objects go to our ERP system.
3. Further tasks on ECN go to Purchasing/Planning to enter information into our ERP system.
4. Last task comes back to Engineering to finish the ECN and any edits.

That presented problems when the supply chain found issues that required a change on a drawing.  Engineering Users couldn't edit a Released object, so we've made this change to the procedure.

1. First task on the Engineering Notice we shift the Lifecycle State to Implementation.
   1. Implementation can be edited by Engineering Users
2. Information on those objects in Implementation go to our ERP system.
3. Further tasks on ECN go to Purchasing/Planning to enter information into our ERP system.
4. Last task comes back to Engineering to finish the ECN and any edits.
5. All objects in ECN go to Prototype, Released, Obsolete, etc upon ECN being Resolved.

Hope this helps.

James
Windchill 11.0