Best way to set database instance's status as retired automatically?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-22-2022 07:33 AM
I am trying to understand how can i set the status of the Database Instances as retire, when they are running on retired servers. The status of the server is getting changed to retired by a human operator on my company but the CI's which run on it (Database Instances, Application Servers) won't update their status as retired automatically, at least on my Servicenow installation which is fully OOTB.
From what i saw, i could try to use Flow Designer to identify the Database Instances connected to the retired servers
but i don't know how to select the Database Instances from this result : the result is, of course, only relationship records.
Has anyone developed something like this or has an idea about how it can be done?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-23-2022 01:20 AM
Thank you Claude D. for your suggestion but, from what i saw, my quest is a little more complicated.
I saw that i cannot query directly the relations table (cmdb_rel_ci) because the status of the serves is on another one (cmdb_ci_server).
So it seems that i have to create
- a subflow to find the retired servers ID's in the cmdb_ci_server
- a subflow to find the Database instance ID's connected with those servers
- and then use a flow to update these Database Instances status on the final table cmdb_ci_db_instance

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-15-2023 02:17 AM
Useful info