Clarity: Auto schedule option in OWB moves the plan more and more in the future as the auto scheduling action is run consequent times

Document ID : KB000048064
Last Modified Date : 14/02/2018
Show Technical Document Details


When a project is autoscheduled without resource constraints, even when doing a master/sub, the real resource is put into the cache. When autoscheduling with constraints in a master/sub a special master resource is put in the cache but it uses the same id as the real resource. If the cache already has a resource in it is not replaced. The problem is that the autoschedule with resource constraints ends up using the real resource thinking it's the master resource. The real resource has the availability taken from it but doesn't get reset before the next autoschedule which causes subsequent autoschedules to move into the future. This change makes sure that both the real resource and the master specific one gets reset before the autoschedule.

Steps to Reproduce:

  1. Create a project called Sub1

  2. Add two resources to the team

  3. Create two tasks and assign both resources to both tasks

  4. Create a project called Sub2

  5. Add the same resources as in Sub1

  6. Create two tasks and assign the resources to both

  7. Create a project called master and add both subprojects above

  8. Open the project in OWB

  9. Auto schedule the plan without "Resource Constraints" * Repeat this action as many times as needed to reproduce

Expected Result: The plan not to move in future

Actual Result: Every auto schedule action moves the plan more and more into the future





Resolved in Clarity 13.3 Generic Patch. Reference TEC605767
Resolved in CA PPM 14.1