- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-21-2016 07:14 AM
The following condition works when the assignment group value selected from the assignment_group drop down list is 'Maintenace':
current.assignment_group.changes() && current.assignment_group.getDisplayValue() == 'Maintenance'
However, this condition does not work when the same 'Maintenance' value is autopopulated via an assignment rule
Further, this condition was used in replacement for my original condition (!current.assignment_group.nil() && current.assignment_group.changesTo(gs.getProperty('table.external_group'))) because I couldnt get that to work. The issue appears to be the use of the function changesTo().
Can anyone help please?
Solved! Go to Solution.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-21-2016 12:19 PM
Check the order field on your business rule. There is some coordination between assignment rules and business rules you should be aware of.
Check section 1.2.1 here

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-21-2016 08:56 AM
It may be working because the middle part with the changes() check is being ignored. See the note on section 2.1 here
http://wiki.servicenow.com/index.php?title=Business_Rules#gsc.tab=0
Note: Asynchronous business rules do not have access to the previous version of a record. Therefore, these GlideElement methods do not work with async rules: changes(), changesTo(), changesFrom(). |
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-21-2016 09:01 AM
I see your point so really I should only be using?:
!current.assignment_group.nil() && current.assignment_group.getDisplayValue() == gs.getProperty('table.maintenance.external_group')

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-21-2016 09:00 AM
Why not change this to a before rule if you can't get rid of that condition ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-21-2016 09:04 AM
That takes me back to the original issue at the top of this chain - condition not working if the assignment group field value is auto-populated with an assignment rule. Works fine when manually selecting from drop down list.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-21-2016 12:19 PM
Check the order field on your business rule. There is some coordination between assignment rules and business rules you should be aware of.
Check section 1.2.1 here