Life cycle mapping form

  • Release version: Xanadu
  • Updated September 30, 2024
  • 2 minutes to read
    • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of Life Cycle Mapping Form

    The Life Cycle Mapping module helps ServiceNow customers transition existing legacy status values to Cloud Service Data Model (CSDM) life-cycle value pairs, which include life cycle stages and statuses for both assets and Configuration Items (CIs).

    Show full answer Show less

    Key Features

    • Mapping for Table: Specifies the legacy CMDB table to which the mapping applies, including descending tables.
    • Priority: Sets the priority for applying the mapping definition; higher priority mappings take precedence.
    • Active: Indicates whether the mapping definition is active, influencing which mappings are used during deactivation.
    • Legacy Field Name: Identifies the current legacy field used for storing a life cycle stage.
    • Legacy Field Value: Represents the current value in the legacy field that will be mapped.
    • Life Cycle Control: Establishes valid combinations for life cycle mapping, ensuring accurate transitions.
    • Life Cycle Stage and Status: Maps legacy values to standard life cycle stages and statuses, ensuring proper alignment in the CSDM.

    Key Outcomes

    By using the Life Cycle Mapping module, customers can effectively manage the conversion of legacy status values, ensuring data consistency and compliance with CSDM standards. This streamlines asset and CI management processes and enhances overall operational efficiency.

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

    Fields on the Life cycle mapping form

    Table 1. Life cycle mapping form
    Field Description
    Mapping for table Legacy CMDB table and descending tables that this mapping applies to.

    Applies to a descending table unless there is a mapping configured specifically to the descending table.
    Priority

    Priority of applying this mapping definition for the table.
    Active

    Denotes whether to apply this mapping definition.

    Deactivation results in lower-priority mappings being used or setting standard life cycle fields to TBD.
    Legacy field name Legacy field in the specified Mapping for table that is currently being used to store a life cycle stage. The value should be used as the source for the life cycle mapping.
    Legacy subfield name Value to set if the Legacy field name has a subfield. For example, if hardware Status has a substatus, then specify the name of the substatus here.
    Legacy field value Legacy value in the specified Mapping for table that is currently being used store life cycle stage. The value should be used as the source for the life cycle mapping.
    Legacy subfield value Value that is set if the Legacy field value has a subfield. For example, if hardware Status has a substatus, then specify the value of the substatus here.
    Life cycle control Class and life cycle stage and life cycle stage status that are used as the authoritative source of valid combinations for life cycle mapping.
    Table Standard object table that the Life cycle control belongs to.
    Life cycle stage

    Standard life cycle stage to map the specified Legacy field value to.

    Note:
    The Life cycle control setting determines that this particular life cycle stage is appropriate for the mapping.

    If there is no match in the life_cycle_mapping table, the value is set to TBD.
    Life cycle stage status

    Standard life cycle stage status to map the specified Legacy field value to.

    Note:
    The Life cycle control setting determines that this particular life cycle stage status is appropriate for the mapping.

    If there is no match in the life_cycle_mapping table, the value is set to TBD.