- Популярные видео
- Авто
- Видео-блоги
- ДТП, аварии
- Для маленьких
- Еда, напитки
- Животные
- Закон и право
- Знаменитости
- Игры
- Искусство
- Комедии
- Красота, мода
- Кулинария, рецепты
- Люди
- Мото
- Музыка
- Мультфильмы
- Наука, технологии
- Новости
- Образование
- Политика
- Праздники
- Приколы
- Природа
- Происшествия
- Путешествия
- Развлечения
- Ржач
- Семья
- Сериалы
- Спорт
- Стиль жизни
- ТВ передачи
- Танцы
- Технологии
- Товары
- Ужасы
- Фильмы
- Шоу-бизнес
- Юмор
ServiceNow Expeditions #11 - Business Rules - After
After Business Rules run after the record is written. They react to committed data: read what changed, touch related records, and kick off downstream work. Think of them as the “post-save” layer where you reconcile side effects you can’t safely do in Before.
✳ 𝐓𝐀𝐊𝐄𝐀𝐖𝐀𝐘𝐒 ✳
After rules run after the record is committed and should react to the saved state.
Use after rules to update or coordinate other records, and keep current-record preparation in before rules.
Do not call current.update() in an after rule because it can retrigger after rules and create loops.
Run only on relevant changes by using "changes" and tight conditions.
Dot-walk safely by guarding nulls and validating references with isValidRecord().
Offload follow-up work with gs.eventQueue() or Async rules so the transaction stays fast.
Keep logic short to avoid long-running transactions that block the user session.
Order your after rules deliberately so they don’t conflict with or undo each other.
Use previous vs current intentionally to detect what changed and drive your logic.
✳ 𝐂𝐇𝐀𝐏𝐓𝐄𝐑𝐒 ✳
0:00 - Intro
0:40 - About the topic
1:40 - Diving into Use case #1
3:58 - Understanding what's stored in a list field
4:35 - The difference between newRecord() and initialize()
6:20 - Validate your sys_ids - What happens if a crew member dies?
7:30 - Showing Use case #1
8:22 - Validation of after business rules
9:12 - Showing the difference between using current and previous object
10:48 - Discussing inheritance of task table
12:12 - Diving into Use case #2
14:24 - Pointing out the way to retrieve the sysid of a record
16:35 - Introduction to the gs.eventQueue()
18:40 - Showing Use case #2
19:51 - Ordering of business rules
20:46 - Discussing long running transactions
21:28 - Takeaways and Outro
✳ 𝐑𝐄𝐅𝐄𝐑𝐄𝐍𝐂𝐄 ✳
SN Utils - https://www.arnoudkooi.com/
SN Execution Order - https://www.servicenow.com/docs/csh?topicname=r_ExecutionOrderScriptsAndEngines.html&version=latest
✳ 𝐃𝐈𝐒𝐂𝐋𝐀𝐈𝐌𝐄𝐑 ✳
This video is for educational purposes only. Information is provided as-is without any warranty of accuracy or completeness. Use of this information is at your own risk. We do not hold rights to third-party materials used under fair use for educational objectives. We are not liable for any loss or damage arising from your actions based on the content of this video.
Видео ServiceNow Expeditions #11 - Business Rules - After канала ServiceNow Expeditions
✳ 𝐓𝐀𝐊𝐄𝐀𝐖𝐀𝐘𝐒 ✳
After rules run after the record is committed and should react to the saved state.
Use after rules to update or coordinate other records, and keep current-record preparation in before rules.
Do not call current.update() in an after rule because it can retrigger after rules and create loops.
Run only on relevant changes by using "changes" and tight conditions.
Dot-walk safely by guarding nulls and validating references with isValidRecord().
Offload follow-up work with gs.eventQueue() or Async rules so the transaction stays fast.
Keep logic short to avoid long-running transactions that block the user session.
Order your after rules deliberately so they don’t conflict with or undo each other.
Use previous vs current intentionally to detect what changed and drive your logic.
✳ 𝐂𝐇𝐀𝐏𝐓𝐄𝐑𝐒 ✳
0:00 - Intro
0:40 - About the topic
1:40 - Diving into Use case #1
3:58 - Understanding what's stored in a list field
4:35 - The difference between newRecord() and initialize()
6:20 - Validate your sys_ids - What happens if a crew member dies?
7:30 - Showing Use case #1
8:22 - Validation of after business rules
9:12 - Showing the difference between using current and previous object
10:48 - Discussing inheritance of task table
12:12 - Diving into Use case #2
14:24 - Pointing out the way to retrieve the sysid of a record
16:35 - Introduction to the gs.eventQueue()
18:40 - Showing Use case #2
19:51 - Ordering of business rules
20:46 - Discussing long running transactions
21:28 - Takeaways and Outro
✳ 𝐑𝐄𝐅𝐄𝐑𝐄𝐍𝐂𝐄 ✳
SN Utils - https://www.arnoudkooi.com/
SN Execution Order - https://www.servicenow.com/docs/csh?topicname=r_ExecutionOrderScriptsAndEngines.html&version=latest
✳ 𝐃𝐈𝐒𝐂𝐋𝐀𝐈𝐌𝐄𝐑 ✳
This video is for educational purposes only. Information is provided as-is without any warranty of accuracy or completeness. Use of this information is at your own risk. We do not hold rights to third-party materials used under fair use for educational objectives. We are not liable for any loss or damage arising from your actions based on the content of this video.
Видео ServiceNow Expeditions #11 - Business Rules - After канала ServiceNow Expeditions
Комментарии отсутствуют
Информация о видео
16 сентября 2025 г. 11:20:21
00:22:35
Другие видео канала




















