Skip to content

Commit 2bd454a

Browse files
Create Prompt for Best Practices for Writing Business Rules in ServiceNow (#29)
1 parent 3c5ed8a commit 2bd454a

1 file changed

Lines changed: 11 additions & 0 deletions

File tree

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,11 @@
1+
Assist me in understanding the best practices for writing Business Rules in ServiceNow. Please provide detailed guidance on:
2+
3+
Naming conventions: How to establish clear and consistent naming conventions for Business Rules.
4+
Script optimization: Tips for optimizing scripts for performance and maintainability.
5+
Execution order: Recommendations on setting proper execution order (before, after, async, and display) based on the use case.
6+
Use of GlideRecord: Best practices for using GlideRecord efficiently, including avoiding unnecessary queries and writing effective condition checks.
7+
Performance considerations: Key factors to ensure high performance, such as reducing query overhead, minimizing loops, and preventing redundant updates.
8+
Setting conditions and actions: How to correctly configure conditions and actions within the Business Rule to ensure it runs only when necessary.
9+
Choosing rule types: When to use before, after, async, and display Business Rules, based on different scenarios and requirements.
10+
Testing and debugging: Best practices for testing Business Rules, logging results, and avoiding common pitfalls like inefficient loops, race conditions, or unoptimized queries.
11+
Your response should help me write efficient, scalable, and reliable Business Rules while avoiding common mistakes.

0 commit comments

Comments
 (0)