Interested in a ServiceNow event built for developers? Registration for now[dev]26 is officially open!

Best Practice for Cloning GRC Workspace (Custom Shell and using OOB Core Tables)

desmond_teo
Tera Contributor

 

Hi Community,

We are looking to build a custom GRC/Risk Workspace for specific user personas on an on-prem ServiceNow instance (version: Zurich), without modifying OOB records or disrupting upgrade paths.


The goal is to create a parallel Experience that reads and writes to core GRC tables (sn_risk_risk, sn_grc_issue, etc.), mirrors the standard GRC layout, and resides within a custom application scope. Note that the page variant approach is not viable due to our business and organisational setup.


We have the following questions:


Q1. What is the recommended approach to set up the UX Page Registry and App Shell while maintaining feature parity with standard GRC Workspaces?


Q2. What is the cleanest strategy for transferring UI Builder page variants across Experience scopes (e.g., manual UIB copy/paste vs. duplicating sys_ux_screen records in Platform view)?


Q3. Are there specific UX Page Properties, List Categories, or Data Resources in OOB GRC that are known to break when referenced within a new custom Experience?


Any guidance or insights would be greatly appreciated. Thank you.

0 REPLIES 0