Is the vision that Life Cycle Stage and Life Cycle Stage Status will be CMDB admin administered fields, or are we expected to use legacy Status fields in our forms and allow the life cycle mapping to take over behind the scenes?

[LM5]

I'm trying to figure out if/how/when Life Cycle Stage and Life Cycle Stage Status need to be surfaced in the CI forms.  When I look at freshly built San Diego dev instance, it's not visible in any CI default view that I looked it.  In the list view, I can see the new fields, but they have no values.  The dev instances are no help as they don't look they've implemented it there yet.

One option is to do the mapping of legacy fields to the new Life Cycle fields but not show those new fields at all.  Another option is to show the newly mapped Life Cycle Control value (ex: Hardware - Defective - In Stock), with nothing editable.  Another option is to show the Life Cycle fields broken out in fields and make them selectable/editable, and dump the legacy fields once the data is migrated across.

Has anyone tackled how to approach this yet, or seen any guidance? 

[CMDB Whisperer · Accepted solution]

For now you should continue to use the existing fields even after opting into the CSDM lifecycle fields.  You do not need to add them to any forms.  If you do add them, you should make them read-only, since for now no user should be selecting them on records where other status fields are enabled.  Since the synchronization is only one direction, ServiceNow doesn't support direct use of these fields yet.  The longer term plan is to support this, but it will require a refactoring of their existing applications in order to support the business logic shifting to Lifecycle Stage/Status.  In addition, customers will need to accommodate this on their own custom apps and configurations (e.g. reference qualifiers, etc.)  My recommendation is that if you do decide to enable Lifecycle Stage/Status now, use it as an opportunity to begin refactoring your own configurations to use Lifecycle Stage, while still having your users use the existing fields.  That way it will make it more seamless when you migrate to the Lifecycle fields in the future.

[LM5]

Paul, thanks for the guidance.