- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-10-2017 06:46 AM
1. On a project record when the status is changed from "Work in progress" to any one of Pending/Open, the percent complete value of the project and project task changes to 0 from its previous value and also Actual Start/End Dates are reset to null.
2. If at all a project status has to be changed from Work in progress to Open/Pending then we would expect the percent complete and the actual start and end dates of project tasks to be as is but currently it is not the case. A project manager would expect the details to be retained even if the project is changed from work in progress to pending/Open.
Please let me know if this is expected behavior and the business reason behind the same.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-15-2017 10:05 PM
Hi Sreedhar
It is not recommended to backtrack from an in-flight project to back to Pending/Open. There is much behind the scenes logic triggered between tasks and states when states are progressed and it gets both technically and functionally awkward when backtracking states as each customer would want/expect something different to happen. I do not believe it is thoroughly documented what all will unravel how when backtracking states, instead a warning is posted to not do it. You may instead want to consider copying the project to a new one to start over. Best wishes.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-11-2017 01:09 PM
This is controlled by the PlannedTaskStateChangeHandler script include. You can see the code where the percent complete is set to zero and duration and actual dates are cleared.
This is not the first time some behavior in the platform has been noted to be noticeably different from what you might expect. My recommendation for a similar case was that there should be some system parameters that control whether these values should be "zeroed out" or not. If you want to keep them, you should be able to. And if not, wipe them out and move on.
Earl
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-20-2017 09:16 AM
I agree with Earl,
sometimes the OOTB mechanism isn't clear and it's very different from my expectation. If it would be possible to configure this behavior it would be great
Thanks Kelly for explanation
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-15-2017 10:05 PM
Hi Sreedhar
It is not recommended to backtrack from an in-flight project to back to Pending/Open. There is much behind the scenes logic triggered between tasks and states when states are progressed and it gets both technically and functionally awkward when backtracking states as each customer would want/expect something different to happen. I do not believe it is thoroughly documented what all will unravel how when backtracking states, instead a warning is posted to not do it. You may instead want to consider copying the project to a new one to start over. Best wishes.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-17-2017 10:05 AM
thanks Kelly