Request: cptAdjustment - enable Costs

[AronGahagan]

Request:

User can select one or more tasks and set a Target Remaining Cost.

• [x] reject completed tasks
• [x] account for all ResourceTypes
• [x] account for CostRateTables (rates & escalations)
• [x] reject Resources where AccrueAt <> pjProrated (3) (if pjStart then costs already accrued; if pjEnd then interferes with Actual Work already accrued).
• [x] account for CostPerUse (Unstarted tasks only; CostPerUse is determined by Assignment Start)
• [ ] ~account for Overtime Work/Cost~ this does not behave as expected*
• [x] incorporate into cptAdjustment_bas and cptAdjustment_frm
• [x] account for TaskType - user can override (Remaining Duration: Retain; Adjust; Trust)

* Details on Overtime

• adding overtime hours (task sheet only) respreads the allocation of regular work in a weird way
• overtime hours are somewhat front-loaded, no rhyme or reason - no matter what contour is selected
• when overtime hours (task sheet only) are removed, regular work is not redistributed as expected
• unit allocations are adjusted upwards when overtime is added; when overtime is removed the allocation % is retained and regular work is not leveled
• manual updates to the regular work after removing overtime work do not consistently update the peak units calc

Todo:

• [x] assign this issue
• [x] label the issue for enhancement or bug
• [x] label the issue with codemodule (so fixes can be aggregated and hotfixed together)
• [x] checkout appropriate branch and create topic branch
• [x] design, code and test
• [x] update codemodule x.y.z
• [x] update CurrentVersions.xml manually
• [x] commit changes prefix comment with Issue #XXX -
• [ ] merge topic into appropriate branch(es) and push
• [ ] delete topic branch

[AronGahagan]

sent to user for testing. it works, but is excruciatingly slow. need to optimize somehow.

[AronGahagan]

Using DoEvents after each oTSV.Value update instead of recalculating seems to be 1) accurate and 2) a bit faster. Added a progress bar so user doesn't think MS Project is just hanging, may alleviate some impatience.

[AronGahagan]

...moving form control updates (progress) and DoEvents after each oAssignment update also seems to be 1) accurate and 2) even faster...

[AronGahagan]

tested on 4 tasks 40d each, 16 resources each, ran in a few seconds. we have a candidate.