Mpxj

Latest version: v13.6.0

Safety actively analyzes 682532 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 15 of 44

9.6.0

Not secure
* Add Planned Start and Scheduled Finish to project properties.
* Add attribute_types method to Ruby classes.
* Updated to use POI 5.0.0.
* Corrected source of Must Finish By project property when reading XER files or P6 databases.
* When reading PMXML files, ensure that the activity calendar is set before calculating slack.
* Remove unused field TaskField.PARENT_TASK.
* Ensure task Unique ID and task Parent Unique ID attributes are treated as mandatory when written to JSON.
* Fix an issue with Ruby gem where a task's parent was not being retrieved correctly in some circumstances.

9.5.2

Not secure
* Add Must Finish By date to project properties.
* Add support for the task attributes Longest Path, External Early Start and External Early Finish, and ensure they can be read from P6 schedules.
* Rename ProjectFile.getStartDate() and ProjectFile.getFinishDate() methods for clarity. Original method names are marked as deprecated
* Ensure that all activities in a PMXML file have a CalendarID attribute to ensure compatibility with older versions of P6.
* Ensure that the user's selected progress period is used to set the project's status date attribute when reading Asta PP files.
* Ensure that a task's Complete Through attribute is not advanced to the start of the next working day (the behaviour of Microsoft Project prior to 2007 was to report Complete Through as the start of the next working day. This change ensures MPXJ matches versions of Microsoft Project from 2007 onwards. Previous behaviour can be restored using the ProjectConfig.setCompleteThroughIsNextWorkStart() method).
* Deprecate task getSplitCompleteDuration() and setSplitCompleteDuration() in favour of getCompleteThrough() and setCompleteThrough().
* Improved the implementation of the TaskContainer.synchronizeTaskIDToHierarchy method.
* Update jsoup to 1.14.2.

9.5.1

Not secure
* When applying a baseline using ProjectFile.setBaseline, gracefully handle duplicate task key values.
* Handle missing values populating cost rate table from an MPP file.

9.5.0

Not secure
* Added support for reading baseline data from embedded baselines in PP files.
* Correct resource assignment percent complete values read from PP files.
* JsonWriter no longer writes attribute type information by default. (The original behaviour can be restored by calling setWriteAttributeTypes(true) on your JsonWriter instance).
* The MPXJ Ruby Gem now generates explicit methods to access attributes rather than relying on "method_missing" to intercept and act on attribute access.
* Don't write Assignment Task GUID, Assignment Resource GUID or Resource Calendar GUID to JSON.
* Don't write a value for Assignment Work Contour to JSON if the contour is the default value (i.e. flat).
* Don't write a value for Assignment Resource Request Type to JSON if the type is the default value (i.e. none).
* Don't write a value for Task Earned Value Method to JSON if the method matches the project default.
* Don't write a value for Task Type to JSON if the type matches the project default.
* Stop writing a default value (-1) for Parent Task ID to JSON if the task does not have a parent.
* Stop writing a default value (-1) for Task Calendar ID to JSON if the task does not have a calendar.
* When reading resource assignments from an MPP file, don't record Project's internal representation of a null resource ID (-65535), record the resource ID explicitly as null.
* For MPX and Planner files, don't write resource assignments for the "null" resource.
* Handle missing status date when reading P6 schedules from XER files or database.
* When reading MPP files, treat UUIDs which are all zeros as null.
* Deprecate the 10 Resource Outline Code get and set methods and replace with get and set methods which take an index argument.
* Provide a helper method (PrimaveraHelper.baselineKey) to encapsulate key generation for setting Primavera baselines.

9.4.0

Not secure
* Read custom value lists for resource custom fields from MPP files (based on a suggestion by Markus Höger).
* Added support for reading custom fields from Asta Powerproject files.
* Ensure short data type values are written to JSON files as numeric values.
* Ensure delay data type values are written to JSON files as duration values.
* Don't write zero rates to JSON files.
* Introduced a separator into rate values when written to a JSON file to make it clear that the value is a rate not a duration (for example: 5.00h is now 5.00/h).
* When writing an enum value of a JSON file, ensure we write the original enum name rather than the value return by toString. This provides more meaningful output (Potentially breaking change if you use the Ruby gem or consume the JSON output directly. Affected attributes are project properties: currency symbol position, time format, date format, bar text date format, schedule from, mpx file version; resource attribute: type).
* Ensure invalid cost rate table data is handled gracefully when reading from MSPDI files.
* Handle missing data when reading MSPDI files (based on a contribution by Lord Helmchen).
* Improve population of summary task names when reading from Powerproject PP files.
* Correctly read hierarchical resource outline codes from MPP files (based on a suggestion by Markus Höger).

9.3.1

Not secure
* Preserve multiple assignments between an activity and a resource when reading P6 schedules.
* Renamed WorkContour.isFlat to isContourFlat and WorkContour.isContoured to isContourManual.
* Include an entry for 0% in the WorkContour curve definition.
* Fix an issue where non-working days were not being treated correctly in date calculations if they happen to still have time ranges attached.

Page 15 of 44

Links

Releases

Has known vulnerabilities

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.