Server Administration > Role-Based Views for Users > Making ViewSets Available to Users > Mandatory ViewSets
Mandatory ViewSets
In combination with permissions for which users are able to download and edit specific ViewSets (see “ViewSet Permissions”), you can ensure that the specified users get the ViewSets by configuring them to be mandatory.
Mandatory ViewSets bypass the user acceptance process for downloading new (or updated) ViewSets from the Windchill RV&S server (see the User documentation for information on the user acceptance process). Instead, mandatory ViewSets are automatically downloaded and imported into each user’s client at the time the Windchill RV&S client connects to the server. Users are not notified that the mandatory ViewSet has been imported or updated and are not able to refuse the new or updated ViewSet. Once installed, mandatory ViewSets are automatically opened in the Windchill RV&S client and their actions and actions groups cannot be customized.
Mandatory ViewSets, in combination with ViewSet permissions, provide your organization with another key component to producing a consistent process across or within groups.
Only published ViewSets can be specified as mandatory.
You can specify if a ViewSet is mandatory in the following operations:
“Editing ViewSet Attributes”
“Publishing ViewSets”
Key Considerations
Users are not notified that a mandatory ViewSet has been updated and cannot refuse (or observe) its import.
Mandatory ViewSets display Mandatory in parenthesis in the Windchill RV&S client title bar.
Users cannot close mandatory ViewSets.
Users can delete mandatory ViewSets, but the ViewSets are imported and opened the next time the Windchill RV&S client is run.
Updated mandatory ViewSets are only opened the next time the Windchill RV&S client is run.
Users may extensively customize optional ViewSets stored in their clients. If you configure the corresponding published (server) Viewset to be mandatory, all of the users customizations are silently lost.
Mandatory ViewSets are intended to be an enforcement mechanism to provide uniform use of a ViewSet by users. They are not intended to be a ViewSet distribution mechanism only.