{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":46693,"path":"servicenow-platform/common-service-data-model-csdm/csdm-life-cycle-mapping-form.md","title":"Life cycle mapping form","bundle":null,"doc_type":null,"release":"australia","body":"\n# Life cycle mapping form\n\nUse 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.\n\n## Fields on the Life cycle mapping form\n\n\n
\n\nField\n\n\n\nDescription\n\n
\n\nMapping for table\n\n\n\nLegacy 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.\n\n
\n\nPriority\n\n\n\nPriority of applying this mapping definition for the table.\n\n The **Priority** value on the life cycle mapping table is used when a record update triggers the “legacy-to-life-cycle” synchronization, 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.\n\n **Note:** Priority is not used if **Reverse synchronization** is active because there should be a maximum of one reverse-synchronize choice for each life-cycle value per class.\n\n
\n\nActive\n\n\n\nDenotes whether to apply this mapping definition.\n\n Deactivation results in lower-priority mappings being used or setting standard life cycle fields to **TBD**.\n\n
\n\nLegacy field name\n\n\n\nLegacy 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.\n\n
\n\nLegacy subfield name\n\n\n\nValue 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.\n\n
\n\nLegacy field value\n\n\n\nLegacy 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.\n\n
\n\nLegacy subfield value\n\n\n\nValue 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.\n\n
\n\nLife cycle control\n\n\n\nClass and life cycle stage and life cycle stage status that are used as the authoritative source of valid combinations for life cycle mapping.\n\n
\n\nTable\n\n\n\nStandard object table that the Life cycle control belongs to.\n\n
\n\nLife cycle stage\n\n\n\nStandard life cycle stage to map the specified **Legacy field value** to.\n\n **Note:** The **Life cycle control** setting determines that this particular life cycle stage is appropriate for the mapping.\n\n If there is no match in the life\\_cycle\\_mapping table, the value is set to **TBD**.\n\n
\n\nLife cycle stage status\n\n\n\nStandard life cycle stage status to map the specified **Legacy field value** to.\n\n **Note:** The **Life cycle control** setting determines that this particular life cycle stage status is appropriate for the mapping.\n\n If there is no match in the life\\_cycle\\_mapping table, the value is set to **TBD**.\n\n
## Life Cycle Stage inheritance for Business Application records\n\nBusiness Application records define a restricted set of Life Cycle Stage values that are intended to reflect application planning and usage, such as Ideation, Design, Operational, and End of Life. These life cycle definitions are configured using the life\\_cycle\\_control table specifically for the cmdb\\_ci\\_business\\_application class. When you view or edit a Business Application record, however, additional Life Cycle Stage values such as Deploy and Inventory might also appear. These stages are not defined directly for Business Application, but are inherited from parent CI classes \\(for example, cmdb\\_ci\\) through the aggregation-based inheritance model that is used by life\\_cycle\\_control. In this model, life cycle definitions from the current CI class are combined with life cycle definitions from all parent classes in the CMDB class hierarchy. Child classes therefore extend parent life cycle definitions rather than overriding them. As a result, Business Application records can display Life Cycle Stage values that are applicable to infrastructure or hardware CIs but might not be semantically meaningful for applications. This behavior is expected and working as designed.\n\nIn contrast, in sys\\_choice inheritance definitions in child tables override the values in parent tables.\n\n**Parent Topic:**[CSDM reference](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/servicenow-platform/common-service-data-model-csdm/csdm-content-frame-reference.md)\n\n**Related topics** \n\n\n[Asset status values aligned to CSDM life cycle values](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/servicenow-platform/common-service-data-model-csdm/csdm-lifecycle-map-csdm-to-asset.md)\n\n[Asset and CI management](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/it-asset-management/c_ManagingAssets.md)\n\n"}}