Page Configuration by Asset Families and Legal Templates

This article contains the following topics:
casm1401
This article contains the following topics:
For most objects, you configure the user interface, save the configuration, and all users in the role that is assigned to the selected configuration see the page that way. No additional configuration options are available. For certain objects (assets, models, and legal documents) you can provide a more specific configuration by selecting a particular
asset family
or
legal template, or all asset families or legal templates
.
You can manage pages in the following ways:
Example: Configure for a Hardware and Software Asset
  • (Hardware Asset) Configure the page for assets by moving important fields (asset name, model name, quantity, serial number, operating system, purchase order number, and service status) to the top of the page and making the fields required. In addition, remove the Host Name field. When you save the configuration, select the asset family
    Hardware
    . As a result, when users assigned to the configuration enter a hardware asset, they see the page as you have configured it.
  • (Software Asset) Configure the page for assets by moving important fields (asset name, model name, quantity, serial number, department, cost center, and purchase order number) to the top of the page and making the fields required. In addition, remove the Service Status and Service Status Date fields. When you save the configuration, select the asset family
    Software
    . As a result, when users assigned to the configuration enter a software asset, they see the page as you have configured it.
Example: Configure Across All Asset Families
Configure the page for assets in all asset families by making the Requisition ID and Purchase Order ID fields read only for all users except the asset fulfiller. The asset fulfiller can edit these two fields. To achieve this result, you create two configurations:
  1. A global configuration that makes the Requisition ID and Purchase Order ID fields read only. Select Across all families for this configuration so that the fields are read only on the Asset page for all asset families. This global configuration applies to all users.
  2. A local configuration that allows users to edit the Requisition ID and Purchase Order ID fields. Select Across all families for this configuration, also, so that the fields can be edited on the Asset page for all asset families. This local configuration is assigned to users in the asset fulfiller role.
As a result, users who are not asset fulfillers cannot edit the Requisition ID and Purchase Order ID fields on the Asset page for any asset family. However, users in the asset fulfiller role can edit the two fields on the Asset page for all asset families.
Example: Configure for a Confidentiality Agreement
Configure the page for legal documents by moving important fields (Document Identifier, Effective Date, Termination Date, and Negotiator) to the top of the page and making the fields required. In addition, remove the Status and Status Date fields. When you save the configuration, select the legal template
Confidentiality Agreement
. As a result, when users assigned to the configuration enter a confidentiality agreement, they see the page as you have configured it.
Custom Asset Families
You can extend the product by creating additional asset families to track products other than hardware and software.
Custom asset families
let you track information about almost any classification of asset in your IT environment. For example, you can create asset families for telecommunications, services. After you create a custom asset family, configure the page and save the configuration for the custom asset family. As a result, a user assigned to the configuration for the custom asset family sees the page as you configure.
Configure the Model and Asset Page by Asset Family
You can configure the Model or Asset page for a specific asset family (for example, hardware asset and software asset) or for all asset families. Users in the role assigned to the configuration see the page as you have configured it.
Follow these steps:
  1. Click the Model or Asset tab.
  2. On the left, click CONFIGURE: ON.
    The configuration of the page is enabled.
  3. In the Configuration Information area of the page, select an asset family or select Across all families.
    If you are creating a global configuration and a global configuration already exists across all families, the Across all families field does not appear.
  4. Specify the information for the new global or local configuration, or select an existing configuration that you want to change.
    Global configuration changes affect all users, regardless of their role. Local configuration changes only affect users in the roles that are assigned to the selected configuration.
  5. Complete any of the following steps:
    • Change a field label.
    • Move a field to a new location.
    • Make a field read-only, required, or optional.
    • Hide a field.
    • Make a previously hidden field appear.
    • Add a field.
  6. Click Save Configuration.
    When you assign a configuration to a role, users in the role see the page as you have configured it.
Configure the Legal Document Page by Legal Template
You can configure the Legal Document page for a specific legal template or for all legal templates. Users in the role that is assigned to the configuration see the page as you have configured it.
Follow these steps:
  1. Click the Legal Document page.
  2. On the left, click CONFIGURE: ON.
    The configuration of the page is enabled.
  3. In the Configuration Information area of the page, select a legal template or select Across all templates.
    If you are creating a global configuration and a global configuration already exists across all templates, the Across all templates field does not appear.
  4. Specify the information for the new global or local configuration, or select an existing configuration that you want to change.
    Global configuration changes affect all users, regardless of their role. Local configuration changes only affect users in the roles that are assigned to the selected configuration.
  5. Complete any of the following steps:
    • Change a field label.
    • Move a field to a new location.
    • Make a field read-only, required, or optional.
    • Hide a field.
    • Make a previously hidden field appear.
    • Add a field.
  6. Click Save Configuration.
    When you assign a configuration to a role, users in the role see the page as you have configured it.