Add Affected Configuration Items missing Configuration Class filter

[kirkr]

Our instance is missing the option to change the Configuration Class when selecting Affected CIs to a Change.

From both the documentation and a personal instance, this should be there to filter on class.

How can I add this to this window?

To navigate to this window, here are the steps:

• Open any Change with the State of New
• Open the Affected CIs related list
• Click the Add button

[Robert Wijnbelt]

This is likely caused by enabling the Bulk/Mass CI update plugins. These add behavior to limit the CI's you can pick to only those of the same class.

A workaround is to disable a client script on the change table called "Mass Update CIs - Sync CI Class".

This will prevent the CI class field from being set, and this causes the picker to show up in the list again.

Check if this is the desired behavior for you, since the Bulk edit is intended to make mass changes to CI's of only the same class.

[Chad Johnson]

Robert is on the right track.  However, the removal of the Configuration Class selection is actually controlled by the AssociateCIToTask script include.  In particular, the method listed below which is called by the _getURL method to help construct the URL used by "Add Affected CIs".

	/*
 	* If "Best Practice - Bulk CI Changes" plugin is active and task type is change_requests
 	*     parent class = ci_class populated on the change_request
 	*     if --None- is selected for ci_class, then cmdb_ci is returned
 	* else
 	*     parent class = cmdb_ci
 	**/
	getParentClass: function(chgReqId) {
		if (GlidePluginManager.isActive("com.snc.bestpractice.bulkchange")) {
			var chgReqGR = new GlideRecordSecure("change_request");
			if (chgReqGR.get(chgReqId) && chgReqGR.ci_class)
				return chgReqGR.ci_class;
		}
		return "cmdb_ci";
	},

[NJ2]

Hello,

Did you resolve this issue, I have enabled the plugin in my personal dev and still can see the configuration class on the UI page. But i cannot see it on my enterprise instance. I checked the code on AssociateCI Script include and they both look same in both the instances.  Please let me if i need to check something.

Thanks,

Niranjan.

[Nataraj Gedela]

I had the same issue and finally came to know that it is expected OOB behavior.
That option will be only visible when the CI selected for Change is one of the 52 defined classes.

You can change CI to any computer whose class is Computer, then Configuration Class Option will be available.

Below are the few classes for which that option appears.

Below article will give you more idea here.
https://hi.service-now.com/kb_view.do?sysparm_article=KB0713599