Life cycle mapping form

  • Release version: Zurich
  • Updated July 31, 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 for assets and configuration items (CIs) into standardized CSDM life-cycle value pairs, specifically life cycle stage and life cycle stage status. This mapping ensures that legacy data aligns with modern lifecycle standards, improving consistency and accuracy in asset and CI lifecycle management.

    Show full answer Show less

    Key Features

    • Mapping Scope: Maps legacy status values from specified CMDB tables and their descending tables to life-cycle stage and status pairs.
    • Priority Handling: When multiple legacy values match mapping rules on an update, the system applies the mapping with the highest priority (lowest numerical value). Priority is not used during reverse synchronization, which expects a single mapping per life-cycle value.
    • Activation Control: Mappings can be activated or deactivated. Deactivation causes fallback to lower-priority mappings or sets life cycle fields to “TBD.”
    • Legacy Field Configuration: Supports mapping for both primary legacy fields and their subfields (e.g., hardware status and substatus), allowing precise source value specification.
    • Life Cycle Control Validation: Uses authoritative life cycle control classes to ensure mapped life cycle stages and statuses are valid combinations per organizational standards.
    • Fallback Values: If no matching mapping exists, life cycle stage and status default to “TBD,” ensuring clarity about unmapped legacy states.

    Practical Use for ServiceNow Customers

    ServiceNow customers can utilize the Life Cycle Mapping form to systematically translate legacy status values into standardized CSDM life-cycle stages and statuses, facilitating accurate lifecycle tracking and reporting. By configuring priority and activation settings, customers control how multiple legacy values are resolved and ensure that lifecycle data remains consistent with organizational policies. This mapping supports cleaner data integration and lifecycle management processes, ultimately enhancing visibility and control over asset and CI states throughout their lifecycle.

    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.