ui-policies

Automate ServiceNow Catalog UI Policy and action configuration via background scripts.

34|13|Updated Feb 6, 2026
One-click install
npx skills add https://github.com/Happy-Technologies-LLC/happy-servicenow-skills --skill ui-policies
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ui-policies
Source: https://github.com/Happy-Technologies-LLC/happy-servicenow-skills/tree/main/skills/catalog/ui-policies
Command: npx skills add https://github.com/Happy-Technologies-LLC/happy-servicenow-skills --skill ui-policies

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the configuration and management of ServiceNow Catalog UI Policies and UI Policy Actions to deliver dynamic, responsive catalog forms across complex scenarios.

Core Features & Use Cases

  • Create catalog_ui_policy records to drive conditional behavior on catalog items.
  • Create and associate catalog_ui_policy_action records to control visibility, mandatory fields, and read-only states, including scripted policies for advanced logic.
  • Use background scripts to link actions to variables, overcoming REST API limitations.

Quick Start

Create a basic Catalog UI Policy for a catalog item and link actions to variables using a background script.

Frequently Asked Questions about ui-policies

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate ServiceNow catalog UI policies and actions?

Automate ServiceNow catalog UI policies by creating catalog_ui_policy and catalog_ui_policy_action records to drive dynamic form behavior. Use background scripts to link actions to variables, overcoming REST API limitations for complex configurations.

What's the best way to make Service Catalog variables mandatory or read-only conditionally?

Configure conditional mandatory and read-only states for Service Catalog variables by creating catalog_ui_policy_action records. These actions control visibility and field requirements dynamically based on scripted or standard policy conditions applied to catalog items.

Why do I need background scripts to link UI policy actions to variables in ServiceNow?

Background scripts are needed to link UI policy actions to variables because ServiceNow REST API limitations prevent direct association. Running background scripts programmatically creates the required links between catalog_ui_policy_action records and target catalog variables.

Can I use scripted conditions for advanced catalog form behavior in ServiceNow?

Scripted conditions are supported for advanced catalog form behavior in ServiceNow. Apply optional scripting within catalog UI policies to handle complex form scenarios, enabling dynamic show, hide, mandatory, and read-only logic across catalog items.

Does this approach work for complex form scenarios across multiple catalog items?

This approach works for complex form scenarios across multiple ServiceNow catalog items. Administrators can create policy records, define actions, and apply scripted conditions to manage dynamic form behavior at scale using background scripts for variable linking.

What are the limitations of using REST API for ServiceNow catalog UI policy configuration?

The REST API cannot directly link UI policy actions to catalog variables, requiring background scripts as a workaround. Administrators must use background scripts to programmatically associate catalog_ui_policy_action records with target variables for complete policy configuration.