- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-25-2016 09:28 AM
We have the hierarchy of Business services --> Service Components --> Sub-service components. - All managed manually.
We do not have a functional CMDB yet - and the work is in progress.
We use these services to link and categorise our Incidents / Problems / Changes.
We have some similar entries for Blackberry & Good technology (sub-service components) and Messaging (service component) - but need to get these unlisted.
I can't see any flag (Active/Inactive) to achieve this.
Nor can I see any retirement date that may be used to mark a service retired / obsolete.
Also - I don't want to delete them as that would disturb my historic data.
Any suggestions on how these can be made inactive or unavailable.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-25-2016 09:34 AM
Hi Sonal
Business Service table which is a child table to cmdb_ci doesnt have any active/inactive flags. In fact CMDB tables will not have active inactive flags. To retire a CI you must have operational plan on using operational_status and install_status from cmdb_ci table.
cmdb_ci is a parent to cmdb_ci_service table you can make use of operational_status filed and write rules not not show non-operative CIs. I haven't seen Service Components and Sub-Service component tables from out of the box. Are they custom? Are they extend from cmdb_ci_service?
Try using operational_status field from cmdb_ci (parent table) and add rules on activity of a component.
hope above helps
Thanks
Sashi
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-25-2016 09:34 AM
Hi Sonal
Business Service table which is a child table to cmdb_ci doesnt have any active/inactive flags. In fact CMDB tables will not have active inactive flags. To retire a CI you must have operational plan on using operational_status and install_status from cmdb_ci table.
cmdb_ci is a parent to cmdb_ci_service table you can make use of operational_status filed and write rules not not show non-operative CIs. I haven't seen Service Components and Sub-Service component tables from out of the box. Are they custom? Are they extend from cmdb_ci_service?
Try using operational_status field from cmdb_ci (parent table) and add rules on activity of a component.
hope above helps
Thanks
Sashi
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-25-2016 09:50 AM
Thanks Sashi,
This makes so much sense!! I was wondering - would this not be out-of-the-box functionality?
I am not a programmer - but have picked up a few things and can probably do the admin bits on Servicenow myself.
Just so you know we have a cascade update of Service component & Business service based on the Sub-service component selected.
So if I retire a Service component - what happens to the underlying sub-service components?
I can see retiring sub-service components should be fairly straight forward.
So to clarify - are you saying that I should add a reference qualifier on the field in which these services are selected?
Or are you pointing to business rules?
Please can you elaborate?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-25-2016 10:10 AM
Before providing a right solution, can you provide me details on
Where is sub-service component and service components data stored? provide me table names like u_cmdb_ci_service_component extends cmdb_ci_service?
Same for Sub-Service component? What is the relation between SubService Component --> Service Component --> Business Service?
Are the extending each other?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-26-2016 08:54 AM
Sure,
Sub-Service component (u_cmdb_ci_service_sub_comp) extends Business Service (cmdb_ci_service) [Can't believe but that's the way it is!! I was expecting Service Component here]
Service Component (u_cmdb_ci_service_comp) extends Business Service (cmdb_ci_service)
Business Service (cmdb_ci_service) extends Configuration Item (cmdb_ci)
Would that be sufficient information?