Issues with Dot-Walked Updated_by in BR — Works in PDI but Not in Our Dev Instance

rhyannagood
Tera Contributor

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!

2 ACCEPTED SOLUTIONS

Ankur Bawiskar
Tera Patron
Tera Patron

@rhyannagood 

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.

 

Regards,
Ankur
Certified Technical Architect  ||  9x ServiceNow MVP  ||  ServiceNow Community Leader

View solution in original post

Chaitanya ILCR
Kilo Patron

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

View solution in original post

7 REPLIES 7

Sandeep Rajput
Tera Patron
Tera Patron

@rhyannagood Can you try and reduce the order of this BR to less than 100 and see if it fires?

Hi Sandeep,

 

It's currently at '10' & it's still not working

Ankur Bawiskar
Tera Patron
Tera Patron

@rhyannagood 

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.

 

Regards,
Ankur
Certified Technical Architect  ||  9x ServiceNow MVP  ||  ServiceNow Community Leader

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.