What is the naming conventions need to follow in Custom app tables?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-22-2025 11:58 PM
What is the naming conventions need to follow in Custom app tables?
Also What are the precautions we need to take while building the custom app?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-23-2025 09:51 AM
Hi Prithvirajk,
Great question! Getting naming conventions and precautions right at the start really helps keep your custom app clean and easy to maintain later on 😊
Naming conventions:
For custom app tables, ServiceNow will automatically create the DB name with your application’s scope, like:
x_appscope_tablename (e.g., x_fin_expense_request).Keep labels business-friendly and clear, e.g., Project Request or Expense Report.
For fields, use lowercase with underscores (requested_for, approval_status) and avoid spaces or special characters.
Don’t use reserved prefixes like sys_, cmdb_, task_, sc_ etc.
Precautions while building the app:
Always work inside your Application Scope in Studio (keeps everything packaged and isolated).
Set up ACLs/roles from the beginning so your app is secure.
Be careful with Business Rules – for example, don’t use gr.update() inside an “on update” rule (infinite loop risk).
Prefer UI Policies for simple field behavior instead of client scripts (lighter and easier to maintain).
When designing fields, think about future reporting, use choice fields where possible instead of free text.
And of course, avoid duplicating or overriding out-of-box tables.
Following these basics will give you a strong foundation for a maintainable and safe custom app .
Hope this helps!
Thanks & Regards,
Muhammad Iftikhar
If my response helped, please mark it helpful & accept the solution so others can benefit as well.
Muhammad Iftikhar
If my response helped, please mark it as the accepted solution so others can benefit as well.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-23-2025 10:12 AM
Hi @Pruthviraj56 ,
Naming conventions for custom app tables:
Always prefix with the app scope name (example: x_company_appname_table).
Use lowercase with underscores to separate words.
Make names clear and meaningful (example: x_mc_hr_leave_request instead of x_mc_hr_lr).
Avoid abbreviations unless they are very common.
Don’t use special characters or spaces in table names.
Precautions while building custom apps:
Don’t reinvent the wheel – check if ServiceNow already has an out-of-the-box table or feature before creating new ones.
Keep the data model simple – don’t create unnecessary fields or tables.
Follow security best practices – apply proper roles and access controls (don’t give admin for everything).
Think of performance – avoid scripts or queries that run on every load unnecessarily.
Naming discipline – use consistent names for tables, fields, scripts, and UI items so others can easily understand.
Upgrade safe – avoid making changes in global or OOB tables unless needed; try to keep everything inside your custom scope.
Documentation – note down why a custom table/field/script was created. It helps a lot later.
👉 Basically: Keep it simple, consistent, and secure. Build only what’s needed and don’t break OOB stuff.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
hi @Pruthvriraj56,
Naming Conventions for Custom App Tables:- While creating custom app tables, use clear, meaningful, and consistent names. Table names should be singular, avoid spaces and special characters, and follow a standard prefix (such as application or organization prefix) to differentiate custom tables from system tables. Use a consistent naming style like CamelCase or PascalCase. Column names should clearly describe the data they store, avoid reserved keywords, and remain short and easy to understand.
Precautions While Building a Custom App:- Before building a custom app, plan the data model and requirements clearly. Apply the principle of least privilege when assigning user roles and permissions. Validate data inputs to avoid errors or duplicates. Design a simple and user-friendly interface. Ensure good performance by avoiding unnecessary logic or fields. Regularly test the app, maintain proper documentation, and design the app to be scalable and secure for future needs.
thankyou
If this response helped you, please mark it as helpful and accept the solution so it can help others too.
kumkumrai
