CIs with Mismatched Operational Status and Life Cycle Stage

Henrik Jutterst · 3 weeks ago

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.

Henrik Jutterst · 2 weeks ago

And also. How are we supposed to update operatinal status when it is locked? See this example:

Damhoej · 2 weeks ago

I think you should talk to your admin.
The field Operational Status is not locked (read only) in a OOB instance and should be editble if you have the correct rights.

SGienow · 2 weeks ago

You're not supposed to.. the legacy value should probably be removed from the form entirely, along with the other legacy lifecycle values, and also make sure that you have the lifecycle mappings setup correctly. See my other post below, for the PI2.0 behavior and non-asset sync KB.

Damhoej · 2 weeks ago

@Henrik Jutterst wrote:
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.

Operational Status can be used to mark a CI in a temporary status, such as if the server is in maintenance you can set the operational status to non-operational to indicate that the server is installed and in production, however at the moment it is unavailable.
It is hard to find documentation of the exact use of Operational Status, but som health dashboards use this status field (as far as I remember)