Community Tip - When posting, your subject should be specific and summarize your question. Here are some additional tips on asking a great question. X
Let me first explain the problem.
We currently use an ECN for the release of items (parts, documents and CAD drawings/models)in PDMLink v9 M040. The items being released are added to the Resulting Objects of the Change Task associated to the ECN. A fairly complex workflow is initiated which includes peer review, approval, and authorisation steps in the Release Process.
The lifecycle that the items pass throughduring this workflow are IN-WORK, UNDER REVIEW, PRE-RELEASED and RELEASED
Once the release process completes and the items are setto RELEASED,the user can look at the changes related to the item to look at the release history.
We have a local requirement to allow selected users to perform very simple "typo" corrections (e.g. spelling mistakes)to RELEASED information. The process here relies on raising a Problem Report and Problem Report Action which allows the assignee of the action permission to set the item back to IN-WORK, make the amendment, and then re-release at the same REVISION. The item will iterate due to the check-out/check-in.
Now the problem: if a user looks at the Change Task associated to the initial release,the Resulting Objects on the task now show the latest iteration ... not the iteraion when the original release took place.
So my question: does anyone know of a method to"lock" a Change Task so that the iteraion showing for the Affected/Resulting Objects are fixed at the point that theChange Task is completed?
Many thanks for any help.
Thanks Antonio,
I am looking to "freeze" the Change Task once it reaches the lifecycle state of Resolved (i.e. the task has been completed.) I take your point that we certainly would not want to lock the Change Task to specific iteration of the objects as the change or release was in progress. Definite 'Ugh' !
I was thinking about baseline, but was also wondering if the "Change Modification Tracking" functionality could offer anything?
Thanks Antonio. I am trying hard to persuade the company to stop the practise of allowing "small amendments" on released information. In my mind it breaks basic configuration management principles. Once it's released, it's released. Right?
Thanks also to you Eric for your suggestions and you are right. One person's typo is another's major change!
I had to pose the question to the forum though. You have confirmed both my view on the practice of amending and also that the business are asking for something in the tool that is not available simply OOTB (out of the box).
-Ian