9.1 to 10.0 Change in Functionality AutoNumbering

[BrianSullivan]

Hello

In 9.1 if you AutoNumber then by default it could not be changed... there is an OIR constraint protecting it. If an Orgadmin hit Rename they could not change the number.... If you want to allow it you could remove the constraint.

In 10.0 you can Rename by Default as orgadmin..... And no reference in the OIR.

Has anyone investigated how to get 10 to act like 9.1? NO User by Default should be able to Change the Auto-Generated Number for a Windchill Part.

Anyone know why PTC Changed the Default Behavior?

Brian Sullivan

[BrianSullivan]

Hello.
Sorry this was a confusion on our part.
AutoNumber acting the same between 9.1 and 10.0;

Both systems allow the AutoNumber for wtParts/Documents to be overwritten with the Modify Identity ACL.

I guess my question should be how to block this? Any Constraints for Part OIR? We were hoping to allow Users to have Modify Identity so they could rename the Name Field. Because Name is so prevalent in the system we were going to use it as a Short Description that could be passed to SAP.

If we can not lock down Name.... then I guess we will need to strip from all the Table Displays... Let it match Number... and Create a New Short Description Attribute for the Wtparts. (as well as Document; CAD to be consistent)

Brian Sullivan

[MikeLockwood]

It really seems that this should be split:

- Freely allow editing the NAME

- Closely control changing the NUMBER

They should not be combined as "change identity" permission

[sdrzewiczewski]

If you are using ESI to pass data back and forth to SAP (or Oracle for
that matter), once the part has been sent to the ERP system, you cannot
change it's number, but you can change it's name.

I do agree that it would be nice to split those two into different
permissions.

Steve D.

> It really seems that this should be split:
>
> - Freely allow editing the NAME
>
> - Closely control changing the NUMBER
>
> They should not be combined as "change identity" permission
>