Restrict Configuration Item for Affected CIs for Change Request

VM3
Tera Contributor

Team,

While creating Change Request, Is there a way to restrict CI list which gets populated when selecting Affected CIs, or Impacted CIs ? 

We want to restrict some classes to pop up e.g. DNS name, IP Address etc. 

Please advise.

Thanks,

VM

1 ACCEPTED SOLUTION

chrisperry
Giga Sage

Hi there,

This can be accomplished by setting your desired CI Classes as 'Principal Class' from Configuration > CI Class Manager. Per the documentation, the Affected CIs related list you are referring to only displays those CIs whose class is set as the Principal Class.

If this answer is helpful please mark correct and helpful!

Regards,

Christopher Perry

If this answer is helpful please mark correct and helpful!

Regards,
Chris Perry

View solution in original post

5 REPLIES 5

chrisperry
Giga Sage

Hi there,

This can be accomplished by setting your desired CI Classes as 'Principal Class' from Configuration > CI Class Manager. Per the documentation, the Affected CIs related list you are referring to only displays those CIs whose class is set as the Principal Class.

If this answer is helpful please mark correct and helpful!

Regards,

Christopher Perry

If this answer is helpful please mark correct and helpful!

Regards,
Chris Perry

VM3
Tera Contributor

Thank you @Christopher Perry   for your quick response. 

This worked out good for Affected CIs. [i.e. I see classes got filtered to only the one I selected for Primary] , however for Impacted CI classes it still shows everything.

Is there any other option for restricting Impacted CIs ?

Please advise.

Thanks,

VM

I believe that is the expected behavior based on the documentation I had linked earlier:

"The Impacted Services/CIs pop-up window lists all CIs and provides standard filtering options. You can also save any filters you create to provide faster access to common CI searches."

With that in mind, you'll need to customize the AssociateCIToTask script include to restrict the Impacted CIs related list as well. Within the AssociateCIToTask script include, the OOB code in line 20 is:

if (addToTable === "task_ci") {

You need to modify that line of code to be this instead:

if (addToTable === "task_ci" || addToTable === "task_cmdb_ci_service") {

This customization should also restrict the Impacted CIs related list to Principal Class CIs in the way that Affected CIs related list was already successfully doing.

If this answer is helpful please mark correct and helpful!

Regards,

Christopher Perry

If this answer is helpful please mark correct and helpful!

Regards,
Chris Perry

VM3
Tera Contributor

Thanks a lot Christopher.