How to restrict loading of macro variables on RITM?

[Tejaswi Gundu]

Hi,

I want to restrict 2 of the macro variables from loading to RITM. Because as they are macro variables, it is taking much time to load on Service Operations Workspace.

I've removed those 2 macro variables on Sctask and it is working fine. Previously, we have faced the same issue for sctask.

I've tried the catalog client script but it will apply after the RITM has loaded. So, we need to stop the loading of macro variables.

Please give me suggestions to achieve this.

Regards,

Tejaswi G

[SanjivMeher · Accepted solution]

What do you have in the macro variable? Could something else be used instead of a macro in the catalog?

Not sure if you can remove the macro. You can probably hide it using catalog UI policy to not show up in RITM, but that wont restrict it from loading.

[Tejaswi Gundu]

@SanjivMeher , Thanks for your response.

Actually, we are having 2 macro variables used in particular catalog item and those 2 variables were taking much time to load as they are macro variables.

In Global instance it is working fine but when we search the catalog task with that particular catalog item which is having 2 macro variables, then it is taking much time to load.

I've removed those 2 macro variables from catalog task via workflow and now catalog task is loading within 10s. Same way I need to remove or restrict those 2 variables from RITM before loading.

I've tried writing query business rule on variable table but didn't get any lead how to achieve this requirement.

Please let me know if you have any suggestions on this.

Thank you!

[sanketgoyal]

To restrict the visibility of macro variables on a Requested Item (RITM) form in ServiceNow, you have a few options:

Client Script:
You can create a client script that sets the “Variable Editor Read-only” field to true. This will make the variable editor read-only, preventing users from modifying the variables.

Business Rule with QUERY Action:
Another approach is to use a business rule with a QUERY action. This allows you to add a custom query condition whenever people query the RITM table.
For example, you can restrict read access to specific RITM records based on certain conditions