I am working on developing lifecycles for our conversion from Intralink to PDMLink.
I am trying to figure out a process problem
During the Lifecycle, I am having users use Promote to get it to go to the proper Released state. As an action from the promotion, I define the lock state as Under Review.
For now, I am keeping the approval process very simple and have a list of approvers. Where I am having problems is that the approvers want to touch the CAD object before they approve the object. Most of the time the purpose is to call up a drawing and add approval information before the document is actually released into PDMLink.
I can always have the approvers reject the submit, make the changes and then resubmit, but this seems to be a bit more work than what they want. The approvers also want the file to remain in a locked state so that no one else can make changes at that time.
The other method I am testing is to allow the approvers access to the files in the Under Review state. In the Lifecycle I added Revise for the Under Review state. I then restrict access using my Policies to only the approvers. This seems to work until the Approver actually checks in an object. This check in seems to break the approval process. After the approver checks in the object, then any approval or reject from the assignments does not place the object to the selected state and stays at the Under Review State. I can add Set State to the Lifecylce so that the Approver can move the file to the desired state. I am a bit wary of defining a process that actually breaks some defined process (the approval process gets broken). I have done funny work arounds in Pro/E and they always seem to come back and bit me where the sun does no shine.
I am wondering if anyone else has had this problem and how did you solve it?
I am not familiar with Change management and I am trying to avoid this for now but if that is a better way, I had better learn fast.
Ronald B. Grabau
ME Applications Engineer
HP - Houston