Loading...
Quick Links

Reply To: “Move Incomplete Parts to Status Date” adds time constraint – sometimes

Home Forums Discussion “Move Incomplete Parts to Status Date” adds time constraint – sometimes Reply To: “Move Incomplete Parts to Status Date” adds time constraint – sometimes

#418339
Tom Boyle
Guest

Larry/Dan,

Although you seem to have resolved the original concern, it’s important to note that you are talking about two completely different, though overlapping, status updating algorithms.

1. The subject of the original question – “Move Incomplete Parts to Status Date” – is a checkbox in the advanced calculation options with a default value of unchecked/false. This box (and the three other related boxes) affect the program’s immediate response to a user entry of partial progress on a task – i.e. a non-zero actual duration, remaining duration, or %complete. If this particular box is checked AND several other key conditions are met, then the start of the remaining duration (i.e. the Resume date) of the specific task will be automatically delayed to the Status Date. (The Resume date may be further delayed by logic restraints and other factors.) The other checkboxes are used to automatically manipulate the Actual Start, Actual Finish, and Stop dates around the Status Date (here be dragons.)

“Move Incomplete Parts to Status Date” will never impose a SNET constraint.

2. The Update Project action – “Reschedule uncompleted work to start after…” – is the one that automatically imposes either a SNET constraint or Resume date delay in the way that Larry describes. The date in this dialog is nominally independent from the Status Date (that is, the user can enter any date into the form, even if the Status Date is initially entered by the program.) Otherwise, the application of Resume dates is similar to the first option, though of course here it is done in bulk rather than one-at-a-time. Good luck, tom