- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-29-2023 09:21 AM
Hello,
I created a business rule that runs against the Reassignment History (u_reassignment_history) table.
The condition that I need to trigger against is when the new assignment value is "App Eng"
Here is what I added to the advance condition field:
current.u_new_value == 'App Eng'
App Eng is the name of the assignment group. Please see my image to review my business rule:
NOTE - I have a larger script but for now I just have the log statement just to see if the business rule gets triggered by my condition. So far it isn't working.
I want the business rule to be triggered anytime I change from one assignment group to "App Eng"
Is my condition formatted correctly?
Solved! Go to Solution.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-29-2023 10:18 AM - edited 11-29-2023 10:20 AM
You can dot walk from there - go to the bottom of the drop down - show related fields

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-29-2023 10:14 AM
Don't see it immediately, though why not using the Filter Conditions instead of a scripted condition?
Kind regards,
Mark Roethof
Independent ServiceNow Consultant
10x ServiceNow MVP
---
~444 Articles, Blogs, Videos, Podcasts, Share projects - Experiences from the field
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-29-2023 10:18 AM
Because I want to expand my condition. The full condition will look something like this:
current.new_value == 'sysID for App Eng' || current.new_value == 'sysID for azure operations'
&& current.task.active == true
&& current.correlation_id == ''
with the last two statements I need to dot walk. Can I do that from the condition builder?

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-29-2023 10:22 AM
Ah just a small misunderstanding of how the filter condition works from your end. Dotwalking is no issue at all for reference fields. I see others also have mentioned that now in the past few minutens.
Kind regards,
Mark Roethof
Independent ServiceNow Consultant
10x ServiceNow MVP
---
~444 Articles, Blogs, Videos, Podcasts, Share projects - Experiences from the field
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-29-2023 09:30 AM
Hi @DanielG
Y don't u use the condition field in when to run condition instead of writing it in advanced section.
Under when to run u can specify whether it is suppose to run before or after insert/update n below under condition u can select the field of new assignment value is App Eng. Then u der advanced u can put only log remove the value from condition field current.u_new_value.
Thanks,
Danish
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-29-2023 09:38 AM
1. I would suggest to go ahead & find the sys_id of the assignment group 'App Eng'. You can do that by going to -
- Application Navigator ( Left Side ) ==> Groups ==> find the group in list view by applying a filter or searching for it ==> right click on it & copy it's sys-id.
- Update your condition to current.u_new_value=="whatever-sys-id-you-got
2. You can also use the WHEN TO RUN section to put condition as follows by selecting appropriate field & its target value something as follows -
Do mark this response as HELPFUL / CORRECT which will help others & motivate me as well.