Dynamic CI Query Implementation

deepti mediratt
Tera Contributor

I am exploring and trying to understand Dynamic CI Groups and its implementation for our I/P/C processes. I am not seeing any documentation specific to Dynamic CI Groups and how it can be leveraged with Change Management process.  I have couple of questions:

 

  1. As I am learning about Dynamic CI Groups, it is my understanding that these Groups can be used for Incident, Problem and Change, correct?
  2. If we assign a Dynamic CI Groups to a Change Request as a CI or an App Service, how do Change approvals work? Is there something OOB in CHG workflow? For our process, our first level approver for a CR is CI owner and second level is App Service Owner.  But if I use Dynamic CI Group as CI or App Service, how will my CHG approvals be routed? Do we have something as Dynamic CI Group Owner? Do I have to customize my CHG workflow to fit in approvals when using Dynamic CIs?

would really appreciate responses to these questions and references to Dynamic CI groups documentation and not just CSDM. Thanks !

5 REPLIES 5

Cassandra Kittl
Tera Guru

To use Dynamic CI Groups on IPC - make the Dynamic CI Group an Application Service (and treat the same way as a mapped application service):

Step 1: Set up a CMDB Query with Filter on key attribute for the query.

Step 2: Set up a CMDB Group for each Sched (CMDB Query) to tie the CMDB Query to the group.

Step 3: Set up the Dynamic CI Group under Service Mapping and tie it to the corresponding CMDB Group.

Thanks Cassandra. But aren't Dynamic CI Groups and Application Service two different tables? Should I allow "cmdb_ci_query_based_service" Aka Dynamic CI Group on my Application Service field on the CHG form?

By making the Dynamic CI Group attached to the Application Service, you can put Application Service in the Configuration Item field (mark the Application Service as a principal CI).

Cassandra Kittl
Tera Guru

On step 2: remove the word "Sched". I pulled the steps from my instructions to create dynamic ci groups based on a patching schedule.