Business rule is running on the portal

[kali]

Hi All,

I have created a BR on the catalog ui policy and catalog ui policy action table such that if the user is not a admin they they should be able to see existing records or create/update new records in the backend tables , 

But i could see that the BR is working on the portal also , is there any way to restrict this in the backend table as well as on catalog builder

[Aditya_hublikar]

Hello @kali ,

You can control this crud operation using ACL also . Try acl for create/read/write .

if this helps you then mark it as helpful and accept as solution .

Regards,

Aditya

[SohamTipnis]

Hi @kali,

I think the issue is happening because Business Rules execute on the server side, regardless of whether the record is accessed through the backend or Service Portal.

I would suggest using ACLs instead of Business Rules to control access to the catalog_ui_policy and catalog_ui_policy_action tables. You can configure Read, Create, and Write permissions based on roles so that only authorised users can manage these records.

For Catalog Builder, you should also check the relevant Catalog Builder roles and permissions to ensure users have the required access.

This way, you can manage backend table access more effectively without unnecessarily affecting Service Portal functionality.

Let me know if this works!!!

If you find my answer useful, please mark it as Helpful and Correct. ‌‌😊

Regards,
Soham Tipnis
ServiceNow Developer || Technical Consultant
LinkedIn: www.linkedin.com/in/sohamtipnis10

[glideFather]

ahoy @kali,

first of all, if your business rule is applied on Catalog UI Policy and UI Policy Action tables, then it has nOTHING to do with Portal... it is triggered when a user is creating, updating or created these tables.

So the described behaviour from Portal must be done by something else.

It is not clear what you are trying to achieve nor what have oyu done, could you share the business rule to double check what you have there?

[kali]

Hi @glideFather ,

In the  before query business rule i have written that in the condition that !gs.hasRole('admin') && gs.isInteractive() and in the scripting i have written that current.addQuery('sys)id',-1)