Browse our Products

Aspose.Tasks for Java 23.5 Release Notes

All Changes

KeySummaryIssue Type
TASKSNET-10892Add Prj.AutoCalculateAssignmentCosts property to allow control of auto calculation of Asn.RemainingCost and Asn.CostEnhancement
TASKSNET-10893Fix ‘TimeSpan overflowed because the duration is too long’ exception when reading project with cost resource from XER formatBug
TASKSNET-10891Fix reading of Tsk.Work field when reading project from Primavera XML format: should read from ‘Planned Labor Units’ instead of ‘At Completion Labor Units’Bug
TASKSNET-10888Fix ‘Cannot find any fonts installed on the system’ error when saving project to MPP when system font folders cannot be accessed by the applicationBug
TASKSNET-10886Fix reading of working times when reading calendar exceptions from XER formatBug
TASKSJAVA-1983Resource usage is wrong importBug
TASKSJAVA-1982Resource usage is not imported correctlyBug
TASKSNET-10878Fix incorect rendering of Chinese characters in output JPG file when converting file in LinuxBug
TASKSNET-10829Fix reading of project from XER format with non-default separator charBug

Public API and Backwards Incompatible Changes

The following public methods were added:Description
com.aspose.tasks.Project.getAutoCalculateAssignmentCosts()Gets whether assignment cost and remaining cost should be auto calculated using assignment’s work and resource rates.
com.aspose.tasks.Project.setAutoCalculateAssignmentCosts(boolean)Sets whether assignment cost and remaining cost should be auto calculated using assignment’s work and resource rates.
The following public enumerations were added:Description
com.aspose.tasks.Prj.AUTO_CALCULATE_ASSIGNMENT_COSTSDetermines whether assignment cost and remaining cost should be auto calculated using assignment’s work and resource rates.
com.aspose.tasks.PrjKey.AutoCalculateAssignmentCostsDetermines whether assignment cost and remaining cost should be auto calculated using assignment’s work and resource rates.

Breaking change notice

Related issue: TASKSNET-10891 - Fix reading of Tsk.Work field when reading project from Primavera XML format: should read from ‘Planned Labor Units’ instead of ‘At Completion Labor Units’

Before 23.5 Task.getWork() was read differently when reading project from PrimaveraXML and XER formats: for PrimaveraXML it was read from ‘At Completion Labor Units’ Primavera field, for XER format it was read from ‘Planned Labor Units’ field. Now Task.getWork() is read from ‘Planned Labor Units’ field. ‘At Completion Labor Units’ can be calculated as a sum of Task.getActualWork() and Task.getRemainingWork().

Correspondence of Primavera fields to properties of com.aspose.tasks.Task entity can be found here.

Examples and additional notes

Related issue: TASKSNET-10892 - Add Prj.AutoCalculateAssignmentCosts property to allow control of auto calculation of Asn.RemainingCost and Asn.Cost.

Previously, assignment’s RemainingCost and Cost properties were calculated automatically using resource’s rate and RemainingWork, Work properties. Now AutoCalculateAssignmentCosts can be used to turn off auto calculation of assignment’s costs.