- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-19-2020 10:51 AM
Hello,
On our DEV and TEST instances (New York version) we are receiving the error message 'Actual end must be after Actual start' when we access the following forms:
- Demand (dmn_demand)
- Change (change_request)
- Project task (pm_project_task)
- User (sys_user)
The problem started suddenly.
Anybody knows what this could be? Looks like it is pointing to a UI Script 'PmClientDateandDurationHandler'
Thank you
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-25-2020 07:55 PM
Hello,
I opened a ticket at ServiceNow and it turned out it was because of a Business Rule 'Actual Start/End Date Validation' on the Change Request table that was never created during our upgrades until our latest NY upgrade. The person at Support was surprised because the Business Rule existed OOB in Madrid (our previous version).
We had a couple of changes that had their actual end date before the actual start date and at some point one of the changes started triggering the Business Rule in our DEV/TEST instances. By adjusting the dates the error stopped popping.
Fortunately, after our PROD upgrade to NY the errors never showed up.
Thank you for your guidance.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-25-2020 07:55 PM
Hello,
I opened a ticket at ServiceNow and it turned out it was because of a Business Rule 'Actual Start/End Date Validation' on the Change Request table that was never created during our upgrades until our latest NY upgrade. The person at Support was surprised because the Business Rule existed OOB in Madrid (our previous version).
We had a couple of changes that had their actual end date before the actual start date and at some point one of the changes started triggering the Business Rule in our DEV/TEST instances. By adjusting the dates the error stopped popping.
Fortunately, after our PROD upgrade to NY the errors never showed up.
Thank you for your guidance.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-19-2020 12:05 PM
we had similar issue
we deactivated existing UI script PmClientDateAndDurationHandler and created exactly the same ui script PmClientDateAndDurationHandler
(dont ask "why?", but this fix worked)
let me know if it works for you