question Re: Applying reference qualifiers on standard change template proposals in Developer forum

Applying reference qualifiers on standard change template proposals

Ashok Kumar Am1 — Wed, 25 Oct 2017 19:08:54 GMT

Hi there,

This is related to standard change template proposal screen. In our environment while proposing change template 'Configuration field' is one of the mandatory field.

And using Configuration field look up i am able to select any CI record .But my requirement here is to restrict CI selection only for certain class.

Is there anyway to apply reference qualifiers on change template proposal screen? Please help.

Thanks

Re: Applying reference qualifiers on standard change template proposals

Eric_Gauthier — Mon, 09 Jul 2018 22:35:07 GMT

We are wanting to do something similar. Did you ever get any solutions to this?

Re: Applying reference qualifiers on standard change template proposals

Daniel Peel — Thu, 11 Oct 2018 16:53:56 GMT

I'm guessing no one has found a way to do this?

Re: Applying reference qualifiers on standard change template proposals

Yifeng Zhang — Thu, 11 Oct 2018 17:14:53 GMT

I've never worked on this but can't you right click and define dictionary on the column ?

is this on the portal side or on the fullfillter UI? which table is this ?

Re: Applying reference qualifiers on standard change template proposals

Daniel Peel — Thu, 11 Oct 2018 17:38:30 GMT

Negative... they are not really fields you can right click on... because they are being stored in the template_values variable

Re: Applying reference qualifiers on standard change template proposals

Yifeng Zhang — Thu, 11 Oct 2018 17:53:32 GMT

I found the catalog item, but I'm on Kingston so the propose standard change form no longer has that CI item reference variable for me.

But, if that is a type of reference variable, you can go into the table contain all the variables, find that variable, give it a ref qual . I'm pretty sure you can do that with a reference variable.

You can give ref qual to either reference variable, choice look up, multi choice look up.. I think, off top my head

item_option_new is the table

Re: Applying reference qualifiers on standard change template proposals

tomas_hanousek1 — Thu, 11 Oct 2018 21:17:56 GMT

I implemented that. Let's say you want to make a reference qualifier to the for Configuration item on the template. Then you have to create the Before Query Business Rule that looks like this (on cmdb_ci table)

(function executeRule(current, previous /*null when async*/) {

	var targetName = gs.action.getGlideURI().getMap().get('sysparm_target');
	if (targetName.indexOf('change_request.cmdb_ci') > -1) {
		current.addQuery('install_status', 1); // installed
	}
	

})(current, previous);

When you click the magnifying glass, there is a parameter in URL sysparm_target that always differ a little bit. On the change form it's just change_request.cmdb_ci, and on change proposal, it has format like change_request.cmdb_ci.{sys_id format}. So you can detect it like this. Then you are able to provide only specific CIs after clicking on magnifying glass.

You should also take care about the putting the Name of CI directly to the field. You cannot find the CI in the list after clicking on magnifying glass, but when you put the name into the field, it behaves as valid. Here I suggest to use client script with AJAX to check if the user put there valid CI.

Re: Applying reference qualifiers on standard change template proposals

Parneet1 — Fri, 13 Mar 2020 14:43:50 GMT

Your answer should be marked correct. Your script saved some of us a lot of time. Thank you for posting your solution.

Re: Applying reference qualifiers on standard change template proposals

Rashmi47 — Tue, 21 Jul 2020 06:46:03 GMT

Thanks! tomas_hanousek

But how should we give the sysid as it keeps changing always. If you have implemented this change_request.cmdb_ci.{sys_id format}. Could you please help me getting the value for {sys_id format}. And if i only use change_request.cmdb_ci, it is causing an issue in other configurations.

Thanks in advance.

Re: Applying reference qualifiers on standard change template proposals

Shankar Manohar — Tue, 13 Oct 2020 13:27:19 GMT

CAUTION!!

The above solution worked but however this BR has to be turned off in our instances due to the excessive logging in our log table which occupied nearly 90% of data. We had to turn this off.

Please test it for logging in your sub prod instances if you are use this BR before migrating it to PROD.

Good Luck!!

Thanks & Regards

Shan

Re: Applying reference qualifiers on standard change template proposals

joeyfrease — Tue, 13 Oct 2020 13:38:02 GMT

**WARNING**

We implemented this on the group table and in about 2 weeks we nearly ran out of disk space. Please see the HI Support reasoning below. I know its not exactly the code above but just a warning...

- The source of this appears to be the following Javascript error: Root cause of JavaScriptException: java.lang.NullPointerException

-- This has been traced to business rule 'ResponsibleCAB_Template Ref Qualifier' which runs against 'sys_group' --

The error is caused by the following line:

var targetName = gs.action.getGlideURI().getMap().get('sysparm_target');

-- If this gs.action function is not accessible within the execution scope it will fail with the NULL Pointer error that we have sighted

-- This appears to be the scenario when this script is run from any non-interactive sessions, such as a background worker thread

-- At present these messages appear to contribute to around 99% of the table size

Re: Applying reference qualifiers on standard change template proposals

Community Alums — Thu, 02 Jun 2022 22:14:33 GMT

Has anyone found a solution to this issue?

Can we fix what is causing the error?

Re: Applying reference qualifiers on standard change template proposals

Daniel Peel — Fri, 03 Jun 2022 03:36:51 GMT

Try wrapping the whole thing in a try/catch, I don't see the errors in the log any more after putting the try/catch around it.

(function executeRule(current, previous /*null when async*/) {
	try {
	if (gs.action.getGlideURI().getMap().get('sysparm_target')){
		
		var targetName = gs.action.getGlideURI().getMap().get('sysparm_target');
		if (targetName.indexOf('change_request.u_approver') > -1) {
			current.addEncodedQuery(new StdChangeUtils().getMgrApprovers());
		}
		if (targetName.indexOf('change_request.u_avp_approval') > -1) {
			current.addEncodedQuery(new StdChangeUtils().getAvpApprovers());
		}
	}
	}
	catch (e){
		
	}
})(current, previous);

Re: Applying reference qualifiers on standard change template proposals

Sara Salerno — Wed, 13 Sep 2023 17:13:23 GMT

Do you happen to have the client script example to validate the CI once it is chosen if they do type the name directly?

Re: Applying reference qualifiers on standard change template proposals

janlendl — Thu, 25 Jan 2024 16:51:13 GMT

It looks like this approach is no longer possible

Standard Change template proposals do not honor reference qualifiers on change_request table fields - Support and Troubleshooting (servicenow.com)

especially if what you want to edit is part of std_chg_template_val_render

Re: Applying reference qualifiers on standard change template proposals

janlendl — Thu, 25 Jan 2024 16:53:57 GMT

I think this will only work if it doesn't belong to std_chg_template_val_render

please see article below

Standard Change template proposals do not honor reference qualifiers on change_request table fields - Support and Troubleshooting (servicenow.com)

Re: Applying reference qualifiers on standard change template proposals

josePinho — Tue, 06 Feb 2024 13:09:54 GMT

Amazing workaround!! It works perfectly to my requirement

Re: Applying reference qualifiers on standard change template proposals

josePinho — Tue, 06 Feb 2024 13:15:13 GMT

Did you found other way to reach this requirement?

Re: Applying reference qualifiers on standard change template proposals

Daniel Peel — Tue, 06 Feb 2024 15:03:46 GMT

This isn't a reference qualifier, it's a business rule... to replace the actions of a reference qualifier basically, and in UTAH this does still work, including the try/catch

Re: Applying reference qualifiers on standard change template proposals

Nidubrolr — Tue, 28 May 2024 14:33:34 GMT

how to use client script on the reference fields under the change request values field?