As an administrator, you can configure the user interface to simplify how users enter, manage, and search for data, protect users from performing unauthorized tasks, and help ensure that you conform to your IT asset management practices. When you configure the user interface, you, and all users affected by your configuration changes, immediately see the changes. For example, you do not want anyone, except the asset manager, to see any information for sites and companies. Therefore, you hide the Site and Company tabs and specify that only users in the asset manager role can see those tabs.
Note: For assets, models, and legal documents, you provide a specific configuration by specifying the asset family (assets and models) and legal template (legal documents).
When configuring the user interface, use the following types of configurations:
Note: Local configuration changes override global configuration changes.
A global configuration lets you modify the functionality of your CA APM implementation. You focus on configuring the pages, objects, fields, and so forth, for your specific implementation without having to make configuration changes for all possible users and roles. For example, you do not want to use the contact management functionality. In this situation, you define a global configuration on the Contact page, hide this functionality from all users, and save the global configuration. As a result, no users see the Contact page, unless you define a local configuration to override the global configuration.
Note: If you do not want to make any global user interface changes for your implementation, you do not have to define a global configuration. You can define a local configuration without defining a global configuration.
Use a local configuration to configure the user interface pages based on the requirements and needs of the different users and roles. For example, you define a global configuration to hide the contact management functionality in your implementation. However, there are users in a specific role who must be able to see and update contact information. In this situation, you define a local configuration on the Contact page, make the contact information appear, and save the local configuration. When you assign the local configuration to the users in the role, they see the contact information.
Important! You cannot assign a global configuration to a role. By default, a global configuration is assigned to a role when the user logs in and the security permissions for the role are determined. You can only assign a local configuration to a role.
A global configuration is always assigned to all roles, even when you assign the role to a local configuration. Any permissions from the global configuration that a local configuration does not override are applied to the role. Global configurations are used to configure the product for every user (except for the system administrator role, uapmadmin). To configure the user interface on a more detailed level by role, add a local configuration. In this situation, all users in all roles will see the configured interface based on the global configuration changes, and users assigned to a local configuration will see the additional changes to the interface.
If a user is assigned to a local configuration, the local configuration is assigned to the role when the user logs in.
|
Copyright © 2013 CA.
All rights reserved.
|
|