How to prevent work_start from being recalculated when Project State changes to "Closed Complete"?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 hours ago
Hello Community,
I am encountering an issue with the Project [pm_project] table regarding how dates are being handled upon closure.
The Issue: When a Project State is changed to "Closed Complete", the system automatically:
Sets the Actual end date (work_end) to the current timestamp.
Automatically recalculates the Actual start date (work_start) using the formula: Actual End Date - Planned Duration.
The Requirement: We want to keep the work_start date exactly as it was when the project moved to "Executing," rather than having it overwritten by a calculation when the project closes.
What I've Checked: I have searched for Business Rules and Client Scripts responsible for this logic but haven't been able to pinpoint the specific script or Script Include handling this recalculation.
Questions:
Does anyone know the specific Business Rule, Script Includeor Engine that triggers this date recalculation?
Is there a recommended "ServiceNow best practice" way to disable this specific recalculation without breaking the standard Project rollup logic?
Any guidance or pointers on where to look would be greatly appreciated!
