- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-25-2017 12:08 PM
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
Solved! Go to Solution.
- 6,311 Views
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-11-2018 02:17 PM
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-06-2024 07:03 AM
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-26-2024 09:19 AM
Anyone reading this thread in future should take note of this. Simple CYA to add the try/catch block to this to prevent the error logging issues.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-13-2023 10:13 AM
Do you happen to have the client script example to validate the CI once it is chosen if they do type the name directly?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-06-2024 05:09 AM - edited ‎02-06-2024 05:09 AM
Amazing workaround!! It works perfectly to my requirement
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-28-2024 07:33 AM
how to use client script on the reference fields under the change request values field?