New access rule for change name permission for all states of object in Windchill

[HelesicPetr]

Based on archived idea I rise a hand to implement it

New access rule of rename permision for all states of object in Windchill 

Windchill user needs the modify permission to rename (change just name) a object in Windchill across all states.

If the wtobject is forward to released state where the object shouldn't be modified the user can't change name  even a new revision is made because the modify permission is not allowed in release state of previous revision...

In some cases the rename operation is required and only admin or Product/Library manager can change the name.

The Idea is to create new permission for change name operation across all states to change it.

Customer needs is to rename MPMLInk operations during a change process and nowadays it is not possible.

[HelesicPetr]

Hello,

I would like to just show existing customization.

Change Name function. (without allowing modify ACL on released versions)

[olivierlp]

Thank you for publishing your idea. We need more information as specified in the form you saw in the submission process. (Questions below). The more details and context you give, the better.
Please let us know within the next two weeks.

1. Describe your environment: What is your industry? What is your role in your organization? Describe your stakeholders.
2. What product & version are you currently running?
3. Describe the problem you are trying to solve. Please include detailed documentation such as screenshots, images or video.
4. What is the use case for your organization?
5. What business value would your suggestion represent for your organization?

[HelesicPetr]

Hello @olivierlp,

1. Why ? PTC does not know partners activity roles atc.?

- industry? Transportation, Automotive, Arms industry, Flexo presses, Agricultural machines and more...

2. All actual versions. 11.0 - 12.1.0.0

3. The attached video shows the problem with customization solution. Customers want it OOTB. 

- change name generally is not possible by user if previous revision is released because user needs MODIFY permission for all revisions to change NAME.

is more clear?

4. described as point 3... users have to contact administrator to change just name of Operations in MPMLink also for all objects in the system. 

NAME is not unique identification for ERP at all. 

5. Much more better relationship with customers that they know that creating a idea has a purpose. (sometimes customers think to stop use Windchill because of lack of PTC interest...)

[olivierlp]

Hello,
Thank you for your idea and the information provided.

[Pekholm]

The current behavior when edit common attributes requires that the user have modify rights on each revision of a WTPart to update part name. Modify Identity only grant rename number. In most cases you don't want to grant modify rights of released data. Is better to introduce a new access rule to grant modify name, than use the modify acl or provide a preference for what attributes to be edited when modify identity is granted.

Best regards

Per

[Marco_Tosin]

The use case is quite common among companies that have Windchill connected to an ERP system.

In the initial design phase of a new product, the new trade name is hardly known so a "generic" one is used.

Despite this, however, it is necessary to already manage the code in the ERP system.

Therefore, once the code has been sent to the ERP system, it is not possible to give users the possibility to modify the identity of the WTPart because the renaming action would also guarantee the renumbering action that would create a new object in the ERP if it was sent again.

To solve this problem, we were forced to create a new attribute, which has the same value as the Name, and modifying the former automatically modifies the latter.

[HelesicPetr]

Hello @Pekholm 

It looks like this is an duplicated idea with a New-access-rule-for-change-name-permission

I've also published a video with custom change name function.

So please vote for it.

Best Regards

PetrH

[olivierlp]

After @HelesicPetr comment, I took the liberty to merge the ideas. It combines the comments in chronological order and, more importantly, the votes. Rather, it combines the voters: if someone voted for the 2 ideas, it counts as only one after the merger. 

[BjoernRueegg]

I believe that the name should not be part of the "Identity" group. The name can be changed during the life cycle. The number, on the other hand, is always the same. 

The customized wizard shown in the video is almost standard, since most European companies not only have one name, but translate it automatically or manually into several national languages. This makes it even more complicated. The companies have to decide which is the main language. This is then the "name" attribute. Multiple languages are not really considered in Windchill.