
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-16-2020 07:40 AM
Hi all,
In CSDM3.0 we can relate a Technical Service Offering to a Dynamic CI group. In such CMDB group reside CI's. My expectation is that a TSO related to a Dynamic CI group should be visible from the involved CI's.
Unfortunately: that's not the case or I do something wrong.
An other question: I like to use the TSO related to the CI's to determine the ticket solver group and the OLA of the TSO. Does anybody know if this works in an OOB instance?
Many thanks for reply's,
Ed
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-17-2020 01:24 PM
Hey Ed,
I think you are on the right track here, but the TSO is just like the BSO except in the scope of the service. For example, Technical Service Offerings are typically things like Windows Hosting - Gold Level, Local Area Network - AMEA or End User Computing - Executive level. There may or may not be Application Services that are consumed by the Technical Service Offering. There are however infrastructure CI's like servers, switches or specific computers that help provide that Technical Service Offering.
In the end, it really depends on the specific CI that is having the issue (it can be an infrastructure item, or Application Service). The routing of the ticket for support is based on the Configuration Item's Support Group or Assignment Group. The commitment to return the CI to working order is based on the specific Service Offering that is being impacted.
Hope that helps!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-03-2025 08:13 AM
Hi Dominic,
I saw the video but I am still struggling to actually create relationship between CIs in a dynamic CI group and a Technical Service Offering. Do we need business rule or script for that?
To add a bit of detail - we need all network devices to be related to specific TSO. We have query setup, dynamic groups created everything is related but I am still missing the part where the relationship between CI and TSO is created.
Thanks,
Jakub
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-05-2025 01:58 AM
Sorry, I've never actually done this. In the video (subject to using the right View), they just showed a section where you select and link.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-06-2025 10:56 PM
Hi Jakub,
If you want all Network Devices (Network Gear) linked to a dynamic CI group, the simplest solution is to create a CMDB Group add an encoded query to contain all your Network gears.
You then create a Dynamic CI Group and add the CMDB Group to this and link the Dynamic CI Group with your technical service offering.
I would suggest creating the Dynamic CI Group through the Application Service table, so you can use the UI form made for the purpose.
Keep in mind, that if you want the Dynamic CI Group and its CI's to inherit attributes from the offering both the offering and Dynamic CI Group need to be classified as "Technical".
You can also check out this article in the support potal. Troubleshooting: CSDM Data Sync for Technical Service Offerings (TSO) - Support and Troubleshooting
I hope this helps.
//Casper
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-13-2025 05:48 AM
Hi Casper,
actually, I was wondering whether CIs and TSOs can be related using Dynamic CI groups.
I already found out that not directly but thanks for the input.
J.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-07-2021 04:24 PM
With the Quebec release, ServiceNow makes it more cumbersome to create new query based Dynamic CI Groups (previously known as Technical Services). This was done by setting the default value for the table attribute to null. If you set the table attribute, you can still create legacy "Technical Services" using either the default view or your own view. I have an simple update set(attached) that restores the capability.
I find that using queries to build a list of CIs for a Service is still the best approach if you can't use top-down discovery. Unlike top-down Discovery, you can select any CI (including CIs that can't be discovered) and add it the Service.
When using the default table view(Configuration Item to Host Database View), you get CIs for all the applications that run on the servers you include in the query. Creating the query is easier and more resilient to change than having to explicitly list all your Application CIs in a CMDB group. If you want to create a Service where all the CIs are in the same class (e.g. All Windows Servers) you can use the table name for the class(or any other custom view) as the table name for the query.
After digging a bit deeper I was able to find a circuitous path to a new custom UI where you can use the Configuration Item to Host Database View and a filter to build the list of CIs for a Dynamic CI Group. If you start at Manage Technical Services -> Application Service, it bring up a list of Application Services using a new csdm_view view, selecting "New" will bring up the CSDM "Create an Application Service" UI. You can also get to the csdm_view from Configuration -> Application Services -> Application Services. This is annoying because that menu item used to take you to the default view for a list of Application Services. Now there is no easy way to get the default view for a list of Application Services.
This new interface (csdm_app_service.do) would be more relevant if you could customize it to show all the fields that are needed for managing Application Services. In the 1st tab called "Provide Basic Details" it wants to to go through all the possible CSDM relationships including a tab called "Parent Application Service".
This interface also exposes a field called "Number", which appears to be a way of giving Application services a Unique ID. I think this may only apply to Application Services created using the CSDM UI because I've never seen any of my Application Services with a value in the Number field.
When you get to tab 2,you can choose a method for populating the Application Service.
From here, you can defining a Dynamic CI Group using up to 3 different approaches(and I found that if you define more than one approach, they are all used to build a list of CIs. I was pleased to see that you can build a CMDB group using Queries that are similar to the original filters on "Technical Services". I am beginning to understand why they hid the original interface in favor of the more powerful approach, but a more direct way to create new Dynamic CI groups is needed.