How to Restrict creation of scripts in a scope from other scope?

[Suggy]

I have created a custom app called HOTEL with a custom table in it. I want to allow other scoped apps read data in this custom table but dont want to allow creation of scripts like Business rules and client scripts in this table.

Hence I have unchecked ''Allow Configuration" and checked 'Can Read'.

But still, from other applications scope, developers are able to choose above table.

ie I have another app called 'AIR LINE'. From that scope, developers can create business rules, client scripts on the table created in HOTEL application.

I don't want that to happen. How to control?

As per docs that should not happen when 'Allow configuration' is not checked.

[PrabhakarCh]

@Suggy 

To restrict the selection of a table from other scopes in ServiceNow, you need to adjust the application access settings for your custom table. Go through below links. Still needed, you may raise a HI Case with ServiceNow for further help. 

https://www.servicenow.com/community/developer-forum/how-to-restrict-selection-of-table-from-other-s...

https://www.servicenow.com/community/developer-blog/securing-an-application-using-cross-scope-access...

=================================

If my response is helpful, click on 'helpful'.

Best,

PC

[Ankur Bawiskar]

@Suggy 

the tables appearing in that table list for business rule only rely on the "Accessible from" and "Can read" and not on Allow configuration

If it's accessible from All application scoped and Can read=true then only that table will appear

How the "Allow configuration" works is explained here for all components such as BR, Client Scripts, New fields, UI actions

Allow Configuration 

The option for "Allow configuration" is primarily used when you want to create the other 3 components on this table from outside the table scope

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

[Suggy]

Hello @Ankur Bawiskar 

the link that you shared clearly says 

"When Accessible from is All application scopes and Can read and Allow configuration are selected, out-of-scope applications can create Client Scripts for the table."

In my case, "ALLOW CONFIGURATION" is not selected in 'HOTEL' application.

Still developers who are in a different scope (AIR LINE in my case) can create Business rules and choose a table which is in HOTEL scope.

Docs also says clearly:

Allow configuration

- Clear the check box to prevent application designers from selecting this table when creating configuration records [Business rules for example]

[Ankur Bawiskar]

@Suggy 

The docs are confusing for Allow configuration.

As confirmed earlier by me to create BR it simply uses "Accessible from" and "Can Read" and doesn't rely on Allow configuration.

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