Hierarchy Configuration

In the product, a hierarchy is a way to establish a logical relationship to an object field. You can define a hierarchy to extend the product and track more information and detail about an object. You can define a hierarchy for any object.
casm1401
In the product, a
hierarchy
is a way to establish a logical relationship to an object field. You can define a hierarchy to extend the product and track more information and detail about an object. You can define a hierarchy for any object.
Example: Create a Hierarchy to Locate an Asset
In CA APM, when you enter an asset, use the Location Name field to enter generic asset information. Information can be the location of an asset (city and address). However, for a hardware asset family, you need a more detailed way to track the asset location. To locate an asset for maintenance and repair, find the specific office number, building number, floor number, and cubicle number. Define the following hierarchy:
Pittsburgh Office Building 3 Fourth Floor Cubicle 49466
In the previous hierarchy, each field is related to the field above it. If you change the information for a parent field, the information for the child field is changed. However, changing a child field (Fourth Floor) does not change the parent field (Building 3).
 
By defining this hierarchy, you know and can track the exact location of the asset. CA APM manages the fields that you define in the hierarchy so they can be used in searches and reports.
Define a Hierarchy
You can define a hierarchy to extend the product and track more information and detail about an object. For example, define a location hierarchy for an asset to track the asset to a specific location. When asset location with an established hierarchy for the asset family is selected, a list appears inside the location section. Each location hierarchy extended field has one list. If the location selected has values for the hierarchy, the values are populated in the drop-down list.
Before you define a hierarchy, verify that you have the following reference information: table name, label, format, field name, attribute name, field size. Also verify, if an entry for the extended field in the hierarchy is required.
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. Permission changes that 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 define a hierarchy for a global configuration. You cannot define a hierarchy for a local configuration.
  4. (Optional) Click Save Configuration to create the global configuration.
  5. Click Add Extension.
    A wizard appears.
  6. To define the hierarchy, select the Hierarchy option and follow the on-screen instructions. The following fields require explanation:
    • Object Label
      Specify the default object label for the hierarchy. You can change this label to meet your requirements. For example, change the default label Asset Extensions to Asset.
    • Object Table Name
      Specify the database table name for the hierarchy.
    • Object Tenancy
      If multi-tenancy is enabled, specify how multi-tenancy works for the hierarchy by selecting one of the following options. The option that you select is applied to all levels in the hierarchy.
      • Untenanted
        Defines objects without a tenant attribute. All data in these objects is public, and any user can create and update untenanted public data.
      • Tenant Required
        Defines objects with a tenant attribute that cannot be null (enforced by CA APM, not the DBMS). All data in these objects is associated with individual tenants; there is no public data.
      • Tenant Optional
        Defines objects with a tenant attribute that can be null. You can either create these objects as tenanted or public. When you select a tenant in a tenant drop-down to create an object, the object becomes a tenanted object. However, when you select the Public Data option in a tenant drop-down, the object becomes a tenanted public object. A tenant drop-down does not appear for users assigned to a role that only exposes a single tenant when entering data.
    • Begin with existing field
      Select an existing field as the basis for fields in the first hierarchy level.
    • Begin with a new field
      Select to start the hierarchy with a new field you define. Define at least two levels for the hierarchy.
  7. Click Save Configuration.
    All users see the hierarchy on the page.