OOB business rule Actual Start/End Date Validation firing with empty work end date
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-26-2019 11:36 AM
We just upgraded our test instance to NY. I'm seeing an issue with the OOB business rule 'Actual Start/End Date Validation'.
I create a new change record and save it and see that this BR fires upon save with this message 'Actual Work End must be after Actual Work Start'. The log within the business rule shows that the actual end date gets a value of ''12-16-2019 02:23:25 PM" (not sure how this date is calculated and set on this field).
I have verified that the actual end date field is actually empty on the change record.
Any idea why this business rule might be firing?

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-27-2019 05:35 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-27-2019 07:27 AM
Yes, did that. No client scripts touch this field. There were a few script includes that have this field in the script but those are all related to the project management pieces that we are not using.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-26-2019 02:57 PM
very strange - the same BR does not fire (works as expected) in IE, but it does fires in Chrome.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-27-2019 04:49 AM
Hello
If this is a Chrome specific issue, perhaps it is related to caching.
Please try on an Incognito window of Chrome (essentially ignores the cache). If this works you will need to clear your All-Time cache for your main browser.
You can also make sure nothing from the Instance cache is messing with the behavior.
Type "cache.do" in the filter navigator to clear the instance cache. Be warned that this may cause temporary slowness.
Hope that helps!
If it did, please mark as Helpful and consider setting the reply as the Answer to the question, thanks!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-27-2019 07:23 AM
Tried clearing cache. did not fix the issue. Also, seeing the exact same issue in safari as well. just not seeing in IE alone.