Specify how to map legacy life-cycle states to CMDB states

  • Release version: Washingtondc
  • Updated February 1, 2024
  • 1 minute to read

    • Use the Life Cycle Mapping module to specify how existing legacy status values should be converted to CSDM life-cycle value pairs. You map both asset and CI legacy status values to life-cycle values.

    Before you begin

    Role required: itil_admin or asset_admin

    About this task

    In this example, your existing data uses a life-cycle attribute named Install Status for hardware CIs. You use the Life cycle mapping form to map the existing Pending Install value of the Install Status attribute to the Deploy/Test life-cycle state in the CMDB.

    Assign CSDM life-cycle values to existing legacy values.

    Procedure

    1. Navigate to All > CSDM > Life Cycle Mapping.
    2. On the Life cycle mappings list view, select New and then fill in the Life cycle mapping form.

      The fields on the form are described in Life cycle mapping form.

      Important:
      If you map more than one legacy status value set to any single life-cycle value pair, then select the Reverse sync option in the next step.
    3. Skip this step if you map only one legacy status value set to a life-cycle value pair.

      The Priority value on the life cycle mapping table is used when a record update triggers the “legacy-to-life-cycle” sync, and multiple legacy value states on the record match with mapping rules. Of the multiple values, the highest priority (lowest numerical value) entry is used to set the life-cycle value pairs. If the highest priority entry can't be used, the system uses the next record in priority. The Reverse sync field does not appear on the form by default, but you can add it if needed.

      Priority is not used if reverse sync is active because there should be a maximum of one reverse-sync choice for each life-cycle value per class.

      Note:
      Use of reverse sync results in some loss of fidelity over time. As time goes on, the lower priority values will become less common (unless you have a process that sets that value directly).
    4. Select Submit.
    5. Repeat the process and, when you have mapped all existing life-cycle states, migrate them to the CMDB.
      For instructions, see Activate life cycle migration.