What's New - June 2020
Click here for an overview of the PPM Pro release process.
The table below lists this month's product release dates.
|Release Notes published||June 5|
|System released to sandbox environments||June 12|
|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 June 17th release webinar. Also, remember you can sign up for any/all upcoming customer webinars here.
- 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.
|Function Area||Leankit Card||Release Note Description||Planned Release Date - Pending QA Approval|
|Requests||122806363||Fixed. When a request is approved at a gate and the approver checks the "Notify Requester" notification, an email is sent to the requester. If the requester is not a user, the email will still be sent but will not include a link to the request, because resources (non-users) cannot log into PPM Pro. Previously, an issue was prevented the email from being sent if the requester was a resource (not a user).||June 26|
|Resource Workbench, TImesheets||1131518173||Fixed. In the Resource Workbench, after selecting a resource and choosing Actions > View Timesheets, the selected resource's timesheets are displayed. Previously, an issue caused the timesheets of the current user to be displayed.||July 3|
|WS API||1133139603||Fixed. The WSDL used for WSAPI now includes the operation elements for SOAP 1.2 bindings for the API method createOrReplaceCalendarEvent, which was added in the June release.||July 3|
New Feature Matrix
For more information…
Enter a support case if you wish to enable in your production environment
Current functionality (Rolling beta)
Demo: Intro to Reporting Beta
New: Building Gantt Chart Reports
New: Grouping and Sorting for List Reports
Deprecating legacy requests
Legacy requests will be deprecated with the June release. This includes:
|June 2020 release||
Transitioning from Legacy to New Requests
End-to-end demo of new requests
If you have any questions regarding the transition, please open a Customer Care case.
The Financial Summary feature is intended to be a highly configurable rollup of all project financials data, including expenses and revenue, with a time series comparison of budget vs. forecast vs. actuals.
Permitted users can configure the available summary fields including what data feeds those fields (manually entered data, financial entries, timesheet actuals, staffing role/resource allocations, and others).
|Beta target - July 2020 release|
Exciting news for customers with multiple Planview products! Planview ID will be launching soon and will provide a centralized user management experience for an organization's administrators to view and manage users' access across Planview products. With Planview ID, users will be able to login to multiple Planview products with a single username and password.
|Function Area||Leankit ID||Release Note Description|
Fixed. Using the ParseInteger or ParseFloat functions in a calculated field with leading zeroes before an 8 or 9 works as expected - will return a number beginning with 8 or 9. Previously, using the ParseInteger or ParseFloat function in a calculated field with leading zeroes before an 8 or 9 returned Null.
|Calendar, WS API||1097325972||
New. You can now programmatically create non-working, whole day calendar events for Base and Resource calendars. The new method is called createOrReplaceCalendarEvent. Ancillary calls include removeCalendarEvents and getCalendarEvents. Note that if an event already exists on the same date as the new event, the new event will overwrite the existing event. See the javadoc for this call by navigating to Admin/Web Services, clicking the View API Documentation button, and searching for the call in the TTBusObjService class.
Improved. When using the Data Import facility to import resources, the resource's Unit is a required field and is now labeled as such with an asterisk in the generated Excel spreadsheet. Previously there was no asterisk denoting that resource's Unit is a required field.
Fixed. The "Base Calendar" field has been removed from the generated Excel template for updating projects (is still available for creating projects). Base Calendar has never been updateable via data import - the Excel template was incorrect.
Fixed. UDFs of Display type Money or Integer display correct values on Forecast entries in all locales. Previously, an issue was causing the "." character to be considered an invalid character, and as a result locales whose currency use a decimal for the thousands separator were not getting expected results.
Fixed. Characters with diacritics (Umlaut, Acute, Grave, Cedilla, Circumflex, Breve, Hacek,Tilde) can be included in the Odata data feed. Note that if you have an existing published dashboard that is not on a schedule, you'll need to republish it - either manually or via a schedule - to apply the fix for this issue.
Fixed. The Last Modified Date for user password reflects the correct date, as expected, for all Time Zones. Previously, for Time Zones other than Pacific, the date displayed was one day early.
Improved. The Send Email button on the project Team section is inactive until at least one resource is selected. If no resources are selected, the button will be grayed out. After selecting resources (click or shift/ctrl-click to select multiple), clicking the Send Email button brings up the email client populated with the email addresses for the selected resources who have email addresses configured on their resource record in PPM Pro. If some or all selected resources have no email addresses configured in PPM Pro, the email client will still open and you can enter the email addresses manually.
Fixed. When configuring a project alert, if you change the Send To value, the Alert Type list refreshes. Previously, an issue prevented the list from refreshing.
|Projects||1099407557||Fixed. When creating a project from a template, the Templates droplist is organized by category. Previously, an issue prevented the category headings from appearing, making it harder for users to find a specific template.|
Fixed. The Field Descriptions report renders the text in the Description field of calculated fields as expected. Previously, an issue caused HTML markup to appear in the Description field for calculated fields.
Fixed. Reports based on the Project Scores By Category report source work as expected. Previously, an issue caused the system to throw an error after clicking Run.
|Reports (Legacy)||1073028235||Fixed. In Legacy reports, the Gate Journey, Gate Wait, and Gate Wait Actions folders and all their included fields have been removed. The fields in the folders were not producing expected results and were causing performance issues, so they have been removed for now.|
|Request, Data Import||1103271304||
Fixed. Requests with titles up to 80 characters long can be imported (provided other requirements for importing are met). Previously, the import was unsuccessful if the request Title had more than 72 characters, instead of 80.
Fixed. Fields that are included in gate logic criteria are marked as "referenced" by the system, and as a result cannot be deleted until they are removed from the criteria. Previously, fields used in gate logic criteria were not marked as "Referenced" and could be deleted, usually resulting in broken gate logic.
Fixed. The editor works as expected when the Base Calendar field is included on the grid. Previously, an issue caused the system to throw an error when the task was edited while the field was on the grid - had to remove it in order to continue.
Fixed. Restricting fields derived from sub-portfolios works as expected - you can show fields on the grid for certain groups, and not for others.
|Timesheets||1103256400||Fixed. Members of the Time Manager group only can edit a resource's timesheet. An issue allowed the Immediate Supervisor of a resource who was also configured as the timesheet approver for that resource to edit the resource's timesheet.|
|Timesheets||1109281890||Fixed. When submitting timesheets that include multiple projects and project managers, the timesheet approval alert for PM approvals is sent to all appropriate project managers/owners. Previously an issue resulted in the alert being sent to the first project manager on the submitted timesheet only.|
|UI, Text Box Fields||1095602111||
Improved. Improved performance when loading entity sections such as Details and Additional Details that have a large number of user-defined text boxes.
|WS API||1084573628||Fixed. The Portfolio Project entity (116) has been added to the list of supported entities on Admin/Web Services.|