2024R2 - Resolved Issues

Below is a summary of the main issues addressed by the Eclipse PPM 2024R2 release. Individual customer cases will be updated by the Support team through the portal. Cases will be closed out with customers upon confirmation that the issue has been resolved to their satisfaction.

Note: This page may be updated as new information becomes available.

The resolved issues in this release fall under the following categories:

 

 

Reporting

A bug prevented Budget items from displaying their true amounts when Financial Plans were viewed in the Excel Add-In. Instead, their amounts would display "0". Additionally, Actual Expenditures that were not created by user Timesheet entries would also display incorrect amounts of "0".

This bug has been fixed; the Excel Add-In will once again display correct Financial Plan values.

A bug caused incorrect values to appear in the "Status Update" field while running AdHoc reports. Specifically, an (Â) character would replace certain spaces that were entered into Status Updates in Eclipse PPM. This led to other invalid characters and symbols appearing in AdHoc report "Status Update" fields.

This bug has been fixed; invalid characters will no longer replace spaces and other characters in AdHoc report "Status Update" fields.

A bug caused users to encounter a "500 Internal Server Error" after refreshing the Financial Extract report in the Excel Add-In. The report would not refresh and error claimed it was due to a server connection issue.

This bug has been fixed; refreshing the Financial Extract report in the Excel Add-In will no longer cause an internal server error.

An issue prevented users from running the Resource Time Eclipse report. When users attempted to run it, an error message would indicate that the maximum count of records had been exceeded.

This issue has been resolved; the timeout limit has been increased to reduce the likelihood of future timeout errors.

A bug prevented users from successfully downloading certain reports that were created with Report Templates. After opening the downloaded file, the report would not contain any data. Instead, an error message claimed that an irrecoverable error had occurred during template processing.

This bug has been fixed; reports from Report Templates can once again be successfully downloaded with the expected data.

A bug caused formatting errors to Status Updates on Project Status reports. When users ran the report, any spaces between Status Update paragraphs were ignored.

This bug has been fixed; Status Updates will now be properly formatted when users run the Project Status report.

 

Risks

A bug prevented Risks Status Updates from appearing when users viewed the Risk's details. The Risk's "Status Update" field would remain empty even though its Status Update was recently updated.

This bug has been fixed; Risk Status Updates will no longer disappear while viewing a Risk's details.

 

Users

A bug prevented Eclipse PPM users from using the "User Group" filed while creating new users. Nothing would happen when the field was selected, which meant that users could not be added to User Groups upon entry into Eclipse PPM. The user creation process had to finish before new users could be added to User Groups.

This bug has been fixed; the "User Group" field is once again functional during user creation.

 

Work Planner

A bug prevented users from successfully importing Work Plans using Microsoft Project. This would create an error that claimed the XML file could not be processed.

This bug has been fixed; users can once again import Work Plans from Microsoft Project.