Click here for an overview of the PPM Pro release process.
The table below lists this month's product release dates.
|Release Notes published
|System released to sandbox environments
|May 10, 10 PM - 1 AM PT
|System released to production environments
May 17, 10 PM - 1 AM PT
Releases are deployed during the standard maintenance windows, which are Fridays, 10 PM PT - 1 AM PT.
- 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 May 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 June 7, pending QA approval.
Note About Multi-Select Lists: Several issues were addressed relating to multi-select lists. In the May release, in order to better support request mapping and improve the SSA architecture, an internal change was made in how user-defined multi-select list fields are stored. Previously, multi-select lists were stored as comma-separated strings with their display values ("Red, Blue, Green"). With this change, internal IDs are stored instead. This has many architectural advantages (request mapping among them) and was long-overdue. The expectation was that this would be an internal change but unfortunately a few end-user visible behavior changes resulted. We have analyzed the reports of these issues (included in the table below) and added support to automated and manual testing to reduce regression risk in the future. We apologize for any inconvenience this might have caused.
|Release Note Description
The WSAPI call getEntitiesByFilter now returns the display text for multi-select list fields rather than IDs.
Multi-select fields contain the display text rather than the ID value when exporting to Excel.
|Multi-select fields where the display text was changed while the list was in use can now be edited (editing will coerce the field to the updated values). Previously an error message would display in certain scenarios.
|Multi-select lists values where the list entries are purely numeric (e.g. "1234") now display correctly in reports. Previously, "Value not Found" would be displayed in some cases.
|Filter results as expected when using a multi-select field with conditions IS NOT, CONTAINS or IS.
|Multi-Select fields display string field values in History.
|Calculated fields based on number fields return Null if the field is blank. Previously the field displayed 0 if the value was Null.
Release planned for Friday May 24, pending QA approval.
|Release Note Description
|Fixed. Owner and Requester fields, as well as calculated fields based on those fields, now render correctly. Previously field metadata was shown instead of the field value.
|Misc entities (non-SSA)
|Fixed. Intermittent error ("Required entityID is missing") when accessing non-SSA entities, such as Resource, Divisions, and legacy requests, no longer thrown
|Fixed. Reports using list fields based on Current Portfolio now render Portfolio Name as expected, instead of Portfolio Class: Portfolio Name.
New Feature Matrix
For more information…
While the multi-currency feature has entered GA status and is available to anyone who wants it, it is an optional feature that will not automatically be enabled in production environments (similar to Managed Staffing and some of our billing support).
If you wish to enable multi-currency in your production environment, please enter a support case.
Note: All customers have an Organization currency. In the past, this currency was the only currency. Now that PPM Pro supports multiple currencies, we needed to make an underlying infrastructure change to incorporate the Organization currency into projects so that reporting on financial fields would work regardless of whether one or more currencies are in use.
Although you will see this field only if you have requested to enable multi-currency, if you have project alerts enabled you might see a one-time notification when this Currency field is initialized with the Organization currency (regardless of whether or not you have enabled Multi-Currency). The property has no impact on your projects if you are not using the multi-currency feature.
GA target - May
New Requests! (aka Requests revamp)
This feature will be rolled out over the course of several releases ("rolling beta").
We will update this list every month to indicate when/what additional features will be included.
Legacy requests will continue to be supported for the foreseeable future. You can use legacy requests and new requests side-by-side while you set up the new requests to your liking. Since the new model is different from the legacy in several key ways, we are not planning an automated migration at this time.
Current functionality (rolling beta)
User Experience Inner Circle: New Requests - Note that this was recorded earlier this year, and target dates have shifted
|Enable Cross Site Scripting Protection
System-wide XSS protection on non-rich text fields such as Title or any non-HTML UDF string fields is now enabled in all environments. The Strict XSS Protection setting in Admin/Organization/Info will still control rich text fields.
NEW: To minimize disruption to existing integrations, we have enabled an option that controls whether WSAPI responses for text box fields, such as Descriptions, will be returned in modified text format (similar to how these fields behave today) or in HTML. If you wish to have WSAPI responses for text box return HTML, please contact customer care.
GA target - May
|PPM Pro - LeanKit Integration Phase 1
Allows you to connect projects from PPM Pro to cards on a LeanKit board.
Interested customers who are already using LeanKit can submit a Support Case with Customer Care or contact PPM Pro Product Management.
|Limited Beta - May target
|Q2 Roadmap Presentation
|October 2019 - deprecate task level expenses
Project-level financials was made generally available (GA) for all customers in October 2018. We will begin to enforce the transition away from task-level expenses on the year anniversary.
Phase 1 - October 2019: The ability to create new task level expense estimates will be disabled (New button removed). This will prevent the creation of new expense estimates.
Phase 2: The task level expense facility will remain visible but view only. This will allow you to run reports on historical data. We will leave this enabled until we are sure that there is no longer any need for this data.
As always, if you are already not using this feature and would like it removed so it doesn't confuse anyone, please enter a Customer Care Case and ask to disable the New button or the entire feature for your organization.
|Transitioning to Project-Level Expenses
|Release Note Descriptions
|Fixed. When working with the Accounts page, you can navigate to any project listed in the Programs section by clicking its link. Previously, an issued caused the project link to be unresponsive.
|Fixed. You can change the value of the Primary Administrator on Admin/Organization/Info. Previously the system threw an error when this field was edited.
|Fixed. Users can edit the default time zone on Admin/Organization/Info as expected. Previously the system threw an error when this field was edited.
|Fixed. The PatternMatch function for calculated fields is treated as a Boolean field. Previously, an issue was causing the function to be treated as a string type which was causing compatibility issues in calculated fields.
|Fixed. You can successfully build a calculated field that subtracts a user-defined integer field from a Date field. Previously, you could subtract an actual integer from a Date field, but if you subtracted an integer field, an error was thrown.
|Fixed. The Rerun menu option is available to all users with appropriate permissions on the dashboard. Previously, the dashboard was not acknowledging permissions granted in a profile with a Team rule.
|Fixed. When importing entities, the entity titles in the mapping file match the names of the entities in the system. Previously, an issue caused the names to be different and thus the correct entities could not be imported.
|Fixed. Applying filters with multiple criteria (such as multiple units) and the ANY operator on the Organization/Manage Time & Expense/Manage Resource Time page works as expected, including out of the box filters such as +My Direct Reports.
|Fixed. If an organization has only one active project category, that category will appear on the projects list. Previously, an issue was preventing the Category field from displaying on the projects grid if there was only one project category.
|Fixed. The standard Budget can be added to the project grid and reordered/removed as expected. Previously, and issue was causing these fields to fail to appear on the grid after moving them to the Selected Fields pane in the Configure Columns dialog and saving.
|Fixed. Invoking the Permissions Explorer on a Project entity (View people with permissions on this entity) shows the correct resources as having permissions. Previously, an issue was causing resources without the appropriate permissions to be displayed.
|Improved. KPI reports return data as expected for all types of fields excluding Create Date and calculated date fields. Particularly, text box fields are displayed properly, and both Lookup list and Status list display properly (with no blanks). There is still an outstanding issue about user-defined date fields that will be addressed in a future release.
|Reports, Financial Entries
|Improved. When reporting on financial entries, if the report definition includes actuals only (and not the parent forecasts), then the actuals will be sorted according to the instructions in the report definition. Previously, even if the forecasts were not included in the report definition, the actuals were first sorted by their parent forecasts, which was confusing.
|Reports, Timesheet Filters
|Fixed. When creating a filter for a Timesheet or Timesheet Entry report, you can now select an Integration Time user. Previously, Integration Time users were not selectable in these filters.
|Fixed. When creating request fields in SSA, the Display Option field works as expected (persists selected value). Previously, an issue caused the Display Option field to display no value when configured to any field type (Integer, Money, Percent, and so on).
|Fixed. Copying data from a request to a project no longer throws an error.
|Fixed. Skill categories can be created/edited as expected. Previously, an issue was preventing the selection of a skill range, which is a required element of a skill category. As a result, skill categories could not be edited or created.
|Fixed. In Task-level (bottom-up) resource planning mode, the task Owner droplist is now populated with All Resources (same as in project-level mode).
|Fixed. Modifications made to task budget fields, such as Budget Cost, are being reflected correctly - specifically with the correct date - in the History dialog. Previously, an issue was causing new modifications to appear as earlier edits in the History dialog.
|Fixed.Timesheet Managers are now able to view and edit pinned timesheet entries, including when the entry has zero hours logged to it. Previously, the Timesheet Manager was unable to create an entry if the entry is pinned and no time had been logged against the pinned entry.
|Fixed. When entering time, the interaction with the user interface is accurate - values that are entered are rendered correctly, and HTC and Total Hours update as necessary. Previously, intermittently, the UI occasionally blinked, and deleted values sometimes reappeared on the grid resulting in a mismatch between the value in Total Hours and the cell values.
Fixed. When creating Timesheet Guidelines, whitespace will be preserved in HTML formatted text entered in the rich text editor. Unfortunately, if you have existing guidelines that are improperly formatted, you'll have to delete the text, save the guidelines, then re-open the Timesheet Guidelines and re-enter and save the text. Now the text should be correctly formatted.
|Fixed. Grid columns are customizable by category. For example, the projects List page can display different columns/column order for Category A and for Category B. Previously, an issue was preventing different layouts by category.
|Fixed. Project Start and End dates are displayed on the top panel after a scenario is Saved. Previously, an issue was preventing these dates from rendering.
|Fixed. SelectEntity calls to portfolios that include Portfolio Class Title (methodId 114145) will return results. Previously an error was returned when this field was requested.