Life cycle mapping / install base items
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 hours ago
Hi,
struggling with Life cycle mapping and investigating how it is intended to be used. OOTB the only life cycle mapping available for legacy state in use is Install Base Item - Operational - In Use. However, I want the customer to be able to update the lifecycle status to "in warehouse", the legacy state still being "in use". It seems that it's not possible to have one legacy state corresponding to more than one lifecycle statuses.
What is the best practice here? I see that it's possible to create new legacy states, but is that really the way to go here? Thankful for pointers, references to information sources etc.
Best regards
Tanja
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3m ago
Hi @Tanja Holm,
Lifecycle Stage and Lifecycle Status are the preferred asset state model, while legacy states are maintained for backward compatibility.
Creating additional legacy states is generally not necessary unless required by a specific business process.
Best practice is to:
Use Lifecycle Statuses (for example, In Warehouse, In Use) for operational tracking.
Keep legacy states as generic as possible.
Use Lifecycle Stage/Status as the primary state model.
ServiceNow's recommendation is to manage asset progression through Lifecycle Stage and Lifecycle Status, rather than extending legacy states to represent every business state.