Skip to main content
A
Anonymous
May 31, 2011
Question

How to allow new iteration at same revision for released EPMDcoument

  • May 31, 2011
  • 11 replies
  • 2506 views

I find that I have lifecycle or domain policies a little too strict.


Once a EPMDocument is released, user cannot check-out until the EPMDocument is "In Work".
However, the only way for a user to get it to "In Work" is to go through a revision (new rev letter).

We need to allow users to get the EPMDoc to "In Work" and check-out without revising.
At first, I thought to give them "Set State" in the domain policy.
Or maybe enable "Set State" in the life cycle (at Released state).
Or both of the above.
I suspect I might be giving the users too much authority with any of the above.


Recommendations?


Gerry

11 replies

Show previous replies
L
LSivertsen1-Visitor
1-Visitor
June 7, 2011
Hi Xavier

We have also seen problems in this scenario concerning access permissions for roles.
We have a role called "View released". They are only able to view released material. In your scenario they would only be able to see 1.3. 2.5 would be hidden for them. PDMLink checks the access to a part on the latest iteration in every revision. PDMLink does not check all iteration in every revision.

This is only a problem for us for the 3.4 migrated objects as we do not allow it to happen in PDMLink. It is a major problem because we still use the "old" part in production. We would love to have this problem fixed.

I would not recommend letting a newer iteration be created in a lower state in the same revision.

Best regards
Lisbeth Sivertsen

Terms & ConditionsCookie settingsAccessibility statement