How to proceed with steps align the Business Unit table with CSDM 4.0 using lifecycle stage/states

[MihirG]

Hi team,

Here is my STR:

Short Description: CSDM 4.0 alignment for the foundation table business_unit.

Description: CSDM 4.0 alignment for the table business_unit, where the custom field "u_active" needs to be deactivated.

My Approach:

Analysis:
I have identified a total of 30 variables where the "u_active" field is used as a reference qual condition for selected Reference table:"Business Unit [business_unit]
". If we deactivate it, some catalog items will be impacted where those variable used. What would be the substitute in this case? I discussed this with the team, and they suggested that either we deactivate it, or, preferably, replace it with the correct lifecycle stage.

After further discussion, we concluded that we need to create a lifecycle mapping for the Business Unit table, as there is no existing entry for Business Unit in the lifecycle_mapping table. Once all the mappings are completed, we can replace the field with the OOTB lifecycle stage/state field.

However, replacement is the only viable solution because we have more than 20 variables, as shown in the variable form below:

Type | Reference
In the Type Specifications section:
Reference | Reference: Business Unit [business_unit]

Reference Qualifier condition:

Active: u_active is = true
Parent: parent is empty | ISEMPTY

What is the procedure? Kindly help me with that.

[Mathew Hillyard]

Hi @MihirG 

CSDM only provides baseline life cycle data for Product, Hardware, Logical (assets/CIs), Document and Location tables. It is based on status values as the point of Life Cycles is to align values that were previously spread across inconsistent operational and install status field values across the CMDB and elsewhere.

You cannot use Life Cycles as to create a mapping you must supply a legacy field name and field value - and these must come from a status field (e.g. phase, state, hardware status, operational status, install status). Technically the life cycle mapping table is looking for any choice list fields on the table. Business Unit contains neither a status field nor any choice list type fields so this option is not possible

I cannot see another OOTB option - you may have to stay with your custom active field. On this table, which only has 14 fields, I wouldn't class this as poor customisation, but necessary!

I hope this helps!
Mat

[mihirgupta]

Thanks for the Guidance.