In our effort to align to CSDM we migrated our application services to the cmdb_ci_business_app table.
I know that the install_status is deprecated: https://docs.servicenow.com/bundle/washingtondc-servicenow-platform/page/product/configuration-manag...
But for now we still have to use it as we plan to migrate to the CSDM Life Cycle maybe next year. Unfortunately (?) our CAB decided we should only use ootb from now on as much as possible.
I couldn't find much but it seems other customers also have run into problems: https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0962866
There's also a weird ootb business rule on business app "Reset stale retired status value" that basically migrates the Retired Value on Insert/Update from 7 to 3. This design decision needs explanation by servicenow.
Why is that a problem for us? Over the years several teams (that are also long gone) implemented some dashboards, reports, notifications, acl, scripts, scheduled jobs, interfaces etc. on the more generic class cmdb_ci. This was never a problem since all child ci classes used the same install_status values. Now we'd have to refactor all of them just so we adhere to the "ootb choices" by servicenow.
You can see here that it is only different on business app
https://[yourinstancename].service-now.com/sys_choice_list.do?sysparm_query=nameINjavascript%3AgetTableExtensions('cmdb')%5Eelement%3Dinstall_status%5Elanguage%3Den%5ElabelSTARTSWITHRetired&sysparm_view=
