Reference 360 > Manage hierarchies > Creating hierarchies
  

Creating hierarchies

You can add, move, and remove code values in the hierarchy to define hierarchy relationships between code values.
Before you create a hierarchy, define the hierarchy model. The hierarchy relationships that you can create and the code values that you can use depends on the hierarchy model.
    1In the Explore panel, select a hierarchy and click Open.
    The hierarchy opens in a new tab.
    2Click Lock.
    A draft version of the hierarchy is created, and the hierarchy is locked for other users.
    3Click Hierarchy.
    The hierarchy page appears.
    4To add code values as top-level nodes, perform the following actions:
    1. aClick Add Hierarchy Value at the Top Level.
    2. The Add Code Value dialog box appears.
    3. bTo view all available code values, in the Search field, enter *.
    4. cSelect the code values that you want to add, and click Add.
    5To add code values as child nodes, perform the following actions:
    1. aHover over the top-level node for which you want to add a child node, and click Add.
    2. The Add Code Value dialog box appears.
    3. bTo view all available code values, in the Search field, enter *.
    4. cSelect the code values that you want to add, and click Add.
    6To move a node, select a code value and drag the code value to a new location.
    7To remove a node, select a code value and click Remove.
    8To send your changes for approval, perform the following actions:
    1. aClick Submit after you finish adding code values to the hierarchy.
    2. The Send for Approval window appears.
    3. bSet the priority, due date, and optionally add a comment.
    4. cIn the Compare Versions section, review your proposed changes.
    5. dClick Send for Approval.
    You receive an email notification confirming that you successfully sent the approval request. Users assigned the Business Steward stakeholder role for the asset or the Reference 360 Business Steward role are notified of the task. The task appears in the Workflow Inbox tab.
    Note: Users assigned the Reference 360 Planner role and the Planner stakeholder role for a hierarchy can send their proposed changes for approval or directly publish their changes without approval.
    9To cancel the approval request, perform the following actions:
    1. aClick Cancel Approval Request.
    2. A confirmation dialog box appears.
    3. bClick OK.
    The hierarchy is reset to the draft state. To unlock the hierarchy, you must discard the draft.
The following image shows an example hierarchy:
The hierarchy displays the North America code value and South America code value as top-level nodes. The North America code value contains child code values, including Canada and USA.
Note: When you sort a hierarchy that contains multiple child nodes in a parent node, the code values are sorted based on the category of child nodes. For example, if a parent node has two categories of child nodes such as CRM country codes and ISO country codes, sorting is applied on each child node category.