Need to Understand Business Rules share Resources
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Need to Understand Business Rules share Resources for better understanding. Please share any resource if you have any.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi @vinodsannap,
You can refer to the below articles; this will help you understand Business Rule easily.
🧠 Mastering Business Rules in ServiceNow: Types, Use Cases & Best Practices
Types of business rules with example.
If you find my answer useful, please mark it as helpful and correct.
Regards,
Soham Tipnis
ServiceNow Developer || Technical Consultant
LinkedIn: www.linkedin.com/in/sohamtipnis10
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hello @vinodsannap ,
You can refer this community article :
https://www.servicenow.com/community/developer-articles/business-rule/ta-p/2329993
https://www.servicenow.com/community/itsm-forum/types-of-business-rules-with-example/m-p/712624
If this helps you then mark it as helpful and accept as solution.
Regards,
Aditya
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
The links above are good. If it helps, the way I keep the four types straight is by when they run:
- before: after the form is submitted but before the database write. Use it to set or check fields on current. You don't need current.update(), the changes save automatically.
- after: after the write. Good for updating related records or firing events.
- async: also after the write, but as a background job so the user isn't waiting. Order isn't guaranteed if several touch the same record.
- display: when the form loads, just after the record is read. Mostly used to pass server data to client scripts through g_scratchpad.
Easiest way to make it click: in a PDI, create one of each on incident with a gs.info() line, then save a record and watch the system log.