Extended Field Configuration

Contents
casm171
Contents
You can design your own fields (extended fields) and can add them to objects. Extended fields are additional fields to help you capture data in your repository critical to the asset management at your site. If you are not able to find an appropriate field in your repository to store key data, define an extended field for the data.
You can define extended fields for models, assets, legal documents, costs, payments, model parts and pricing, contacts, companies, organizations, locations, and sites. You can use extended fields when searching and for reports.
You can add an extended field that you created for an asset cost to a legal document cost. Under Legal Document, click Add Existing Fields on the Costs configuration page.
Extended fields are shared with the products integrating with CA APM (CA Service Desk Manager and CA Service Catalog). Any changes that are made to the extended field values in the integrating products are immediately reflected in CA APM. And, any changes you make to the extended field values in CA APM are reflected in the integrated products.
Define an Extended Field
You can define an extended field to help you capture all data in your repository that is critical to your asset management program. For example, when entering an asset for a blade server, there is no way to enter the chipset. Define an extended field that is named
chipset,
which adds the field to the Asset Details page. Users can enter the chipset information (for example, Intel 5520) with the other information such as the asset name, serial number, memory, processor, operating system.
These steps work only the first-time you complete the wizard and define the extended field for the object. Before you define the extended field, verify that you have the following information for reference: table name, label, format (character, boolean, currency, date, decimal, or integer), field name, attribute name, field size, and whether an entry for the extended field is required. After you complete the wizard, you can configure the extended field like any field.
Follow these steps:
  1. Click the tab and optional subtab for the object that you want to configure.
  2. On the left, click CONFIGURE: ON.
    The configuration of the page is enabled.
  3. In the Configuration Information area of the page, complete the following steps:
    1. Specify the information for the new global configuration, or select an existing global configuration that you want to change.
    2. (Optional) In the Object drop-down list, select the part of the object that you want to configure. Any permission changes you make (for example, deny permissions to move a field) apply only to that part of the object.
      For example, when configuring a legal document, you select Legaldoc Status History in the Object drop-down list. You deny permissions to move fields for that part of the object (the status history). The permission changes apply only to the status history part of the object. Changes do not apply to the other parts of the object.
    You can only define an extended field for a global configuration. You cannot define an extended field for a local configuration.
  4. Click Save Configuration to create the global configuration.
  5. Click Add Extension.
    A wizard appears.
  6. To enter the information for the extended field, select the Simple Field option and follow the on-screen instructions.
    To change the default object label for the extended field, change the label in the Object Label field. For example, change the default label
    asset hardware Extension
    to
    Hardware Extension
    .
  7. Click Save Configuration.
    All users see the extended field on the page.
    After you add a field and define an extended field, and save the field to a local or global configuration, users can define an event for the field. For more information about managing events, see Event and Notification Configuration for CA APM.
Grant Permissions to Define an Extension
You can grant permissions to users so an Add Extension link appears to define an extension.
Follow these steps:
  1. Click the tab and optional subtab for the object that you want to configure.
  2. On the left, click CONFIGURE: ON.
    The configuration of the page is enabled.
  3. In the Configuration Information area of the page, specify the information for the new global configuration. You can select an existing global configuration that you want to change.
    You can only define an extended field for a global configuration. You cannot define an extended field for a local configuration.
  4. In the Permissions area of the page, move Extend Object to the Granted Permissions list.
  5. (Optional) Select the Inherit Permissions from Parent Object check box to apply any security permissions from a top-level (parent) object to the lower-level (child) object using the same configuration.
    For example, you create a local configuration for an Organization. In the configuration, you deny permissions to change field labels, move fields, make fields required, and hide fields. After you save the configuration, you open Attachments under Organization and select the Inherit Permissions from Parent Object check box. All permissions from the Organization are applied to Attachments. In this example, because permissions to change field labels, move fields, make fields required, and hide fields are applied to the Organization, the permissions are also applied to the Attachment.
  6. Click Save Configuration.
    When you assign a configuration to a role, users in the role have permissions to define an extension.