I am new to Servicenow , What Best Practices to Follow in Each Project ?

spgfx07
Tera Contributor

Thursday

I am new to Servicenow , What Best Practices to Follow in Each Project ?

0 Helpfuls
  • 520 Views
6 REPLIES 6

Shaik Dimple
Kilo Sage

Thursday

Hi @spgfx07,

Along with what’s been shared above, a few things that helped me early on:

  • Avoid hardcoding sys_ids in scripts. Use system properties or look the record up by name.
  • Don’t use GlideRecord in client scripts. Use GlideAjax instead.
  • Try not to modify OOB records directly, since it can cause skipped changes during upgrades.
  • Test with impersonation as a normal user, not just as admin. ACL and role issues often show up only that way.
0 Helpfuls

Abhishek_W
Giga Guru

yesterday

Hi @spgfx07 

 

▶️  Understand the requirement before development
Before writing any code or configuring anything, understand what the client or business actually needs.
Keep in mind

- Understand the business problem.
- Identify who will use the functionality.
- Understand the current process.
- Identify the expected outcome.
- Check whether ServiceNow already provides an out-of-the-box (OOB) solution.
- Clarify acceptance criteria with the business analyst.

 

▶️  Follow out-of-the-box OOB functionality first
-Configure first, customize only when necessary.

 

▶️  Use proper Naming convention while creating Client script, BR, Script Include, comments in code ,etc.

 

▶️  Update set best practices
- Create separate Update Sets for each task/story.
- Give meaningful names.
- Keep only related changes in an Update Set.
- Complete the Update Set before moving it.
- Preview before committing.
- Test after deployment.
- Never make direct changes in Production unless emergency change process permits it.

▶️  Ask your architect before creating table, field, etc .


▶️  While deployment always check the all the changes in update set are required or not.

 

If this response helps you , Accept ✔️ the solution , mark it helpful 👍. 

Regards,

Abhishek

 

0 Helpfuls