Configure custom properties using attribute level security

If your Teamcenter environment contains persistent custom properties added for occurrences and item revisions, you can configure them so that those custom properties can be shown or hidden in the Filter panel for users and also in the search results.

Procedure Identify the custom properties that you want to be configured for attribute level security (ALS) and set the Fnd0SupportAls property constant to true for all of them. This property constant is available on the persistent business object. Ensure that the Awp0AllowSearchOnALSEnabledProperties global constant is set to false for the custom properties. By setting this constant to false, the custom properties are not indexed and do not appear in the Filter panel for users who belong to the group marked as Internal and External. If you want the custom properties that are configured for ALS to be available in the Filter panel for users that belong to the group marked as Internal, set the value of this constant to true.

Tip If you set the Awp0AllowSearchOnALSEnabledProperties global constant to true, the users who belong to a group marked as Internal can view the custom properties that are configured for ALS. If these users create sessions and worksets with the custom properties and then share these sessions and worksets with users who belong to the group marked as External, they will still be able to view those custom properties. In order to restrict the users in the group marked as External from viewing the custom properties in the sessions and worksets when this constant is set to true, use access control lists (ACL). Deploy the BMIDE project and then index the required structures using Smart Discovery Indexing. Set the value of the AWS_FullTextSearch_enable_als_restrictions_on_groups_with_external_security preference to false.

Results The custom properties that are configured for ALS are hidden from or shown on the Filter panel for the structures that are indexed using Smart Discovery Indexing.