- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-05-2025 04:00 AM - edited 09-05-2025 04:24 AM
Hi All,
There is a BR which check the condition if the assignment group is not empty and assigned to is empty the state should be assigned it is working fine in the workspace, but if record is created via record producer the state is not changing after updating some value it is getting updated. Even in some cases just saving the record it is getting updated,
what could be the reason..
Thanks,
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-05-2025 11:31 PM
Hope you are doing good.
Did my reply answer your question?
If my response helped please mark it correct and close the thread so that it benefits future readers.
Ankur
✨ Certified Technical Architect || ✨ 9x ServiceNow MVP || ✨ ServiceNow Community Leader
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-05-2025 04:06 AM
Hi @Devansh1
please share the BR.
It might be the checkbox on create/update or anything else, please share
This reply is 100 % GlideFather and 0 % AI. Disaster may appear. Deal with it!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-05-2025 04:12 AM
Hello @Devansh1 ,
Verify if your BR is set to run on: Before Insert and Update.
Please Mark Correct ✔️ if this solves your query and also mark Helpful 👍 if you find my response worthy based on the impact.
Regards,
Shruti
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-21-2025 04:53 AM
Hi @Devansh1,
Your Business Rule (BR) correctly sets the state to “Assigned” when assignment_group is filled and assigned_to is empty — but fails for records created via a Record Producer because of timing issues.
When created from a record producer, field values are often populated after the BR executes, so the condition isn’t met initially. Later updates or saves re-trigger the BR, and then it works.
Fix options:
Make the BR run Before Insert and Before Update with proper ordering (e.g., order < 100).
Adjust BR order so it executes after other scripts or flows that set the assignment group.
Add the same logic directly in the Record Producer script.
Use a Flow or post-insert script if population is asynchronous.
In short — it’s a sequencing problem. The BR runs before the necessary data exists on record creation via the record producer.
