- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-10-2025 07:11 PM
Hi everyone!
I'm encountering an issue with a Business Rule that’s designed to transition a case from Suspended to WIP when a comment is added. The Business Rule includes a condition that requires sys_updated_by (the updater of the record) to match the value retrieved via a dot-walk from the opened_for field (i.e., opened_for.updated_by).
What’s happening:
In my (PDI):
The configuration works as expected, and the Business Rule fires when the condition is met.In our Organization’s Dev Instance:
When I configure the condition as “Updated by is same as” and then dot-walk to the opened_for.updated_by field, the Business Rule does not fire. However, if I simply use “Updated by is same as Updated by” (without dot-walking), it works fine.
I’d appreciate any insights or suggestions on how to resolve this or adjust the configuration, so the intended logic is consistently met.
Thank you in advance!
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-10-2025 07:49 PM
Things to check
1) are you sure Opened for field is populated?
2) shouldn't you check the userID to check if the user who updated is the same as Opened For user
Updated by [SAME AS] OpenedFor->UserID
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
04-10-2025 08:08 PM
Hi @rhyannagood ,
It should update by same as opened_for.userid
like @Ankur Bawiskar mentioned
are you setting the value of the state to WIP in the actions?
check if the abort action is checked and uncheck it
please share the screenshot of actions tab in the BR
or check if there is any other BR or anylogic which is aborting the action of this
Please mark my answer as helpful/correct if it resolves your query.
Regards,
Chaitanya

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-10-2025 07:20 PM - edited 04-10-2025 07:20 PM
@rhyannagood Can you try and reduce the order of this BR to less than 100 and see if it fires?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-10-2025 07:37 PM
Hi Sandeep,
It's currently at '10' & it's still not working
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-10-2025 07:49 PM
Things to check
1) are you sure Opened for field is populated?
2) shouldn't you check the userID to check if the user who updated is the same as Opened For user
Updated by [SAME AS] OpenedFor->UserID
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
04-10-2025 07:53 PM
Hi Ankur,
I forgot to mention that I did attempt with the UserID & that didn't work. And yes, the ' opened_for' does populate! I'm honestly clueless as to what it could be.