Retire Configuration Items Subflow not updating Operational Status to retired

[NarayanaParella]

Dear Team, Does Anyone find that 'Retire Configuration Items' Subflow not updating the Operational status 

[ramyashree1]

You need to

configure a custom BR to achieve this.

[Tony Branton]

Retirement Definitions are used to specify the field to be used for retiring a CI record.  You can specify a Retirement Definition for a parent CI class (e.g. cmdb_ci) that will be inherited by CI child classes.  You can replace life_cycle_stage with operational_status in the OOB Retirement Definition for cmdb_ci, remembering to set the definition's active flag to True.

Note:

• If a child CI class has an active Retirement Definition, it's children will inherit from that definition.
• You need at least one active Retirement Definition covering the CI class you want to perform Retire/Archive/Delete operations on.
• I do not recommend using a custom BR as mentioned above ⬆️

[NarayanaParella]

Thank you Tony. Another question, if a CI returns back after retirement, How we can automatically put CI back into Operational Status?

[Tony Branton]

Assuming the retired CI is not archived or deleted, if the field used to specify retirement is updated e.g. Discovery updates the operational_status field, then it will not longer be in a retired state.  Depending on the filter specified in the Retire policy, the CI may end up being put back to a retired state when the policy is executed again in the future.

If the retired CI is archived or deleted, then a new CI record would be created e.g. Discovery found the CI and added it to the CMDB.