Rename a Released Part file

[snellutla]

Hi,

What settings I have to change in PDMLINK 9.1 so a user can rename a part file after it is promoted to "Released" state.

Thanks,

Sharath

Release 9.1

DateCode M050

[MikeLockwood]

Modify Identity (needs to be at all states in the object's current history).

[snellutla]

Midify Identity is only allowing me to change to change File Name and Number but not name. I want to rename all the three fields.

Changing Modify to "YES" allowed me to change the name but it is also allwing users to change other part attributes which I don't want.

Thanks,

Sharath

[ddemay]

You have to grant both. Or, write a customization. PDM and PLM systems are designed to protect data and so what you are seeking is usually locked down after it leaves the In Work state of the first version.




Sent from my Verizon Wireless BlackBerry

[MikeLockwood]

Modify Identity requires Modify as prerequisite.
Note also that this acts on the Master, so the permissions are needed for all states in the object's current history.

There is no place that I'm aware that PTC documents what permissions are needed together for things like this.

[pwilliams-3]

Mike,
Here is the documentation from the "Business Administration of Windchill PDMLink 10.0" training (Module 7 Page 24).

Permissions Needed for Change Identify Operations
The Modify permission is required to change the attributes of an object that are not identity attributes.

* A user may perform a change of non-identity attributes if:
* The user has Modify permission to all versions of a business object.
* A user may perform a change of identity attributes if:
* The user has Modify Identity permission to all versions of a business object.



Patrick Williams | Engineering Systems | o: 616.698.3766 | c: 616.947.2110
[cid:image001.jpg@01CCB4CA.65F39F00]

From: Lockwood,Mike,IRVINE,R&D [

[ddemay]

Which on existing stuff requires reassigning the lifecycle of existing
objects depending on how you configured this.



This all aside, if you need to way to only change the name field on a
mastered object such as a CAD Document or Part or Document, then configuring
these permissions will yield too much flexibility. Filtering actions or
creating a workflow triggered via a wizard or action (or state change)
provides audit capabilities and reduced access control issues. Workflows
run as administrator, so any use of these to assign a task and then rename
the object might result in needing some extra code to update who the rename
was actually done by (unless you use a state change) Ultimately, you may
want to reassess why there is a need to change the name or other attributes
on mature data.







From: Lockwood,Mike,IRVINE,R&D [