How do I sync Service Offering Fields to Individual CIs

Erick18
Mega Guru

According to the CSDM there is a way to use Service Offerings with CMDB Groups to be able to sync fields on individual CIs. Is there any documentation or guide on how to set up this functionality. I would like to populate the fields such as Owned By, Support Group and Managed By Group on the Service Offering and then those values would be synced to the underlying CIs. 

1 ACCEPTED SOLUTION

scott_lemm
ServiceNow Employee
ServiceNow Employee

Erick,

There are 2 mechanisms to populate data onto CIs as referenced by the Common Service Data Model. Please note the data in scope is limited to the following:

  • Managed by Group - the group responsible for the CI and/or the data of the CI
  • Support Group - the group used for routing Incident tasks
  • Change Group - the group used for routing Change tasks

The first mechanism is for Managed by Group only and populates a single Managed by Group on all CIs within a particular class. For example, all "Windows Servers" will have the Group "Win Server Team" populated in Managed by Group data field. This is meant to be a quick mechanism to ensure all discoverable/critical CIs has a Managed by Group populated. Details of setting this up in the CMDB Class Manager can be found HERE.

The second mechanism is for Managed by Group, Support Group, and Change Group. It uses the Technical Service Offering and a Dynamic CI Group to copy the values from the Technical Service Offering to all CIs that are managed by said Technical Service Offering. This is also an opportunity to stratify the Managed by Group within a particular CMDB Class thus overwriting the generic value assigned to an entire CMDB class (as outlined above in first mechanism). Details of setting this up can be found HERE.

NOTE: synchronizing data across platform objects impacts performance of the platform. The above mechanisms went through extensive testing to limit performance impact. It is greatly suggested that any additional/custom synchronization of data outside the scope of the above mentioned mechanisms be considered by their impact on performance.

Hope this helps,
Scott

View solution in original post

4 REPLIES 4

SebastianKunzke
Kilo Sage
Kilo Sage

You can not populate all fields you asked for. At the moment it will only work for the group fields (Managed by group, support group, change group)

Please follow the documentation.

Linda S
ServiceNow Employee
ServiceNow Employee

Data Synchronization -  is the capability you can use to push Support Group information from TSO thru Dynamic CI Group to individual CI's in the Dynamic CI Group....

scott_lemm
ServiceNow Employee
ServiceNow Employee

Erick,

There are 2 mechanisms to populate data onto CIs as referenced by the Common Service Data Model. Please note the data in scope is limited to the following:

  • Managed by Group - the group responsible for the CI and/or the data of the CI
  • Support Group - the group used for routing Incident tasks
  • Change Group - the group used for routing Change tasks

The first mechanism is for Managed by Group only and populates a single Managed by Group on all CIs within a particular class. For example, all "Windows Servers" will have the Group "Win Server Team" populated in Managed by Group data field. This is meant to be a quick mechanism to ensure all discoverable/critical CIs has a Managed by Group populated. Details of setting this up in the CMDB Class Manager can be found HERE.

The second mechanism is for Managed by Group, Support Group, and Change Group. It uses the Technical Service Offering and a Dynamic CI Group to copy the values from the Technical Service Offering to all CIs that are managed by said Technical Service Offering. This is also an opportunity to stratify the Managed by Group within a particular CMDB Class thus overwriting the generic value assigned to an entire CMDB class (as outlined above in first mechanism). Details of setting this up can be found HERE.

NOTE: synchronizing data across platform objects impacts performance of the platform. The above mechanisms went through extensive testing to limit performance impact. It is greatly suggested that any additional/custom synchronization of data outside the scope of the above mentioned mechanisms be considered by their impact on performance.

Hope this helps,
Scott

rafi438
Tera Contributor

Hi Scott,

Thanks for detailed answer. Both the mechanisms mentioned above are to populate data on CIs.

But is there a way to visualize which CI is connected to which service offering? (provided,the connection is done through dynamic ci groups and not manual)

 

For manual methods, we can establish the relationship manually for each CI-->mapped application service so that it can be shown(as shown in the picture)

But we would like to see the same kind of view for all CI's connected through dynamic CI Group to the top layer service offerings as well.