Table of Contents

Search

  1. Preface
  2. Introducing Reference 360
  3. Getting started with Reference 360
  4. Manage system reference data
  5. Manage reference data sets
  6. Manage code lists
  7. Manage code values
  8. Manage crosswalks
  9. Import data
  10. Manage hierarchies
  11. Manage attributes
  12. Manage workflows
  13. Manage jobs
  14. Reference 360 REST API
  15. Glossary

Reference 360

Reference 360

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.
  1. In the
    Explore
    panel, select a hierarchy and click
    Open
    .
    The hierarchy opens in a new tab.
  2. Click
    Lock
    .
    A draft version of the hierarchy is created, and the hierarchy is locked for other users.
  3. Click
    Hierarchy
    .
    The hierarchy page appears.
  4. To add code values as top-level nodes, perform the following actions:
    1. Click
      Add Hierarchy Value at the Top Level
      .
      The
      Add Code Value
      dialog box appears.
    2. To view all available code values, in the
      Search
      field, enter
      *
      .
    3. Select the code values that you want to add, and click
      Add
      .
  5. To add code values as child nodes, perform the following actions:
    1. Hover over the top-level node for which you want to add a child node, and click
      Add
      .
      The
      Add Code Value
      dialog box appears.
    2. To view all available code values, in the
      Search
      field, enter
      *
      .
    3. Select the code values that you want to add, and click
      Add
      .
  6. To move a node, select a code value and drag the code value to a new location.
  7. To remove a node, select a code value and click
    Remove
    .
  8. To send your changes for approval, perform the following actions:
    1. Click
      Submit
      after you finish adding code values to the hierarchy.
      The
      Send for Approval
      window appears.
    2. Set the priority, due date, and optionally add a comment.
    3. In the
      Compare Versions
      section, review your proposed changes.
    4. Click
      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.
    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.
  9. To cancel the approval request, perform the following actions:
    1. Click
      Cancel Approval Request
      .
      A confirmation dialog box appears.
    2. Click
      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.
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.

Back to Top

0 COMMENTS

We’d like to hear from you!