Day 26: DDIS - Client UI Actions using GlideRecord

in

Scan Check Type: Table Check [sys_ui_action]

The client side GlideRecord object is often inefficient, because it returns lots of unnecessary data. GlideRecord and g_form.getReference are both involved.

Use client data as much as possible to eliminate the need for time-consuming server lookups. The top ways to get information from the server are g_scratchpad, and asynchronous GlideAjax lookup.

This scan was developed using a table check with condition to identify any UI action records that are marked client side, active, and contain GlideRecord or GetReference. This rule is inspired by a QualityClouds check.

Download and import the XML to check it out in your instance! At the end of the month I will be bundling all the checks together.

Day 26 scan_table_check_da7e6ddd2f7311107caa93acf699b66c.xml