Interested in a ServiceNow event built for developers? Registration for now[dev]26 is officially open!

CIs with Mismatched Operational Status and Life Cycle Stage

Henrik Jutterst
Kilo Sage

I've read this article: https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1703220 but I still don't understand WHY there is a mismatch AND what I should do to fix this.

I looked at one Business Application and ran a script to update to correct Operational status.

Script:

var gr = new GlideRecord('cmdb_ci_business_app');
gr.get('15a9bbbe1b016110a8aaeb11b24bcbfd');

gr.operational_status = 6; // Retired
gr.update();

 

XML before:

<life_cycle_stage display_value="End of Life">End of Life</life_cycle_stage>
<life_cycle_stage_status display_value="Retired">Retired</life_cycle_stage_status>
<operational_status>1</operational_status>
<sys_id>15a9bbbe1b016110a8aaeb11b24bcbfd</sys_id>

 

 

XML after:

<life_cycle_stage display_value="Operational">Operational</life_cycle_stage>
<life_cycle_stage_status display_value="In Use">In Use</life_cycle_stage_status>
<operational_status>6</operational_status>
<sys_id>15a9bbbe1b016110a8aaeb11b24bcbfd</sys_id>

 

 

We allow our application owners to update their Life Cycle State and Life Cycle State Status, but Operational Status is not synced.  Question: Where and how is that done?

 

Yes, I read that these statuses does not have to be in sync, but for us they have to. And also this is a metric in Data Foundations Dashboard.

0 REPLIES 0