Manage Fields

This article contains the following topics:
casm173
This article contains the following topics:
You can change the display and attributes of field information on the page to meet your asset management practices and help make it easier for users to enter information for the objects they manage. In the product, these fields are referred to as
configured fields
.
You can manage fields in the following ways:
  • Change a field label to help make the field more familiar to users and conform to your IT asset management practices.
  • Move a field to a new location to help make it easier for users to find the field on the page.
  • Hide a field from display when users should not be able to view a particular field on the page.
  • Make a field appear when users must be able to see a field that you previously hid. For example, you previously hid the Capacity field. Users must be able to see that field because it is required. Add the field back so users can enter a value when defining an asset.
Follow these steps:
  1. Click the tab and optional subtab for the object that you want to configure.
    On the left, click CONFIGURE: ON.
    The configuration of the page is enabled.
    In the Configuration Information area of the page, complete the following steps:
    1. Specify the information for the new global or local configuration, or select an existing 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, and not to the other parts of the object.
    Global configuration changes affect all users, regardless of their role. Local configuration changes only affect users in the roles assigned to the selected configuration.
  2. To change a field label, complete the following steps:
    1. Click the field label and enter the new label.
    2. Click Save Configuration.
      When you assign a configuration to a role, users in the role see the new field label.
  3. To move a filed to a new location, complete the following steps:
    1. Drag-and-drop the field to a new location in the current section.
      You cannot move a field from one section of the page to another. For example, you cannot move a field from the Additional Information section to the Basic Information section.
    2. Click Save Configuration.
      When you assign a configuration to a role, users in the role see the fields in the new location.
  4. To hide a field, complete the following steps:
    1. Next to the field, click the Remove Field icon.
    2. Click Save Configuration.
      When you assign a configuration to a role, users in the role do not see the field. If an event is defined for the hidden field, users still receive notifications. However, any mapped attribute that is not accessible in the workflow process associated with the event is not sent as part of the notification.
  5. To make a previously hidden field appear, complete the following steps:
    1. Click Expose Hidden Fields.
    2. To add the field to the page, follow the on-screen instructions.
    3. Click Save Configuration.
      When you assign a configuration to a role, users in the role see the field on the page.
      After you make a previously-hidden field appear, users can define an event for the field. You do not have to save the configuration because the field has already been added to the configuration. For more information about managing events, see Events and Notifications for CA APM.
Add a Field
You can add a field to the page when users must be able to see a field that exists in the repository but is not part of a global configuration, or any field that has been removed and you have denied access. For example, you previously removed an extended field that is named chipset from the Asset Details page. Users must be able to see and enter a value for this field, so you add the field back onto the page. In addition, if you previously added an extension but did not save the global configuration, use these steps to add the extended field to the page.
When you add a field to an object having multiple asset families (Assets and Models) and legal templates (Legal Documents), the field is added to all families and templates for the object, regardless of the family or template to which you added the field. For example, you add a field for the Hardware asset family. The field is added to all other asset families, including Computer, Other, Projects, Service, and Software.
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 to 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 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.
    You can only add a field for a global configuration. You cannot add a field for a local configuration.
  4. Click Save Configuration to create the global configuration.
  5. Click Add Existing Fields.
    A wizard appears.
  6. To add to the page, select the fields.
    For extended fields, a link appears that matches the object label that is specified when defining an extended field. To add to the page, click the link and select the extended fields.
  7. Click Save Configuration.
    All users see the 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.
Make a Field Read-Only, Required, or Optional
A
required field
is a field that must contain a value to save the record. When you configure a field or create an extended field, you can make the field read-only, required, or optional. Making a field that is required is useful for fields that contain key pieces of data.
When making a new required field, saved records may not have data in the field. When you save the record in the future, you must enter data into the new required field. You must also enter data when a pre-existing record is updated by an application you write using the web services. Your client application must verify that the required field contains data, or provides data for the field. If not, the record will not be updated.
We recommend that before you make a field required, you populate the field for all existing records. You can search to locate all occurrences of blank values in the field by searching for NULL or space (clear the value field).
To make a field read-only, required, or optional
  1. Click the tab and optional subtab for the object that you want to configure. On the left, click CONFIGURE: ON.
    The configuration of the page is enabled.
    In the Configuration Information area of the page, complete the following steps:
    1. Specify the information for the new global or local configuration, or select an existing 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, and not to the other parts of the object.
    Global configuration changes affect all users, regardless of their role. Local configuration changes only affect users in the roles assigned to the selected configuration.
  2. Next to the field, click the appropriate icon to make the field read-only, required, or optional.
  3. Click Save Configuration.
    When you assign a configuration to a role, users in the role see the fields as read-only, required, or optional.
Manage Field Permissions
You can grant permissions to users so they can configure the user interface to change a field label, move a field, make a field required, and hide a field.
You can also grant permissions to users so they can configure the user interface and can perform mass changes on a field. You can perform mass changes on fields that are associated with the following objects:
  • Asset
  • Model
  • Legal document
  • Organization
  • Contact
  • Company
  • Location
  • Site
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 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 assigned to the selected configuration.
  4. In the Permissions area of the page, do one the following:
    • To grant permissions to change a field label, move Modify Labels to the Granted Permissions list.
    • To grant permissions to move a field, move Order Fields to the Granted Permissions list.
    • To grant permissions to make a field required, move Requiredto the Granted Permissions list.
    • To grant permissions to hide a field, move Secure (Read-Only and Access)to the Granted Permissions list.
    • To grant permissions to perform mass changes on a field, move Mass Changeto 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 perform the respective configuration.
View Field Information
You can view the information about any field, including extended fields, to see database-related field attributes. For any field, you can view the object label, database table name, database field name, attribute name, data type, description, and size. Use this information in the following ways:
  • You want to view CA APM data outside of the product using an external reporting solution and must understand database-level information. For example, you want to know the database table name, field name, attribute name, data type, description, or field size for a particular default field or user-defined extended field.
  • You have changed a field label or moved a field to a new location on the page. Use the field information to understand how the field is represented in the database. This field information can be helpful when you work with Technical Support to understand any specific configuration changes you have made to the product.
Follow these steps:
  1. Click the tab and optional subtab for an object.
  2. On the left, click CONFIGURE: ON.
    The configuration of the object is enabled.
  3. Next to the field, click the View Details icon.
    The field information appears.