Asta Powerproject version 15.0.02.323 release notes
This topic lists the issues that have been addressed in the Asta Powerproject version 15.0.02.323 fast track release.
| Issue | 32140 | ||||
| Category | Progress | ||||
| Summary | Transferring progress from one project to another results in negative lag being applied to links in the destination project. | ||||
| Description | Before this release, a customer reported that when they transferred progress from one project to another, negative lag was applied to some links in the destination project. | ||||
| Resolution | The issue that caused negative lag to be applied to links has now been resolved. | ||||
| Issue | 32153 | ||||
| Category | Progress | ||||
| Summary | When entering values into the Actual Effort column, some negative Effort Remaining values result. | ||||
| Description | Before this release, a customer reported that when they entered values into the Actual Effort column, some allocations had negative Effort Remaining values. This happened if the Fill to progress line radio button was selected on the Progress tab of the Options dialog. | ||||
| Resolution | The progress period report date in the project in question was some way in the future, and Asta Powerproject was attempting to apply a completed section to allocations that stretched off into the future, beyond the current finish date of the allocations. This resulted in negative Effort Remaining values. Asta Powerprojectnow ensures that when completed sections are applied to allocations that have a calculated parameter of 'Allocation', they finish no later than the current finish date of the allocation. This means that allocations no longer end up with negative Effort Remaining values. | ||||
| Issue | 32163 | ||||
| Category | Filters | ||||
| Summary | Asta Powerproject will not open a project, reporting that 'SOT already exists'. | ||||
| Description | Before this release, a customer reported that Asta Powerproject was unable to open a project and that it reported 'SOT already exists' when attempting to do so. | ||||
| Resolution | Two summary tasks on the same bar contained tasks that passed the criteria of the active filter, which resulted in the bar being included in the filter results set twice. This caused problems when attempting to open the project. Asta Powerproject is now able to cope with objects that pass filter criteria more than once when opening projects. | ||||
| Issue | 32181 | ||||
| Category | Reschedule | ||||
| Summary | Task or milestone on the same bar as a summary task causes an error when rescheduling. | ||||
| Description | Before this release, if you rescheduled a project that contained a task or milestone on the same bar as a summary task, Asta Powerproject reported an 'An error occurred whilst rescheduling' error. | ||||
| Resolution | This error was caused by Asta Powerproject's logical path calculations attempting to calculate the float of the implied link between the summary task and the task or milestone, which resulted in the error. Asta Powerproject no longer attempts to calculate the float of implied links between summary tasks and tasks or milestones on the same bar. | ||||
| Issue | 32185 | ||||
| Category | Spreadsheet | ||||
| Summary | The Actual Quantity column allows only whole numbers to be entered when it refers to a specific progress period. | ||||
| Description | Before this release, a customer reported that if they configured the Actual Quantity column to refer to a specific progress period, any decimal numbers that they entered into the column were rounded up or down to the nearest whole number. | ||||
| Resolution | Numbers in the Actual Quantity column are no longer rounded to the nearest whole number if the column is configured to refer to a specific progress period. | ||||