Unless you've installed the CSDM Activation plugin and enabled the mapping table, any updates to the Life Cycle Stage/Status fields will not automatically sync to the Operational Status field. The CSDM Activation plugin was originally a pre-requisite for using Data Manager, however we removed that dependency in the Tokyo release and allowed you to set your own Retirement Definitions.
Retirement Definitions allow you to specify the status fields you want to use to define retirement for a CI class. Any child CI classes inherit a parent CI class's Retirement Definition. If you set a Retirement Definition for a child CI class it overrides the parent class's Retirement Definition.
The Retirement Definition is used to set the associated status field(s) in a CI record based on the CI class, and the same definition is then used by the Archive and Delete policy types to act on retired CIs.
We ship OOB Retirement Definitions, however at least one definition must be active and a definition for the Configuration Item (cmdb_ci) class is set as always being active. You can change the default definition's configuration to use something other than the Life Cycle Stage/Status fields e.g. Operational Status - remember that all CI classes will inherit that definition unless you specify another definition e.g. using Operational Status = Retired for cmdb_ci_server.
Once you set a Retirement Definition and make it active you should see Data Manager set the associated status field on your CIs.
Note: unless you have a business requirement, there's no need to install and activate the CSDM Activation plugin and mapping table.
