Rename Problem (access rules?)

[DavidBrand]

Hopefully the below will make sense. 

Problem

When a design is started the CAD object (EPMdoc) is given a sketch number (SK) and initially checked in at revision 0.0 at WIP release level (state) and a COGpart (wtdocument) is automatically created. While the design progresses, it is checked in and the iteration is increased.

When the design is ready to be sent outside of the business, the revision is set to A.0 and set state is used to change the state to PROTOTYPE.

Revise is used to change the state back to WIP (revision B) so changes can be made.

When the design is ready for release to Manufacturing it is renamed to a Made Part (MP) number. Set state is used to change the state to WIP for RELEASE and revise is used to change to revision 1.0 (Prototype parts have alphabetical revisions and Production parts have numeric revisions and the WIP for Release state is used to change from alpha to numerical revision sequences).   

Part no.	Revision	State	Modification / Rename Permission
SK12345	A	WIP	Y
Set State	A	Prototype	N
Revise	B	WIP	Y
Set State	B	Prototype	N
Renamed to MP7890	B	Prototype	N
Set State	B	WIP for Release	Y
Revise	1	WIP for Release	Y
Promotion Request	1	Released	N
Revise	2	WIP for Release	Y

User is unable to rename SK12345 to MP7890 because the object has been set to Prototype level.

Is it possible to grant rename permission to a user for an object that has been set to a state that the user does not have modification permission?

[BenLoosli]

I have a question with this scheme.

How do you find information on SK12345 after it has been renamed? In the Windchill database, the name will now be MP7890, so a search for SK12345 will return nothing. You may be better off do a Save-As in Windchill at rev B to your new MP7890 part so you maintain both the SK and MP numbers.

I would do the revise to Rev C first, then do the rename. This will give the user modification rights at Rev C.

[DavidBrand]

Thanks Ben

We can use a report to find  the information on the renamed SK12345. Using Save-As also means that we have to either use the update parents during save-as or manually replace in the assemblies. Rename takes care of all the assemblies, so is easier for users.

We originally had access rules set so rename worked, but it allowed users to modify objects at PROTOTYPE and they would forget to revise.

David

[SvenVanDroogenb]

---

@BenLoosli wrote:

I would do the revise to Rev C first, then do the rename. This will give the user modification rights at Rev C.

---

This won't work, you will need Modify permissions on all Life Cycle States used for each individual iteration.

[SvenVanDroogenb]

In the Policy Administration you can grant Modify Identity permissions on all Life Cycle States for a usergroup containing the users who need to be able to change the number.