Change – Corrected Driving path identification when tasks have SS Predecessors
Detailed Explanation
Corrected an error calculating the driving slack when a predecessor has a Start-to-Start dependency. The prior version was evaluating the finish date of the predecessor vs the start date of the successor instead of the start date for both. The error was on ln188, col 64 of module SSIDrivingSlack
Build Release
13.4.7 – 01-19-2021
Change Number
13.4.CP02 – Predecessors flagging in Embedded Sub-Project
Correction, Change or New feature
Change – Change the way predecessors are marked as critical items
Detailed Explanation
In some instances, the predecessor flagging was only occurring on the external task in the active project instead of the source task in the predecessor’s project. The method of marking was changed to set an object to the predecessor’s project and its task according to a predecessor string indicating the predecessor is in a subproject
In GetPredecessors using Set exTaskPrj = GetObject(Task.Project) to set object to a task in the subproject
If SPTaskIDExists(exTaskPrj, exTaskPrj.Tasks(CLng(Mid(DepString, InStrRev(DepString, "\") + 1)))) Then
