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
yesterday
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
3 hours ago
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 hours ago
Hi @Prithvirajk ,
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.
