Hello Community,
Variable editors are really great way to show end user’s input to fulfillers. I get this question several times that, "hey Rahul, can we show variables on tasks other than catalog task" ?
Actually, there was a $500 bounty about this feature by
Let me give you an example, suppose, a requestor creates an incident via record producer. Out of the box, there is variable editor for task extended tables. Hence, you can show variable editor for target record of the record producer, in this case incident.
Reference of out of the box variable editor :https://docs.servicenow.com/bundle/orlando-it-service-management/page/product/service-catalog-management/task/configure-default-variable-editor.html
However, what about incident task? What if fulfiller working on incident task would like to see user’s input? Navigate to incident every time ?
Below is a way to leverage UI macro to show variable editor on incident task
Example case,
User Rahul creates an incident using record producer
Record Producer
Resulting incident record
Incident task
Interesting right ? Let’s break this and find out how I have achieved it.
UI Macro
Name:CascadeFormatter
Script
<?xml version="1.0" encoding="utf-8" ?>
<j:jelly trim="false" xmlns:j="jelly:core" xmlns:g="glide" xmlns:j2="null" xmlns:g2="null">
<g:requires name="scripts/js_includes_catalog.js" includes="true"/>
<g:requires name="styles/${new CatalogCssSelector().getVariableCss()}" includes="true"/>
<g:requires name="scripts/classes/ServiceCatalogForm.js"/>
<g2:evaluate var="jvar_catalog_item">
function eval_cat_item() {
var cat_item = "";
var catItemProducedGr = new GlideRecord("sc_item_produced_record");
catItemProducedGr.addQuery("record_key", current.incident);
catItemProducedGr.query();
if (catItemProducedGr.next())
cat_item = catItemProducedGr.getValue("producer");
return cat_item;
}
eval_cat_item();
</g2:evaluate>
<g2:evaluate var="jvar_cat_sets" jelly="true">
var jvar_cat_sets = "";
var gr = new GlideRecord("io_set_item");
gr.addQuery("sc_cat_item", jelly.jvar_catalog_item);
gr.query();
while (gr.next()) {
if (jvar_cat_sets.length > 0)
jvar_cat_sets += ",";
jvar_cat_sets += gr.variable_set;
}
jvar_cat_sets;
</g2:evaluate>
<div data-sn-macro-sys-id="${jvar_macro_sys_id}">
<g2:evaluate jelly="true"> var recordObject = new GlideRecord('incident');
recordObject.get(current.incident);
</g2:evaluate>
<j2:set var="ref" value="recordObject" />
<j:set var="jvar_producer_target_record" value="true"/>
<g2:client_script type="catalog_item" catalogItem="$[jvar_catalog_item]"/>
<g:inline template="catalog_ui_policy.xml"/>
<g2:render_component componentName="com.glideapp.servicecatalog.DefaultQuestionEditor"/>
</div>
</j:jelly>Formatter
Screenshot:
Navigate to incident_task and add this formatter at the place of your choice
Hopefully, this article would help to those who are searching for a solution to this problem 🙂
Hello,
I followed your guides to show the variables from Record Producer to the Task Case form (sn_customerservice_task)
But I met this error. It said the fields which come from the Variables are not filled in, even though on the form, the values of theses fields already appeared.
Error
Variables fields
Do you have any idea on this error?
Thank you very much!
Hi,
The key to above solution is the point that the parent record(incident in my case) should be create via a catalog.
To make this applicable on change request,
- I have created a record producer on change_request table with applicable variables such as description and short description as show in below Image
- Added the existing formatter to Change request form as shown below
- Created a new UI macro(named Change Task Variable Editor Custom) as shown below and added on Change task form
<?xml version="1.0" encoding="utf-8" ?>
<j:jelly trim="false" xmlns:j="jelly:core" xmlns:g="glide" xmlns:j2="null" xmlns:g2="null">
<g:requires name="scripts/js_includes_catalog.js" includes="true"/>
<g:requires name="styles/${new CatalogCssSelector().getVariableCss()}" includes="true"/>
<g:requires name="scripts/classes/ServiceCatalogForm.js"/>
<g2:evaluate var="jvar_catalog_item">
function eval_cat_item() {
var cat_item = "";
var catItemProducedGr = new GlideRecord("sc_item_produced_record");
catItemProducedGr.addQuery("record_key", current.change_request);
catItemProducedGr.query();
if (catItemProducedGr.next())
cat_item = catItemProducedGr.getValue("producer");
return cat_item;
}
eval_cat_item();
</g2:evaluate>
<g2:evaluate var="jvar_cat_sets" jelly="true">
var jvar_cat_sets = "";
var gr = new GlideRecord("io_set_item");
gr.addQuery("sc_cat_item", jelly.jvar_catalog_item);
gr.query();
while (gr.next()) {
if (jvar_cat_sets.length > 0)
jvar_cat_sets += ",";
jvar_cat_sets += gr.variable_set;
}
jvar_cat_sets;
</g2:evaluate>
<div data-sn-macro-sys-id="${jvar_macro_sys_id}">
<g2:evaluate jelly="true"> var recordObject = new GlideRecord('change_request');
recordObject.get(current.change_request);
</g2:evaluate>
<j2:set var="ref" value="recordObject" />
<j:set var="jvar_producer_target_record" value="true"/>
<g2:client_script type="catalog_item" catalogItem="$[jvar_catalog_item]"/>
<g:inline template="catalog_ui_policy.xml"/>
<g2:render_component componentName="com.glideapp.servicecatalog.DefaultQuestionEditor"/>
</div>
</j:jelly>Now it works on both change and change task
Change Request
Change Task
Remember: If you are creating change from template/interceptor then this may not work as it needs variables to work.
Hope this helps.
Regards,
Rahul
Hi All,
This is a very old post of mine and honestly never got a chance to work on this.
I made a very new generic solution for variable editor to work as close as how catalog task editor works.
Below are the steps to use :
- Create a formatter and add UI macro named "CustomVE" in the formatter.
- Add this formatter to your table.
- Create a new system property
- Name : customve.<current table name where you are using the formatter>.parent.field example : customve.incident_task.parent.field
- Type : String
- Value : The field name which represents the parent child relationship for example, incident task has field name "incident" which defines parent child relationship. as shown below
You are now good to go. This now supports save/update from both child and parent. In this case Incident and incident task.
Note: I did not check this for scoped application.
You can download this from share https://developer.servicenow.com/connect.do#!/share/contents/3490912_custom_variable_editor_for_reco...
Hopefully this will help all of you.
Observation : catalog UI policies / Catalog Client script doesn't work. Workaround : Use table level client script / UI policy client script
The issue you mentioned doesn't occur anymore
Variable attributes
Before saving
After Saving
It could be due to the old version of UI macro being used earlier.
Hello RahulPandey,
Thank you, I have downloaded and followed the same steps which you have mentioned in the article .
Mandatory Issue, is resolved. I thought I'll work in Scoped application, But unfortunately in not working in scoped application, May be it require few modifications to work for scoped.
I tested this solution for Scoped application, These are my observations.
- Update/Save functionality is working only for Reference, Select Box and Date fields. Its not working on Single line text, Multi line Text , Check box fields (Test only these 6 Fields).
- UI policies and Client scripts which were written on Record Producer to apply on Target record are not working on child Task level.
Really Thank you, great work. Need to see what to do with Scoped app.
Thanks and Regards,
Anil
Hi @ShrutiKamboj ,
To avoid error messages from mandatory fields, switch from checking the Mandatory checkbox directly on the variable record to using a Catalog UI policy. This works for me in a scope application.
