---
title: GlideRecord And GlideRecordSecure Should Not Be Used In Catalog UI Policies. Script True
description: "Impact Area Performance Severity High Affected Element Catalog UI Policy **Affected element** For new instances, deprecated BPs will not appear. For existing instances, the new BPs will appear as ignored, and if enabled, their corresponding deprecated ones should be deactivated…"
url: "https://community-staging.qualityclouds.com/qcdocs/qc/servicenow-rules/gliderecord-and-gliderecordsecure-should-not-be-used-in-catalog-ui-policies-script-true/"
updated: "2025-03-21"
category: Rules
---

# GlideRecord And GlideRecordSecure Should Not Be Used In Catalog UI Policies. Script True

Impact Area

Performance

           Severity

High

           Affected Element

Catalog UI Policy

**Affected element**

For new instances, deprecated BPs will not appear.

For existing instances, the new BPs will appear as ignored, and if enabled, their corresponding deprecated ones should be deactivated to prevent duplicate issues.

| BP Deprecated | New BP | Affected Element |
| --- | --- | --- |
| SN-0348       | SN-GLIDERECORD-USAGE-CUIP-TRUE   |  Catalog UI Policy |

## Rule ID

**SN-GLIDERECORD-USAGE-CUIP-TRUE**

Impact

The client side GlideRecord/GlideRecordSecure object is often inefficient, because it returns lots of unnecessary data.

## Remediation

 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.

**Time to fix**

40 min