Issue with before and at or before operators in conditions fields on Washington

[Dubz]

Hi All,

I'm seeing issues with conditions created on date/time fields using the 'before' and 'at or before' operators on the Washington DC release. All existing conditions using these operators have lost their value in the UI, although the condition string still appears in the XML. Any attempts to create new versions of these conditions yields the same result. So far, my observation is that these conditions aren't functioning correctly either so this goes beyond just a UI issue. The Report application is unaffected so it seems to be just an issue with conditions type fields.

Is anyone else seeing this issue? I've seen this on 4 different Wasington instances so i'm slightly suprised to see no other complaints of this anywhere else. Any form using a conditions field is affected eg SLA definitions, business rules, state transition conditions...seems pretty significant.

Cheers

David

[Mark Manders]

I don't have this issue on mine. When did you upgrade? Have you logged a ticket with NowSupport about it?

[Dubz]

I've seen it on 2 client instances that were upgraded a number of weeks ago, a sandbox instance my company have and on a PDI i acquired just today. Where did you test this? My client have logged a case for it so i'm waiting to see what they come back with.

[Dubz · Accepted solution]

Apparently this issue is related to PRB1777164 which is fixed in Washington patch 4 hotfix 2 which will be released at the end of July. It's also fixed in Washington patch 5 hot fix 1 and patch 6.

[Mark Manders]

That explains the difference. Mine was already on 5.1