Dot walking in condition builder does not work in Assignment Rules

[Rushikesh Mandh]

ctomasi pradeepksharma Assignment rules don't work when dot walking is done in condition builder. Is this a known bug? If the dot walking provision is provided, ideally it should work.

[darius_koohmare]

Hi Rushikesh,

This "issue" is seen across the platform anywhere the condition builder is present (ui policies, business rules, etc.).

The dot walking on these rules does not work in the condition if you do a changes function, because the rule is triggered by the update of the current record.

e.g. if you do a business rule on incident and set condition to parent.short_description changes, it will not evaluate because the update the BR would be 'listening' for is just that current incident, not its parent.

Using a scripted condition is required if you want to use changes on related (dot walked) records:

Dot walking is not working in UI policy conditions

Catalog UI Policy - dot walked conditions not working, need a workaround.

Similar to PRB647552 - [Catalog UI Policy] Dot walked condition not working.

[Rushikesh Mandh]

Hi darius.koohmarey,

I am not using any 'Changes' condition in condition builder, I am building a simple condition in assignment rule i.e. if configuration item.class is Server then Group is 'Server Support Group', which is not working.

[darius_koohmare]

Thanks Rushikesh.

I think a scripted condition would solve the problem. Script example

[Rushikesh Mandh]

Hi darius.koohmarey,

That's strange because ServiceNow itself doesn't recommend hard coding in scripts.