cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Rename'Change an object's name attribute' should be controlled not depending on 'MODIFY' permission.

Rename'Change an object's name attribute' should be controlled not depending on 'MODIFY' permission.

Current behavior is described in CS37461.

But customer desires to change object's name by some dedicated permisson like 'RENAME' not depending on 'MODIFY'

because the object once released turned to be read-only(cannot MODIFY), if the object revised, nobody cannot rename though the object status is still 'In-Work'.(because Rev.A is read-only; cannot MODIFY)

7 Comments
Level 7

Agree, and there is also the reversed use case: I want to grant checkOut/checkIn but deny changing the Name

Level 11

This leads to the discussion to have the possibility to set modify rights for each attribute... So you could actually make it possible to have marketing user to change only their attribute and haven't any rights for technical attributes. Or in this case the Engineer can change only certain attributes on the change Notice.

Level 7

the questtion is: Is Name just an Attribute or does it belong to Identity? Some Customer consider Name as Identity (eg. for WTDocuments) and even established name uniqueness for it.

Level 8

Our use case.

We have Sketch numbers (SK) for initial design and prototype, followed by Made Part (MP) numbers for Released designs.

Start  SK at WIP release level were users can create, delete, rename etc. objects. When the design is ready to leave the business the object is set to PROTOTYPE release level (either promotion request or set state) and the object can not be modified without revise which sets back to WIP. With current behaviour we have to use SAVE-AS to move from SK to MP where we would prefer to use RENAME.

Level 8

brueegg, this is exactly what we need. We need the abiltity to grant permissions to modify specific attributes, even if the element itself is for example "released". suppose you have a attribute: "obsolete reason", which indicates the reason why someone change the state to obsolete. you don't want to allow to modifiy anything but this attribute. as I'm aware of, this is not possible.

this was possible 20 years ago in the good old "Work Manager" of CoCreate! Customers who made the switch are often dissapointed by things like this.

Community Manager
Status changed to: Acknowledged
 
Community Manager
Status changed to: Acknowledged