Enterprise One Version 17 Update 13 Patch 4

Resolved Issues for Portfolio Resource Management 17 Update 13 Patch 4:

Released:  10/14/2021

• This patch addresses a compatibility issue with May 2021 PowerBI Report Server. When uploading OData Sourced PBIX files to Reporting Content Management. for more information please visit https://success.planview.com/Planview_Enterprise_One/Portfolio_and_Resource_Management/Analytics_and_Reporting/Power_BI/Power_BI_Report_Server_Update_Notification 

Resolved Issues for Portfolio Resource Management 17 Update 13 Patch 3:

Released:  10/05/2020

• 00301832 - On September 21st, Planview identified a report subscription error that affects the standard subscriptions functionality of Enterprise One. If certain rare configurations and sequence of events occur, this error allows a given report to be distributed containing the wrong portfolio data within a company's internal environment to recipients of a given subscription definition. 
  Details: It was possible when clicking the Update button within an existing subscription (subscription B) that the portfolio context would be improperly set based on the value from the previously edited subscription (subscription A) which would result in subscription B running and sending the wrong data to recipients defined on subscription B. This would only be possible if a given report had multiple subscriptions defined across multiple portfolios.
  Planview has since resolved this issue with a security patch and made publicly available to our customer base.
  Planview recommends applying E1 17.3.3 release to your environment in-order-to prevent the possibility of encountering this scenario. 

Resolved Issues for Portfolio Resource Management 17 Update 13 Patch 2:

Released:  09/10/2020

• SQL Server Only.  This patch addresses an issue with the release of 17.13.1 that caused a failure on the spread down of a Work Portfolio View on a SQL Server database.
  Navigate to Work > Work Portfolios > Portfolio View
  Action Menu >Financial Planning > Spread-down Financial Plans

Resolved Issues for Portfolio Resource Management 17 Update 13 Patch 1:

Released:  08/28/2020

00216361, 00254039 - Modified the processing of the daily tables to improve error handling and resolve concurrency issues:

• This version resolves an issue where creating a primary key violation in a temporary table caused the procedure it to fail
• Now the procedure will not delete valid daily records without reinserting them even in case of a failure
• If the PSP_DAILY_SCH is called for a specific portfolio it will refresh only those daily records that corresponds to the relevant assignments updated after these daily records were created. This change improves performance and concurrency for customers that run PSP_DAILY_SCH for several large overlapping portfolios within a short period of time.
• The latest version will not start if the PSP_DAILY_SCH procedure if it is already running in the refresh mode for all projects in another session. The previous version would prevent the procedure running concurrently only with the full rebuild.
• The error handling logic has been split into steps and the step number will be shown in the PV_ERRORS table in case of an error
• The latest version will contain records for every call to the PSP_DAILY_SCH procedure with its parameter values in the new DAILY_SCH_LOG table.
• Now the procedure will consistently include the last day of the time range to the DAILY_SCH calculations.

00296064 - We improved performance of Financial Management Rollup by optimizing the stored procedures.

00266287 - Financial Planning Excel Import: Line notes will only be updated by import when the Line Note value is not empty.

00266098 - Timesheets:  Oracle Only:  Users no longer encounter a server error when clicking on Overdue Timesheet email link.

00286855, 00290873, and 00292756 - Lifecycle workflows are designed to help automate, so when they decided to not activate that first step of a new incremental model (when set to start silently), we stepped in to stop this less than desirable behavior. They are now behaving!

00237301 - After an investment status is refused then published, the primary lifecycle segment will now suspend all incomplete steps and the secondary lifecycle segment will become active.

00263985, 00264206, and 00265167 - Column Sets:  Some users started experiencing an issue when they would open the "Detail Column Set" screen for an existing column set and moving attributes up/down in the list.  The attribute display name would disappear and reappear when you selected a different attribute.  We can thank our friends that create the Chorme browser for this!  This was a bug introduced by Chrome version 81.0.4044.129 and is fixed by upgrading to version 81.0.4044.138.

00255563 - Work View:  A minor change was made to the Reserve and Allocation Profile pages in that they will no longer display profile segments with zero effort.  These pages can be accessed from the Assignments Graph by clicking either Reserve Profile or Allocation Profile.

00230952 - Corrected Runtime Error encountered when editing project status on Portfolio view.

Backup Procedure:

Database: Back up the Planview Database and the \midtier\admin directory.

Web Server:  Backup the entire Planview\MidTier\WebServer directory.  

Note: The Web Server installer will merge any new web.config and Planview.Scheduler.exe.config settings with the custom settings entered by customers. The installer will save a copy of the existing web.config file as Web.config<date> in order to refer to the custom settings before the last update.

Planview Database Installation and Upgrade Instructions

1. Run PRM17.13.4AdminToolsSetup.exe on an Administrator’s client workstation or any server that has the Admin Tools installed. Set the destination directory to one level above the DBA folder (usually c:\planview\admin).
2. From the /admin/dba directory, edit the RunUPDATE_PRM17_to_PRM17_13_4.bat file and populate with the appropriate Planview database values.
3. Execute the RunUPDATE_PRM17_to_PRM17_13_4.bat file to update the Planview database.

Note: Oracle customers will encounter an "INSERTXMLAFTER": invalid identifier errors during the database upgrade process. This is an Oracle identified bug that has been addressed in an Oracle patch. This error will only affect Ideation Management customers. If you are not an Ideation Management customer, then this error can be ignored. If you do use Ideation Management, then the database server will need to upgrade to 11.1.0.7 or higher.

This completes the Planview database portion of this installation.

Planview Web Server Platform Installation Instructions:

Run PRM17.13.4WebServerPlatformSetup.exe on the Web Server. The target path is set automatically based on registry settings entered during the initial Planview Enterprise One – Portfolio and Resource Management release 17 installation.

This completes the web server portion of this installation.

Recovery Procedure:

Web Server:  

a.    Stop all Planview Services.

b.    Stop the World Wide Web Publishing Service.

c.    From the \webserver\AdminTools directory, Edit the UnregisterAssemblies.bat by replacing %1, throughout the file, with the Planview directory path (i.e., C:\Planview\Midtier\Webserver).

d.    Run the UnregisterAssemblies.bat.

e.    Replace the backup of the entire \webserver directory.

f.     From the \webserver\AdminTools directory, edit the RegisterAssemblies.bat by replacing %1, throughout the file, with the Planview directory path (i.e., C:\Planview\Midtier\Webserver).

g.    Run the RegisterAssemblies.bat.

h.    Restart all Planview Services and the World Wide Web Publishing Service.

i.      At this point, the restore of the Web Server is complete.

 Changes to Environment:

For the components listed in the Backing Up Planview Enterprise Components section of this document, changes are logged in the following files. Note: The paths to the files are based on a default installation. If you change the location of Planview Enterprise components during an install, the paths noted in this section will not be applicable.

Database: Review the 17.13.4000Administration Tools.log one level above the DBA directory.

Web Server:  Review the 17.013.4000WebServerPlatform.log one level above the Webserver directory.

If you have any questions or require further assistance, please call Planview Customer Care at (512) 346-8460.