Configuring the User Interface › How to Configure the User Interface › Hierarchy Configuration › Define a Hierarchy

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 a location is selected for the asset, and the location has a hierarchy established for the current asset family, 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.

Important! Before you define a hierarchy, 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 in the hierarchy is required.

To define a hierarchy

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, and not to the other parts of the object.

   Important! 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. Select the Hierarchy option and follow the on-screen instructions to define the hierarchy. The following fields require explanation:

   Object Label

   Displays 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 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. You must define at least two levels for the hierarchy.

7. Click Save Configuration.

   All users see the hierarchy on the page.