Clarity does not allow to mark a task completed if ETC is non zero. I wrote a process but it does not trigger on completion if there is ETC. Any ideas would be appreciated.
I need to clear ETC and allow users to mark a task Completed.
Add a new checkbox attribute to Task Object: Clear ETC and Set to Complete
Then, have your process clear the ETC before setting Task Status to Complete. Could also create this as an Action, selectable from Task's Action pull-down menu.
What do you think?
In a real world scenario, if there is ETC on the task, then it is considered as not completed. Is there any business case to close a task as completed even when there is ETC on it?
If ETC is left on a completed task, expect issue to develop when updating schedule in OWB, MSP or Gantt.
For instance, if task is marked 'Completed' in MSP, and remaining ETC (Remaining Work) is converted to Actual Hours - which, upon saving back to CA PPM will generate an error message for resources expected to enter Actual Hours via timesheets.
If this were resolved, then one would run into scheduling issues,
Someone could suggest that one may want to maintain the original amount of work forecasted in the form of actuals + ETC, for some reason. But, this is what Baselines and Cost Plans built from Allocations or Assignments are for.
Actually in MSP when you mark a task 100% Complete, it captures the Actual Finish Date and then moves any Remaining Work (ETC) to Actual Work. If the project is set to Track Mode of PPM, upon save to PPM the Actual Work will be thrown away, and the Actual Finish Date, % Complete, and Status will be updated.
Ok – thanks for the update. An undocumented change, apparently.
In the past, one would get an error message. Just tried this on 14.2, classic interface, and it’s working as you describe.
However, I would still recommend that users not mark their tasks 100% complete in MSP. Why?
- MSP still converts remaining work to actual work
- When updating schedule, MSP will use these hours when updating subsequent task start/finish dates, giving incorrect results
It is still better, IMO, to set remaining work to zero in MSP, then update the schedule, then save back to CA PPM. IMO, it was better to have the interface generate an error on save, rather than to strip the actual hours off. The error message enforced proper handling of the remaining work.
I like the check box idea. This will work. Thank you!
Retrieving data ...