2025R1.2 - Resolved Issues

The 2025R1.2 version of Eclipse PPM will be deployed on Wednesday, November 5th, 2025. This minor release will address the following high-priority customer issues. Click on any of the resolved issues below to learn more about them:

 

Users were unable to edit the Financial Plan under Project > Financial Plan > Edit. An error occurred when attempting to open or modify the Plan if the Year View selection was set to Calendar Year instead of Fiscal Year.

This issue has been resolved; Financial Plans can now be opened, edited, saved regardless of whether Fiscal Year or Calendar Year is selected.

An issue caused an error when editing or saving a Resource Type that included a Rate containing decimal values. The error occurred both when assigning a Resource Type with Default Rate containing a decimal value and when updating the Rate Card information directly under Administration > Resource > Rate Cards, due to improper handling of decimal inputs in the Rate validation process.

This issue has been fixed; Resource Types and Rate Cards can now be created or updated successfully using decimal Rate values without any errors.

An issue prevented users from seeing results when using the Quick Search functionality across Project, Program, Issue, Risk, and Task modules. Performing a text search and selecting any of the “Show All Results” options previously returned no results because the API was not returning records.

This issue has been fixed; Quick Search now returns results correctly across all modules.

An issue prevented users from successfully copying existing Filters across various modules, including Program, Project, Issue, Risk, Task, Notes and Assignments. When attempting to Copy and Save a Filter, an error message appeared.

This occurred due to an issue with how Filter IDs were handled in the JSON payload during the copy process, causing the API request to fail.

This issue has been fixed; Filters can now be copied and saved successfully without any errors.

An issue caused errors when submitting Project Approvals (Baseline, Status, or Financial) that included certain supplementary data fields, such as Health Indicators or Last Status Modified Date. Submissions with these fields triggered validation errors related to handling of string or decimal values in the supplementary data.

The issue has been resolved. Project approvals (Financial Plan, Project Status and Baseline) can now be approved and saved successfully with all supplementary data fields.