Why to create custom table under the scoped application not on the Global application

[Yasin Shaik11]

Hello All,

When I am trying to create the custom table under the Global application on the header of the form the message is "ServiceNow recommends creating custom tables in scoped applications. To learn more about creating scoped applications, click here. "

Here my question is, I would like to know why ServiceNow recommends creating custom tables under scoped application not on the Global application is there any specific reason ? If Yes please share supporting documents so that i will share with client. 

[Aman Kumar S]

Hi @Yasin Shaik11 ,

The link that you have in your query itself has a good explanation of why and with a good example as well.

In brief, creating custom tables under scoped applications provides benefits in terms of isolation, versioning, security, customization portability, and adherence to best practices. It allows for a more controlled and efficient management of customizations within the ServiceNow platform.

[Ravi Chandra_K · Accepted solution]

Hello @Yasin Shaik11 

Greetings!

ServiceNow recommends creating custom tables in scoped applications rather than in the global scope for several reasons:

Isolation and encapsulation: Scoped applications in ServiceNow provide a way to isolate customizations and configurations from other parts of the platform. This isolation helps prevent conflicts and dependencies between different applications, making it easier to manage and upgrade the system. By creating custom tables within a scoped application, you can keep your customizations contained and avoid impacting the global scope.

Modularity and reusability: Scoped applications are designed to be modular and reusable. They can be easily packaged and distributed as standalone units, allowing you to deploy the application to multiple ServiceNow instances or share it with other organizations. Creating custom tables within a scoped application ensures that the tables and their associated business logic are packaged together, promoting better portability and maintainability.

Versioning and upgradability: Scoped applications have their own versioning and upgrade mechanisms. When you create custom tables in a scoped application, you can manage and upgrade them independently of the global scope. This enables you to make changes and enhancements to the tables without impacting other parts of the platform or other applications.

Enhanced security: Scoped applications provide enhanced security controls and boundaries. By creating custom tables within a scoped application, you can define specific security roles and access controls that apply only to those tables. This helps restrict access to sensitive data and prevents unauthorized modifications.

Governance and compliance: Scoped applications allow organizations to enforce governance and compliance policies specific to their applications. By creating custom tables within a scoped application, you can enforce data and process governance rules tailored to your application's requirements.

Overall, creating custom tables within scoped applications promotes better organization, isolation, modularity, security, and upgradeability. It aligns with ServiceNow's best practices for application development and helps maintain a stable and manageable platform environment

In this thread Mark explained Custom table creation impacts interms of licensing.

https://www.servicenow.com/community/developer-forum/custom-table-global-scope-and-licensing/m-p/140...

Help others to find a correct solution by marking the appropriate response as correct answer and helpful!!

Kind Regards,

Ravi Chandra.