Click here for an overview of the PPM Pro release process.
The table below lists this month's product release dates.
|Release Notes published||January 3|
|System released to sandbox environments||January 10|
|System released to production environments||
Releases are deployed during the standard maintenance windows.
- Features that are ready will enter GA status in the first month's release of each calendar quarter: January, April, July, October. There will be an occasional variance from this schedule. You can enter a support request to move a beta feature into your production environment.
- You can request that beta features be enabled in your production environment by entering a support ticket. Please note that any issues you find will be handled during the normal development cycle.
- Planview sends out status emails in advance of planned releases/updates. These alerts include the date and time window of the update, as well as a link to the release notes that include a list of the issues addressed in the update/release. To subscribe to these alerts, please go to https://status.planview.com/ and click the Subscribe button.
- We hold a live product release webinar - typically on the Wednesday before the production release. This webinar will be hosted by PPM Pro product management and consulting personnel, and will include time for Q&A. Click here to register for the January 15th release webinar.
- Inner circles are offered as a way for our interested customers to collaborate with PPM Pro Product Management and each other, provide feedback on PPM Pro product capabilities, and guide new feature development. Click here for more information or to register.
Release planned for Friday January 31, 2020, pending QA approval.
|Function Area||ID||Release Note Description|
|Access||Improved. Better handling of certain transactions that were causing interrmittent 500-type errors to occur.|
|Dashboards||889628175||Fixed. Dashboard expiration alerts being sent as expected.|
|Notes, Status Comments||962927214||Improved. Notes and Status Comments now accepts 1M bytes, plain text, includes spaces, line returns. Previously, these fields were limited to 4000 characters, which was preventing common actions such as pasting in text, because the (small) size limit had been exceeded.|
|Rich text editor||963125218||Fixed. Descriptions can be updated without loss of data, as expected. Previously, description fields that had ordered lists lost data upon saving.|
New Feature Matrix
For more information…
Current functionality (Rolling beta)
|Beta - currently available in sandboxes only||
WS API calls using getEntityFields
Part of an ongoing effort to make our field types consistent. When using getEntityFields, Description fields for all entities will be returned with a fieldTypeId = 12 for text box instead of 1 for string. This will only affect integrations that are parsing out fieldTypeId as part of the integration.
|Support for Chromium-based Edge Browser||Effective January 15, PPM Pro will add the latest version of Microsoft Edge (Chromium-based) to the list of supported browsers, coinciding with the GA release of Microsoft Edge. The latest versions of Chrome and Firefox, as well as Internet Explorer 11, will continue to be supported as well. Chromium-based Edge offers several speed and security advantages over Internet Explorer 11 and while we have no firm timetable for end-of-life for IE11, we hope that Chromium-based Edge offers customers a supported path to move to a modern browser. Note that this applies to Chromium-based Edge released on or after January 15 only. Edge Classic will not be formally supported, though it's thought to generally work with PPM Pro.
See https://blogs.windows.com/windowsexperience/2019/11/04/introducing-the-new-microsoft-edge-and-bing/#325DU81XPlvqJgCb.97 and https://techcommunity.microsoft.com/t5/windows-it-pro-blog/the-perils-of-using-internet-explorer-as-your-default-browser/ba-p/331732
|Ability to use beta (revamped) reports in production environments||Currently the new (revamped, beta) reports is turned on in sandboxes. Soon (target is February), they can be turned on by request in production environments. Once available, please enter a support case if you wish to enable in production.||Target - February 2020|
|Multiple assignees for project logs (issues/risks)||
Ability to assign multiple resources to project logs, granting owner permissions to assigned users (including Time users), as well as prepares for phase 2 integrations with LeanKit and Projectplace.
|Target - February 2020|
|Calculated Fields: Do the Right Thing!||
Currently, PPM Pro loosely enforces the data type setting used to configure a calculated field, resulting in inconsistent behavior between fields in the UI and fields in reports. Click here for more information.
In a future release, the application will strictly adhere to the data type setting on the calculated field. This stricter enforcement is part of a larger infrastructure effort, and as such the date is for this change has not yet been set. We will update the release notes when we have more information.
|Target - February 2020||Calculated Fields: Do the Right Thing!|
|Function Area||ID||Release Note Descriptions|
|Groups||942430797||Improved. In scenarios where a user inadvertently creates a nested filter-based group, error handling has been improved to ensure performance is not severely impacted. Previously this kind of mis-configuration resulted in extreme performance issues.|
|Internal Rates, Internationalization||947954430||Fixed. Editing a rate table while the user preferences are set to the German locale works as expected. Previously, an issue was causing the rate table entry to be set to inactive after making an edit while the user preferences were set to the German locale.|
|PPA||Fixed. PPA now includes project financial data as well as task-level expenses and role demand cost in its scenario optimizations. Previously PPA was looking only at role demand and task-level expenses, which has been recently deprecated.|
|Permissions||946719165||Fixed. Stakeholder users with the appropriate permissions can drill down from reports to view the Project Logs sections of projects.|
|Portfolios, Projects||938184418||Fixed. Associating a project with a portfolio works as expected. Previously, an issue prevented the list of projects to display.|
|Project, Tasks||943129919||Fixed. Copying a task into a project works as expected - you can select the target project Title from a list, and the Title is formatted correctly. Previously, an issue was causing the project Description text to appear in the project Title and resulted in garbled text.|
|Projects, UI||943142668||Fixed. Columns that are configured as locked remain locked after refreshing the projects List grid.|
|Reports||927412161||Fixed. When using the special character '&' in Description field text of a report, the character renders correctly on the Reports list. Previously, an issue was causing the character to render as '&'.|
|Reports, Projects||943842163||Fixed. Using the report source All Baseline Details on a Project with the option to 'Include current Values' includes the current values. Previously, an issue caused the current values to be blank, even if the 'Include current Values' option was selected.|
|Requests||922777083||Fixed. Low-level error message no longer appears in the hover tool tip for request fields that are not editable.|
|Requests||786485919||Fixed. The correct count value (number in parenthesis that indicates the number of items in a section) now displays. Previously, an issue intermittently caused the count to be (0) when in fact there was at least one item. The count updated after entering the section.|
|Requests||940302086||Fixed. When copying a request that has one or more associated items, such as notes, attachments, or associations, the count for the relevant items is correct on the copied request. For example, if you copy a request that has 3 notes, the new request will show (3) in the Notes tab.|
|Requests||937510912||Fixed. For gated requests, if you clear a field that was required for submission/moving to the next gate, you can still place the request On Hold or Reject it. Previously, if a field required for submission/moving to the next gate was cleared, no actions were available.|
|Requests||942310330||Fixed. Searching for a project's 'Associated Request ids' is 'All' works as expected - returns a list of titles of associated requests. Previously an issue caused a list of associated project titles to display, instead of request titles.|
|Fixed. Request fields that are used in approval criteria cannot be deleted. A new 'Gate' section now appears in the View References dialog and records any fields (including calculated fields) used in gate criteria. Previously if a field was not used on a request form, but was used in approval criteria, the field could be deleted, resulting in an error.|
|Requests||942342843||Improved. The request Description field can contain up to 4000 characters.|
|Requests - Legacy||950042831||Fixed. After creating an item from a request, the name of the new item appears in the Item column in the Request list as expected. Previously an issue was causing the ID of the item to display, rather than the Title.|
|Requests, Filters||942536233||Fixed. The Request ID is now available as a filter field.|
|Requests, List||939631381||Fixed. Request list fields based on PickList: Resource / Active User work as expected. Previously, an issue was causing an 'invalid value' warning to appear when selecting a value from the list.|
|Reports||927424810||Fixed. Searching on reports that include an '&' in the search string will return results as expected.|
|Status Comments||931952487||Fixed. Cutting and pasting text from one status comment into another works as expected. Previously an issue was causing the background color to be set to white after pasting in the text.|
|Tasks||934805274||Improved. Bulk scheduling resources to a large number of tasks performs faster.|
|Tasks||792156766||Fixed. Task estimated/scheduled hours are calculated correctly when a zero day duration task spans multiple days - one of which is a non-working day. Previously, an issue caused this scenario to double the task estimated and scheduled hours.|
|Tasks||907300793||Fixed. When using the Manual Percent Complete method with manual tasks, when a task has a complete date, the value of the % Complete field is 100%. If the Complete Date is removed, then the % Complete field returns to whatever value it was set to before the Complete Date was added (so either a previous value or a value of 0 if no previous value existed). Previously, when the Complete Date was removed, the % Complete value remained at 100%.|
|Tasks||New. In the project Tasks section, the Actions menu now has a "Spreadsheet Edit" option for invoking the spreadsheet-style editor (in addition to the icon that toggles).|
|Tasks, Filters||927525248||Fixed. Task filter fields are behaving as expected. Previously the filter was being respected on the task grid, but not in the task Details panel.|
|Tasks, MSP Import||907914300||Fixed. When importing tasks into PPM Pro, the hours per day value is respected whether set in MSP or in the PPM Pro project. Previously, an issue resulted in hours per day = 8, regardless of the settings in MSP or PPM Pro.|
|Timesheets||932784889||Fixed. Deactivating an administrative time type after it was used in a timesheet entry will result in a meaningful error message when updating the timesheet. Previously 'Unknown error' was shown.|
|Timesheets||938939862||Fixed. Users can log time up to 4 timesheet periods in advance. Previously an issue was limiting timesheet entry to only 2 timesheet periods in advance.|
|Timesheets||940789775||Fixed. After sorting the Home/Timesheet Approvals grid and then approving a timesheet, the sort order is retained. Previously, an issue cause the sort order to revert after the page was refreshed after approval.|
|Timesheets||946945876||Fixed. The Total Hours field displays the correct value after a user updates contoured timesheet entry values. Previously, an issue required a browser refresh to display the correct value.|
|Timesheets, staffing||928986356||Improved. If a timesheet entry has been created for an allocation (regardless of hours entered - can be 0, pinned), the role for that allocation cannot be changed on the project Staffing screen. The informational message that explains this scenario has been clarified. New message is: 'The role cannot be changed because one or more timesheet entries exist for this allocation.'|
|UI, Requests, Portfolios||937939698||Fixed. Entity lists that have multiple viewing styles, such as Portfolios (chart view) and Requests (card view), retain the selected view, even after multiple refreshes. Previously, the views sometimes changed after refreshing.|