Delegate access rights to mass data based on item revision access

The WNB0_MethodTypesToDelegateAccessToOwningWSO preference controls which mass types can be updated based on item revision access. That is, you can control which types of mass data can be modified by users who have access to the owning item revision, even if they do not have direct access to the mass attributes.

This preference uses internal names from the Wnb0MethodTypeValues LOV. It delegates create or update access rights to the owning workspace object. This means that if a user has access to an item revision, they can modify the specific mass data types that you define in this preference. The default values for this preference are From Design and From Design (Coated).

Procedure

1. From Launcher, click Preferences.

If this option is unavailable, search for it. You can pin it from the search results for future access.

2. Search for and open the WNB0_MethodTypesToDelegateAccessToOwningWSO preference.
3. Add an internal name from the Wnb0MethodTypeValues LOV as a value for this preference.

Examples

Consider that a user is working on an aircraft landing gear design:

Aircraft landing gear assembly (Item revision)

• Actual mass: 500 kg (WnbAttr1)
• Asserted mass: 485 kg (WnbAttr2)
• From design mass: 475 kg (WnbAttr3)

In this case, the user has access to this item revision. Suppose they use a CAD tool, such as NX, to update the design by changing some components. Even though the mass changes in NX, they cannot update the Asserted mass in Teamcenter because they do not have direct access to WnbAttr2, based on the ACL.

Consider that you add Asserted as a value to the preference. Now, the user has access to the item revision. They modify the design in NX, changing the mass to 490 kg. They can publish the new Asserted mass to Teamcenter from NX. The Asserted mass is updated to 490 kg in Teamcenter. However, they still cannot modify the Actual mass, because you have not added this value to the preference.