Skip to main content
C
cc-21-Visitor
1-Visitor
October 20, 2010
Question

Previous releasd revision set to obsolete automatically

  • October 20, 2010
  • 2 replies
  • 918 views

Hello

is there a way that PDMLink set automatically to obsolete the latest previous released revision when a new revision is released.
For instance B is released. I create C and release it I would like B to be set automatically to Obsolete.

Thank you very much

2 replies

avillanueva
23-Emerald I
avillanueva23-Emerald I
23-Emerald I
October 20, 2010
Yes, but you would have to write some custom code. If your releases are
done via a workflow, add a step that looks at the items being released
and sets the state on the item's previous revision to Obsolete. If done
in any other way, you would have to create a listener service to listen
for state changes.


P
patrick.chin11-Visitor
1-Visitor
October 21, 2010

Antonio V. is correct.

Also, I advise to follow a standard engineering change process that meets most manufacturing and supply chain requirements. Not all objects go immediately to obsolete. Some previous released still has effectivity based on specificlots, serials and so on. See attached. It is usually best practice to have engineering process sync with MFG and supply chain. Though engineering always designs to the latest release, engineering must support the sustainability and service of other past products.

If your effectivity is immediate for failures or immediate recalls, then it will automatically set the resulting objects to obsolete or superceded.

Terms & ConditionsCookie settingsAccessibility statement