Need Site Admin privs to create types & attributes??

[MartyRoss]

Wejust received a communication from a PTC TSE confirming that we need to give "Site Administrator" privileges to our business users that wish to create / modify types & attributes as part of their normal workflow.

That sounds crazy to me! Could that really be true??

The bottom line is - according to the TSE - the types and attributes belonging to the default organization (in our case, the only organization) are considered site-level types & attributes, therefore only a site admin can modify them.

Is it normal to give site administrator privileges to non-administrative users of Windchill? If any of you have experience with this particular question in the context of an organization with strict security practices, please share how you handled it.

[MikeLockwood]

Yes, that's absolutely true - but there is much more to the discussion.


1. Don't give these users Site Admin.

2. Rehearse this type of thing, especially related to attributes, on a test system before applying to production.

3. Think about and discuss and plan and fully document this type of thing before even putting in on a test system.

Note that:

- You can never, ever, ever delete an attribute that has been used, even once (although you can delete the mapping to a type for going forward)

- Once you use the attribute, your database grows to accommodate it for all rows; this can never be reduced

- Once you create a sub type, you can never, ever, ever change the display name (if you make a typo you're stuck with it)

In general: Think about it 3 times, rehearse it twice, put in production only once. Limit the number of people who actually do this in production.

[MikeLockwood]

Clarification - Below relates to admin configuration related to types and attributes.
Regular users need to edit attribute values in the course of their normal work. Editing the value of an attribute is like editing the value of a dimension.

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