PPM Enhancements for May 22, 2020
We are deploying the following enhancements to Changepoint PPM on Friday, May 22, 2020. This post is designed to help you understand how new and enhanced features can improve your PPM experience, and to guide you in making decisions about how to configure those features (if applicable). To facilitate training and testing ahead of this release, the features below will be deployed in Sandbox environments on Monday, May 18, 2020. The next Changepoint PPM Release is June 5, 2020.
For detailed information about these and all PPM Features, see the PPM Online Help.
To receive email updates about the latest enhancements coming to Changepoint PPM, click the Follow button on the Release Notes section page in the Daptiv Community.
New PPM Enhancements
New option to disable invite notification to converted users
We added a new option for administrators to disable the invite notifications that are sent when they convert an external resource to an enterprise member. This option only disables the invite notification, the new enterprise member will continue to receive other notifications from PPM.
Notable PPM Fixes
Exported Excel files do not match Capacity Planner
We fixed an issue where Net Availability in Excel exports did not match the data displayed in the Capacity Planner. This issue occurred when any workspaces were excluded from Net Availability calculations. These were workspaces were still being included in Net Availability calculations in Excel exports, which caused the mismatches. Now, Excel exports of the Capacity Planner will recognize the excluded workspaces and the data in those files will match the data in PPM.
Team Manager headers misaligned when viewing by Week
We fixed an issue in Team Manager where the column headers of the Resource Allocations pane were misaligned when viewing in Week mode. This issue made it harder to discern which column the headers belonged to. This issue no longer occurs and column headers in Team Manager are correctly aligned regards of the viewing mode.
Aggregate fields display inaccurate data after DA item import
This release fixes an issue where aggregate fields may display inaccurate data after a Dynamic Application (DA) item import. This issue only occurred with DAs that had existing items and only when users opted to recycle all of the existing items during the import. When this happened, aggregate fields would not recalculate values using data from the new items. This issue is resolved and aggregate fields will automatically recalculate using data from imported items.