Hide Variables in the Approval Summarizer on the Approval form

NamrataJain
Tera Expert

‎09-04-2014 12:59 AM

Hi All,

We are working on MSP instance and we have same catalogs being shared across multiple clients.

We are able to hide the variables on the main form like change request using scripting and all but the same we are not able to do so in the Approval Summarizer that is available on the approval form.

Any help would be greatly appreciated.

Thanks you.

Best Regards,

Namrata Jain

Labels:
0 Helpfuls
  • 2,353 Views
5 REPLIES 5

marcguy
ServiceNow Employee
ServiceNow Employee

‎09-04-2014 01:06 AM

Those approval summarizers are UI Macros, there are seperate ones for each table or else they will fall back to approval_summarizer_default.



You will need to examine the code in these UI Macros and remove the parts referring to the variables.



I believe it's just this section:



<td valign="top" width="50%">

                                                                                                    <g:call function="variable_summary_approval.xml" question_name="${task.sys_id}"


  question_help_tag="${smart_description}" sc_req_item="${task.sys_id}"
  help_class="${jvar_line_color}"/>  

                                                                              </td>


0 Helpfuls

NamrataJain
Tera Expert
In response to marcguy

‎09-04-2014 01:34 AM

Hi,



Thanks for the quick response and I found that for our change request we didn't create any new approval summarize and default is being used.



The above code you gave is used in the "approval_summarizer_sc_req_item".



Not sure what changes should i do here to satisfy my conditions.



Sorry i might be sounding dumb , but I am tired trying to find the correct solution for this.



Once again I appreciate all your help.



Thank you.



Best Regards,


Namrata Jain


0 Helpfuls

marcguy
ServiceNow Employee
ServiceNow Employee
In response to NamrataJain

‎09-04-2014 01:39 AM

you could create a approval_summarizer_change_request UI Macro from the existing one actually then customise it away just for change request, then if you ever need to use the default one again elsewhere it won't be change specific and will continue to be out of the box.



On our one, we added lots of change specific fields, like risk, impact etc.


0 Helpfuls