UI Policy not working on native view of record producer

Swapnil Srivas1
Tera Contributor

‎03-31-2025 09:03 AM

While working on record producer, when clicking on "try it" UI action, the Catalog UI policies are not working on the view that appears(catalog_cat_item_view). The same catalog UI policies are working on the portal view. Is there a way we can fix it?

0 Helpfuls
  • 1,496 Views
22 REPLIES 22

Ankur Bawiskar
Tera Patron
Tera Patron

‎03-31-2025 09:11 AM

@Swapnil Srivas1 

it should work for both.

Try to ensure this is set to ALL

AnkurBawiskar_0-1743437513232.png

 

If my response helped please mark it correct and close the thread so that it benefits future readers.

Regards,
Ankur
✨ Certified Technical Architect  ||  ✨ 9x ServiceNow MVP  ||  ✨ ServiceNow Community Leader
0 Helpfuls

Shivalika
Mega Sage

‎03-31-2025 09:31 AM

Hello @Swapnil Srivas1 

 

The UI TYPe for this UI policy must have been set to "Mobile/Service Portal". That's the reason it's only showing up in service portal.  Change it to "All",  so that it also covers desktop. 

 

Kindly mark my answer as helpful and accept solution if it helped you in anyway. This will help me be recognized for the efforts and also move this questions from unsolved to solved bucket. 

 

Regards,

 

Shivalika 

 

My LinkedIn - https://www.linkedin.com/in/shivalika-gupta-540346194

 

My youtube - https://youtube.com/playlist?list=PLsHuNzTdkE5Cn4PyS7HdV0Vg8JsfdgQlA&si=0WynLcOwNeEISQCY

0 Helpfuls

Swapnil Srivas1
Tera Contributor

‎03-31-2025 09:42 AM

Hi, The UI type is selected to all.

0 Helpfuls

Shivalika
Mega Sage
In response to Swapnil Srivas1

‎03-31-2025 09:47 AM

Ok @Swapnil Srivas1 

 

Then it can be because of elements on which this UI policy is working . On what is that UI policy working. ? 

 

Many new features, such as advanced scripting, multi-row variables, and catalog builder improvements, are designed specifically for Service Portal.

 

Certain client-side scripts and UI policies may not function fully or consistently in the native view, as they rely on Portal-specific APIs and framework adjustments.

 

you might want to encourage them to transition to Service Portal for future-proofing and to avoid functionality issues, as some features may not behave consistently in the native view.

Kindly mark my answer as helpful and accept solution if it helped you in anyway. This will help me be recognized for the efforts and also move this questions from unsolved to solved bucket. 

 

Regards,

 

Shivalika 

 

My LinkedIn - https://www.linkedin.com/in/shivalika-gupta-540346194

 

My youtube - https://youtube.com/playlist?list=PLsHuNzTdkE5Cn4PyS7HdV0Vg8JsfdgQlA&si=0WynLcOwNeEISQCY

 

0 Helpfuls