Life cycle mapping form

  • Release version: Yokohama
  • Updated January 30, 2025
  • 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 in ServiceNow enables customers to convert existing legacy status values into standardized CSDM life-cycle value pairs, which consist oflife cycle stageandlife cycle stage status. This mapping applies to both asset and Configuration Item (CI) legacy status values. It ensures consistency and alignment with CSDM standards by translating diverse legacy statuses into a unified life cycle framework.

    Show full answer Show less

    Key Features

    • Mapping Scope: The mapping applies to specified legacy CMDB tables and their descending tables, unless a specific mapping exists for those descendants.
    • Priority Handling: When multiple legacy values match mapping rules during record updates, the priority field determines which life cycle value pair to apply. The entry with the highest priority (lowest numerical value) is selected first. This priority is not used during reverse synchronization.
    • Active Status: Mappings can be activated or deactivated. Deactivation causes the system to use lower-priority mappings or set life cycle fields to "TBD" (To Be Determined).
    • Legacy Field and Value Specification: Users specify the legacy field and, if applicable, subfield names and values that serve as the source for mapping.
    • Life Cycle Control Validation: The mapping references a life cycle control that defines valid combinations of class, life cycle stage, and life cycle stage status, ensuring authoritative and consistent assignments.
    • Fallback Values: If no matching mapping is found in the lifecyclemapping table, the life cycle stage and status default to "TBD".

    Practical Use for ServiceNow Customers

    By configuring the Life Cycle Mapping form, ServiceNow customers can seamlessly transition legacy asset and CI status data into the CSDM-compliant life cycle framework. This supports improved data standardization, reporting accuracy, and lifecycle governance. Customers should carefully define mappings with appropriate priority and activation settings to ensure correct and authoritative life cycle assignments during data synchronization processes.

    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.

    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.

    Note:
    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.
    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.