OOB business rule Actual Start/End Date Validation firing with empty work end date

[vktripper]

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?

[Ashley Snyder1]

Wanted to check on this screenshot being OOTB, as I checked an NY SN lab and PDI instance without modifications and my screenshot doesn't match yours, it does however match the OPs, perhaps this is some secret Orlando stuff we don't know about? 😉

Here's the screenshot from my NY PDI:

[Chaitanya Redd5]

Just Checked and found that the filter conditions of the business rules are different in Madrid and New York

Screenshot from Madrid:

screenshot from New York:

[Ashley Snyder1]

Very interesting since the OP stated they just migrated from Madrid to NY on their test instance.

OP, can you watch the field or check client scripts relating to that field?

[Noah Drew]

Whoops! Thanks for catching me on that Ashley and Chaitanya!

Only difference between my Madrid and NY instances is an 'm' vs an 'n' so I got the wrong one by mistake.

Given the change, we could also check if there are any other BR's that "touch" work_end in some way. Search the Business Rules by the change_request table and Script contains "work_end".

[vktripper]

I did and could not find any BR that was touching the work_end field in the script. The only ones that do except the one I have already noted are defined on the planned_task table.