- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-26-2018 12:49 PM
Hi everyone,
Here at the company we started with a list of applications in the Business Services list (cmdb_ci_services) and after some months, they decided to populate the same CI's in the Applications (cmdb_ci_appl), then we add a script include to "hide" the Business Services list from selection based on some categories.
They decided now to clean up the Business Services list by deleting some of the CI's there. The problem would be by deleting it will affect old incidents and change records that have those CI's in the form.
Did anyone already faced the same situation that could share how to solve this?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-12-2018 07:30 AM
Sounds like you are most of the way there already then. You should just update one or the other records (Applications or Business Services) for whichever is not desired to be used anymore, and set it to Non-Operational. Update your reference qualifier to only retrieve Operational CI's along with whatever other criteria you have in place
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-26-2018 01:21 PM
We ad similar issue. In our last project instead of using Application table, all the applications were stored in Business Service.
But then we migrated all the applications from Business Service later, but didnt delete the data from Business Service. We created another table Business Portfolio which is the parent of application and stores the business such as insurance, reinsurance, corporate, hr, finance etc
Please mark this response as correct or helpful if it assisted you with your question.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-26-2018 01:23 PM
Interesting.
I, unfortunately, do not have an answer or suggestion. Other than perhaps make a one-to-one relationship between the Application and Business Service. If you needed historical context, then you could traverse the relationship. Although, that seems like an unwieldy solution.
My interest is really in what caused the decision to use applications instead of business services. Did you evaluate the use of Business Applications (cmdb_ci_business_app) in addition?
I had developed a service taxonomy based on business services, but now, I am rethinking it. I am still trying to determine the best and proper use of applications, business applications, business processes, business services, technical services, oh my.
We do not own APM (but may in the future). We do own Service Mapping and hope to deploy it when Discovery is up and running successfully.
Like yourself, any experience anyone has with these issues is most welcome and would be most appreciated.
Larry
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-30-2018 09:24 AM
Hi Luiz - Ideally you would control the usage through a combination of status fields (status is non-operational or decomissioned, etc) and filters. You can create a reference qualifier to only select CI's (of any kind) that are "Operational"
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-30-2018 01:19 PM
Yes, we know that. But as I said, the problem is that they want to stop using the list we have in the Business Services list. Some of the CI's are duplicated showing in the Applications list and the Business Services list.
So, when someone start to type in the CI field, they will see 2 or more items with same name.
If for example, someone create an incident for software BLABLA, only one record should show in the CI field as:
BLABLA Application
Instead of:
BLABLA Applications
BLABLA Business Service
