CA PPM 15.1 Change Impact and Upgrade

HID_release_info_change_impact_op
ccppmop151
HID_release_info_change_impact_op
Plan the 
CA PPM
upgrade and determine the upgrade options that fit your business needs. As the administrator and implementer, use this information to plan your training and rollout efforts. Complete information for the current release and summary information for previous releases is provided here. The complete 
Change Impact and Upgrade 
content
 
for a specific 14.x release is available by selecting a release in the Versions drop-down on this page. Content before 14.x is available on the Documentation page of CA Support Online.
This article covers the following topics:
  • The system preparation before upgrading
  • An overview of the upgrade process
  • The post-upgrade tasks
  • Features and enhancements for the current and previous releases and the upgrade actions that they require
To prepare for an upgrade to Release 15.1, review the supported upgrade paths, features, enhancements, and required upgrade actions. If you are upgrading from an earlier release, review the information for the updates in Releases 14.4, 14.3, 14.2, 14.1, and the 13.x releases.
2
Supported Upgrade Paths for Release 15.1
If you have any of the following releases installed on the base level with no patches, you can directly upgrade to 
CA PPM
 Release 15.1:
  • CA PPM
     Release 13.3
  • CA PPM
     Release 14.1
  • CA PPM
     Release 14.2
  • CA PPM
     Release 14.3
  • CA PPM
     Release 14.4
Follow the upgrade patch levels and exceptions in the following table only if you have installed any patches on the base versions:
Supported Patch Levels for Upgrade
Upgrade Patch Level Exceptions
Download and Install the Patch
Patch level 13.3.0.14 installed on the base version 13.3.0
None
Patch level 14.2.0.11 installed on the base version 14.2.0
None
See the
CA PPM
14.2 and Jaspersoft Patches
page in the 14.2 documentation.
Patch level 14.3.0.7 installed on the base version 14.3.0
None
See the
CA PPM
14.3 and Jaspersoft Patches
page in the 14.3 documentation.
Patch level 14.4.0.2 installed on the base version 14.4.0
None
See the
CA PPM
14.4 and Jaspersoft Patches
page in the 14.4 documentation.
For example, you have 
CA PPM
 13.2 or an earlier release. Upgrade to one of the listed releases before you upgrade to 
CA PPM
 Release 15.1.
If you are on a 
CA PPM
 patch level that is not included in the preceding list, take care when attempting an upgrade to Release 15.1. Issues can result if you try to upgrade to Release 15.1 from a patch level that is not supported. For best results, wait for a supported upgrade path to a later release or patch. To find out more, contact CA Support or your CA Services representative. Also, visit the cappm Community to collaborate with your community members.
The Release 15.1 installer can upgrade your data set from various older releases. The installer detects how many incremental upgrade steps are required to upgrade to Release 15.1.
If you are running a version earlier than Release 12.1.1, consider upgrading to 12.1.1, 12.1.2, or 12.1.3 before you upgrade to Release 13.3 (as a prerequisite to upgrading to 15.1). Although the interim upgrade is not required, it simplifies the troubleshooting and restart process if an upgrade step fails.
Add-in Compatibilities for CA PPM 15.1
Review this important information about upgrading installed add-ins, accelerators, and connectors for Release 15.1.
  • If you are upgrading from Releases 13.x or 14.x to Release 15.1, the following add-ins are upgraded automatically:
    • PMO Accelerator
    • Accelerator for the PMBOK
    • CA Agile Planning
  • If you are upgrading from any version before Version 13.0 to Release 15.1, upgrade all installed add-ins.
  • Starting with Version 13.3, a new installation process is required for add-ins, accelerators, and connectors. For more information, see 
    Installing and Upgrading
    .
The add-ins, accelerators, and connector releases that are included in the following table are compatible with Release 15.1 for a new installation of Release 15.1, an upgrade from 12.x to 15.1, and an upgrade from 13.x and 14.x to Release 15.1:
Add-in, Accelerator, or Connector
Release
End of Life Date
PMO Accelerator
15.1.0
Application Portfolio Management (APM) Add-in
15.1.0
Agile Add-in
14.4.0
Earned Value Manager
2.0.3
Accelerator for PRINCE2
2.0.2
Accelerator for the PMBOK
2.0.5
Accelerator for New Product Development
2.0.4
Connector for Microsoft SharePoint 2013
3.0.0
CA Agile Planning
14.1.0
CA PPM SaaS Integration Adaptor
14.1.0
Business Relationship Manager (BRM) Accelerator
3.0.2
June 30, 2016
CA PPM
Catalyst Connector
2.5.0
June 30, 2016
CA Unicenter Asset Portfolio Management (APM) Connector
2.0.2
June 30, 2016
Connector for CA Unicenter Service Desk and CA Software Change Manager
2.0.1
June 30, 2016
PPM Essentials Accelerator
2.0.2
June 30, 2016
Service Connect
2.0.0
June 30, 2016
End of Life for Some Add-Ins and Connectors
CA Technologies is continually working to improve our software and services to best meet the needs of our customers. To focus our development efforts and to help our customer base achieve their strategic business initiatives, we are investing our resources in new technology and software, and have dropped support for these add-ins and connectors:
  • Business Relationship Manager (BRM) Accelerator
  • CA PPM Catalyst Connector
  • CA Unicenter Asset Portfolio Management (APM) Connector
  • Connector for CA Unicenter Service Desk and CA Software Change Manager
  • PPM Essentials Accelerator
  • Service Connect
For complete details, download the End of Life Announcement PDF.
User Interface Changes for Release 15.1
Official Debut of the New User Experience for Project Management and Timesheets
This release marks the official debut of the New User Experience that includes dynamic new ways to manage projects, tasks, and timesheets. Project managers, resource managers, and team members recognize the following value:
  • The casual Project Manager sees simplified ways to manage projects, collaborate with their team, and report project status.
  • The Resource Manager sees simplified ways to review and approve timesheets.
  • Team Members see simplified ways to record their time.
Upgrade Action
: For all new customers, the 
New User Experience
 is already active and ready to use. For upgrading customers, the 
New User Experience
 is not active. Administrators can activate the 
New User Experience
 by completing the steps under 
Enable the New User Experience
 in Configure General System Settings. If http(s)://<server> is the URL for your existing 
CA PPM
 environment, the URL for the 
New User Experience
 is http(s)://<server>:/pm.
For upgrading customers, activating this feature also resets all fields in the Default Time Entry Options to the stock default values. If you currently have any of these fields configured differently than the stock values, revisit this configuration page after activating timesheets for the 
New User Experience
.
Administrators can configure Single Sign-On (SSO) for the 
New User Experience
 by configuring the SSO server.To learn more, see 
Configure Single Sign-On (SSO) for the New User Experience
 in CSA: Security, Passwords, LDAP, SSL, SSO, XSS, and FIPS.
To manage projects in the 
New User Experience
, verify that the PMO Accelerator add-in is installed on your
CA PPM
instance. Users with the Project – Navigate access right get an error message if the PMO Accelerator is not installed. See Install the PMO Accelerator Add-In and PMO Sample Data.
For users accessing only the new Timesheets (with only the
Timesheet – Navigate
access right), the PMO Accelerator is not required.
Make sure that you provide the appropriate users with the following new access rights as required:
  • C
    lassic PPM - Navigate
    . The access right allows users to navigate back to Classic 
    CA PPM
     from the 
    New User Experience
     using the icon_classic_ppm.png  
    Classic PPM
    main menu item.
  • Project - Task Management (Instance)
    . The access right allows team members to create, edit, delete, and add assignments to tasks. The right is automatically granted if you add the team member to a project in the 
    New User Experience
    .
Resource Management Changes for Release 15.1
Resource Management Portlet Enhancements
The Resource Manager and Investment Manager filter fields are now browse lookup fields. In previous releases, these text fields were more difficult to use as filters. The following portlets reflect these changes:
  • Top Down Planning by Investment
  • Allocations - Weekly Detail
  • Allocations - Allocation Discrepancy
  • Unfilled Requirements
  • Booking Status
Upgrade Action
: None. After an upgrade, users automatically experience these fields as browse lookups. Any pre-upgrade configuration of field types in the portlet filter section is ignored and these fields appear as browse lookups after upgrade.
In this release, users can filter on Booking Manager in the following Resource Planning portlets:
  • Booking Status
  • Unfilled Allocations
  • Allocations - Weekly Detail
  • Allocations - Allocation Discrepancy
  • Top Down Planning by Investment
In previous releases, this field was not available. Users can also add the Booking Manager field in their own custom power filters. Studio developers can find the new Booking Manager filter field in the Team Allocation and Actuals vs Allocation Discrepancy data providers.
The following Resource Planning portlets already included the Booking Manager browse lookup field in filter and list views:
  • Workloads - Resource Workloads
  • Capacity - Role Capacity Histogram
  • Capacity - Role Capacity
In these portlets, Booking Manager is now available in power filters. Developers can find the Booking Manager filter field in the Resources with Aggregation and Roles with Resource Aggregation data providers.
Upgrade Action
: None.
Portfolio Management Changes for Release 15.1
The Portfolio Management updates for Release 15.1 include the following items:
  • On the portfolio targets page, users can now select all the roles under Portfolio Role Totals (Hours/FTE). Users can also perform the applicable actions such as remove, populate capacity, and so on.
  • The number of roles that you can add on the portfolio targets page has increased from 25 to 75.
  • After adding roles on the portfolio target, you can configure the Waterlines view to see all available roles. The portfolio constraint gauges at the bottom of the Waterlines view are now vertically stacked for better user experience.
Advanced Reporting Changes for Release 15.1
The Advanced Reporting updates for Release 15.1 include the following items:
  • Jaspersoft 6.2.1 is certified and supported. 
    CA PPM
     releases 14.3, 14.4, and 15.1 all support this single Jaspersoft version. Follow the instructions in 
    Install and Configure Advanced Reporting with Jaspersoft
     to help ensure a successful installation and configuration.
  • Jaspersoft 6.2.1 enables System Administrators (Superusers) and Organization Administrators (Tenant Administrators) to perform the import and export actions. However, the 
    CA PPM
     Advanced Reporting integration with Jaspersoft enables only the Jaspersoft Superuser to perform these actions. For more information, see 
    Upgrade Jaspersoft and Advanced Reporting Content
    .
  • You can no longer export report output to FTP.
  • Ability to Restrict Notifications to Trusted Email Domains
    . Administrators can specify trusted email domains (for example, ca.com) so that report emails and job status notifications do not go out to email addresses outside these domains. The user can still specify any email address for notification when scheduling a report. However, before sending the emails, the system filters out the email addresses that do not match the trusted domains. See 
    Install and Configure Advanced Reporting with Jaspersoft 
    for details.
  • Access Events are Enabled for a Maximum of Seven Days. 
    Advanced Reporting users can see the recently viewed items and the modified items from the following locations:
    • Recently Viewed Items
       section on the Advanced Reporting Home page
    • Modified by me
       section under Advanced Reporting Home, View, Search Results
    The items appear for up to seven days from the date you accessed or modified the reporting item. For example, you modify the Application Assessment Analysis report today, then the report appears under the Modified by me items for the next seven days starting today. On the eighth day, the report no longer appears under Recently Viewed Items.
    : For
    CA PPM
    releases 14.3 and 14.4, access events are enabled only if you are integrating with Jaspersoft version 6.2.1 or higher.
  • Page limits
    . When installing and configuring Advanced Reporting and when you have a Non-Scheduler instance in a clustered environment (Standalone node), the maximum number of pages, by default, that can appear on the user interface is limited to 500 pages. When the limit is exceeded, you receive an error. If you need more than 500 pages to appear, you can schedule a report. When you have a Scheduler node, the maximum page limit is 1000.
Integration Changes for Release 15.1
Integration with 
CA Agile Central
 (Formerly Rally)
CA PPM
 integrates with 
CA Agile Central
 agile development software. The integration works with 
CA Agile Central
 SaaS. The integration also supports WSAPI version 3.0.
As of August 2018, the integration of any release of CA PPM with any
on-premise
edition of CA Agile Central (formerly Rally) is no longer supported. CA PPM and CA Agile Central SaaS integrations are recommended.
To learn more, navigate to 
Integrate with 
CA Agile Central
 
in the Add-ins and Integrations section.
REST API Changes for Release 15.1
The
CA PPM
REST APIs can only be used by
CA PPM
engineering. At this time, the REST APIs are not supported for customer or partner use.
Our strategy is to focus on developing robust APIs as we design the
New User Experience
. The APIs may change as we make architectural improvements, add capabilities, and optimize performance. We will review our strategy every release and make the APIs publicly available as soon as possible.
Administration Changes for Release 15.1
Resource (User) Action Tracing
To troubleshoot potential issues, administrators can activate Action Tracing on a resource (user). When the user logs in to 
CA PPM
, the software generates a trace file. The trace file captures the actions that the resource performs in the application. The 
app-trace.xml
 file is available in the installation\logs directory. Historically, CA Support Engineers were required to derive this information from a custom log category on the security.logs page.
Trace flags determine the output of Action Tracing. For the feature to be useful, both of the following flags must be enabled:
  • traceEnabled="true"
  • traceJDBC="true"
Upgrade Action
: None. By default, these settings are set to 
true
 in the properties.xml file.
Export to Excel Time-Based Governor
A governor adds business logic to Excel exports that is designed to minimize inconvenience and wait time. One minute after you Export to Excel, the application estimates the completion time. If it exceeds the approved 10-minute default threshold, a message appears in the exported file to alert the user. The message indicates that the export has been stopped. The approved timeout threshold has been exceeded. The new Excel file displays the estimated time it would have taken to complete the operation. 
For example, a user forgets to apply a filter and attempts to export 60,000 rows. Only the first 25,000 rows can be exported. Due to subpages and display conditions, the export is estimated to run for 45 minutes. In previous releases, performance suffered as the user waited 45 minutes for the export to complete. In this release, after only one minute, the application cancels the export. To save time, the user filters the list down to 7,000 rows and exports to Excel again, this time without performance delays.
Upgrade Action
: No action is required. Adjust the timeout threshold only if required. Be aware of the performance impacts and load times of any adjustments you make to your configuration. As a best practice, remind users to filter their data to reduce the number of rows below 25,000. If additional rows are required, they can also create a report instead.
Governor Settings (Maximum Data Limits)
Governor settings optimize performance by enforcing maximum limits on specific data. For example, the maximum size allowed for an uploaded document is 20 megabytes and the maximum number of rows you can export to Excel is 25,000. These limits help prevent a minority of users from degrading the performance of all other users.
In previous releases, these settings were stored in the 
properties.xml
 file, the database, and other hardcoded areas. In this release, governor settings are now stored in a single 
governors.properties
 file located in 
<INSTALL_DIR>/config
As an example, you no longer need to specify a 
Maximum Rows for Export To Excel
 value. This field has been removed from the Administration, General Settings, System Options page.
The following table lists the recommended and enforced governor settings for this release:
Governor Setting
Default Value
Units
Maximum file size for a document. (Only applies during initial upload. Any pre-existing documents that exceed the setting are not affected.)
20
MB
Maximum number of rows that you can export to Excel.
25,000
rows
Maximum number of rows that can be fetched in a list view or grid portlet. (Only applies if you configure aggregation on the list view or grid portlet.)
50,000
rows
Maximum number of query rows that you can retrieve using a GEL script. (Only applies to select queries that run in GEL scripts.)
100,000
rows
Maximum number of tasks in a timesheet.
250
tasks
Maximum number of nodes that you can read or write through XOG.
150,000
nodes
Maximum number of attributes in a portfolio.
700
attributes
Maximum number of roles in a portfolio.
75
roles
Maximum time for an export to Excel before ending the export.
600
seconds
Maximum number of to do items for a task.
25
to do items
Upgrade Action
: The approved defaults are enforced to optimize performance. We recommend that administrators do not adjust these settings. However, the application detects any changes in the 
governors.properties
 file without a restart of the server. As an administrator, you can disable (not recommended) a governor entry using a -999 value in the 
governors.properties
 file.
Allow Posting of Future Timesheets
The Allow Posting of Future Timesheets option has moved from the Administration, Project Management, Settings page to the Administration, Project Management, Timesheet Options page. There are no functional changes for this option.
Upgrade Action
: If this option is currently deactivated in 
CA PPM
, when activating the 
New User Experience
 timesheet feature, this option is activated. Review the settings of this option.
Bubble Chart Display Improvements
The appearance of bubble charts has been enhanced to improve comprehension and executive decision making. Color improvements apply to default colors, optional display mappings in Studio, or the System Options color palette. The charts support color and transparency values in a standard RGBA color model. 
RGBA color values are an extension of RGB color values with an alpha channel to determine opacity. RGBA colors specify values for red, green, blue, and an alpha parameter between 0.0 (fully transparent) and 1.0 (fully opaque). The color model is a W3C standard and is supported in all major web browsers.
Instead of black borders, the lines for data points appear in a darker shade of their assigned color. The fill color for each bubble is also translucent in a lighter shade. Transparency helps identify overlapping values.
The following image shows two examples:
rgba_bubble.png
Upgrade Action
: None.
Microsoft Project Interface Changes for Release 15.1
Install the Microsoft Project (MSP) Interface at the System Level
The 
CA PPM
 Microsoft Project Interface installation is enhanced to allow administrators to install the MSP Add-In at the system level. As a result, all users of the system can access the MSP Interface. This enhancement applies for interactive and silent installations. For more information, see MSP: Manage Projects with Microsoft Project.
Upgrade Action
: We recommend that you uninstall any previous versions of the Microsoft Project Interface before installing Microsoft Project Interface Release 15.1.
Open Workbench Changes for Release 15.1
Resize Popup Windows
: In previous releases, popup windows were too small, did not resize, and required scrolling. You can now resize following commonly used pop-up windows:
  • Task Properties
  • Resource Properties
  • Project Properties
  • External Dependencies
  • Subprojects
  • Manage, Multiple Baselines
  • Preferences
  • View Definition (Project - New or Project - Edit View)
To resize a window, position the mouse pointer over the lower right corner. The pointer changes to a double arrow to indicate that you can drag to resize the window. The controls inside the dialog box move in accordance with the drag.
Aggregate custom numeric and money values
: In previous releases, Open Workbench aggregated custom numeric fields up the WBS hierarchy. You could not edit the summary values. At one point, the automatic aggregation feature was disabled. In this release, you can now decide if the numeric or money values need to be aggregated up the WBS. To enable this option, click Preferences, Options. In the resulting General dialog box, select the Aggregate custom numeric and money values check box. Summary values remain as is, and are not editable.
Upgrade Action
: None. By default, this option is not selected for a new installation and an upgrade. Once selected, its value remains as you set it through future upgrades.
Documentation and Online Help Changes for Release 15.1
  • The online help architecture has been improved. The previous server-side design has been replaced by a client-side design. Administrators no longer have to configure each server to access docops.ca.com with specific port numbers or IP addresses. 
    : We recommend that all users register at ca.com and log in to view all the documentation and not only the public pages that require no login. You can also participate in the CA Communities and access other exclusive content. SaaS SSO customers should use the same email username to log in to the CA On Demand portal and the ca.com web pages.
  • In Chrome, each time you click Help in the application, the online help may open a new window. The following workarounds are available:
    • Switch to another browser.
    • Close unwanted browser windows or tabs.
: Multiple browser windows for each mouse click on the Help link is experienced by users in different ways. To some users, it is an annoying behavior or even a known issue. To other users, it is not noticed or even considered advantageous. It establishes a persistent frame of reference based on where you were in the application when you clicked Help. For example, you may have help windows open for Resources, Financial Management, and Studio, reflecting your navigation in the application to those three areas before clicking Help.
Data Model Changes for Release 15.1
To view a summary of the data model changes for this release including the data warehouse, see 
Schema Changes 
under
 Reference.
Data Warehouse Updates for Release 15.1
Data Warehouse Options Update
  • The following two options in the Administration, General Settings, System Options, Data Warehouse Options section have been removed:
    • Disable Resource Security for Reporting?
    • Disable Investment Security for Reporting?
  • The following four fields are renamed. There is no change in the functionality.
    • 'Store Weekly Time Increments?' is renamed to 'Include Weekly Period Data'
    • '
      Store Monthly Time Increments?' is renamed to 'Include Monthly Period Data'
    • '
      Store Fiscal Time Increments?' is renamed to 'Include Fiscal Period Data'
    • '
      One Set of Fiscal Periods?' is renamed to 'Consistent Fiscal Periods across Entities'
  • The following option is newly added:
    • Include only financial Plan of Record. Specifies whether to include all financial plans (cost plans, budget plans, and benefit plans) or only the current budget plan and the cost plan of record in the Data Warehouse. Out-of-the-box, only the current budget plan, the cost plan of record, and associated benefit plans are included in the Data Warehouse. To report on only the current budget plan or the cost plan of record, keep the option selected. To compare previous plans with current plans on investments, unselect this option. Unchecking this option can impact the Data Warehouse performance. You may notice a significant difference in the load time for large data sets.
For detailed descriptions of the fields, see Configure the Data Warehouse and Advanced Reporting Domains.
Performance Improvement for Incremental Updates
Performance has been improved for the Incremental Data Warehouse load specifically in the following areas:
  • Resource availability
  • Project teams
  • Task assignments
The incremental load time is reduced by adding some indexes and using temporary processing tables.
Security Model Update
The Load Data Warehouse Access Rights job has been rewritten for faster performance. As a result, the performance of the Load Data Warehouse Access Rights job is significantly improved especially for customers with a large dataset.
The following improvements were made to the Data Warehouse schema for the security model:
  • The following security tables have been removed and recreated as views to support existing reports. The views are not for use when building new reports.
    • DWH_INV_SECURITY
    • DWH_RES_SECURITY
  • The 
    CA PPM
     security tables are now copied to the Data Warehouse with minor enhancements and consistent naming conventions.
  • The views are recreated and used for generating ad hoc views and reports. 
Upgrade Actions
:
  1. After upgrading, run the following jobs in the listed order:
    • Load Data Warehouse (select the Full Load option)
    • Load Data Warehouse Access Rights
  2. Do not use the following views to build new reports. The views were created to support the existing reports that were based on the deprecated tables. The existing reports will still work, but you may experience slow performance:
    • DWH_INV_SECURITY
    • DWH_RES_SECURITY
  3. Use the following views to build new reports:
    • DWH_RES_SECURITY_v
    • DWH_INV_SECURITY_v
Known Issues for Release 15.1
The following section lists the Known Issues at the time this release is delivered. See the CA PPM Knowledge Base available at support.ca.com for the latest known issues.
Known Issues for the 
New User Experience
  • Create Project Button Appears for Users Without Create Project Access Right in the 
    New User Experience
    The +Project button always appears for users that have access to the 
    New User Experience
     project tiles page. The button appears even if the user does not have the access right to create projects. To limit who can create projects, we recommend that you limit the view access of the project templates in Classic 
    CA PPM
    . Without access to project templates, a user is unable to create projects in the 
    New User Experience
    .
  • Invalid date message appears in date fields of the 
    New User Experience
To populate the date fields in the 
New User Experience
, you can either use the date picker or manually enter a date. To manually enter a date, follow the exact format specified below or you receive an "Invalid Date" error message.
      • Format = Mmm dd yyyy in English locale and language (for example, May 02 2016).
      • The format is different for different combinations of language and locale.
      • Any days below 10 must have a zero.
      • The month is the first three letters with the first letter capitalized.
      • The date does not have a comma.
Once you enter the date in the correct format and move away from the field, it is accepted and saved. We recommend that you use the date picker instead of manually entering a specific value in the date fields.
  • Prompt text disappears from fields in the 
    New User Experience
     when using Internet Explorer
When using the 
New User Experience
 with Internet Explorer, the prompt text for a field disappears as soon as the field has focus. This is a known issue for Microsoft Internet Explorer.
  • Timesheet Review and Approval page only shows the booked time in hours
Timesheet users can see a visual gauge indicating Total Hours (or Days) booked on My Timesheet over Total Hours (or Days) of available work time. The Timesheet Review and Approval page only shows the time in hours (instead of days) if your administrator has set up the time entry display unit as Days in Classic 
CA PPM
.
  • Timesheet Review and Approval page - adjustment timesheet in progress increases the team member count
Timesheet Approvers may see an increased team member count when there are adjustment timesheets that are in progress. When a posted timesheet is being adjusted and an adjustment timesheet is created, while this timesheet is in Open, Submitted, Approved or Returned state, the adjustment timesheet appears on a separate row. As a result, the Timesheet Approver sees two rows for the same team member. One row is for the posted timesheet that is being adjusted, and the second row is for the adjustment timesheet that is in progress for any of the other states.
  • Timesheet Review and Approval page - click Enter to filter the Team Member field
When a Timesheet Approver enters search criteria in the team member search field, filtered results are not returned until you click Enter. After the results appear, clicking the X to clear the search field does not update the results until you click Enter.
  • Link in email notification for submitted timesheet goes to a blank page
When a Timesheet Approver receives a notification that a timesheet has been submitted, the URL link goes to a blank page. After landing on the blank page, the approver can click the timesheets menu link. Clicking this link takes the approver to the Review & Approve page where the approver can locate and take action on the submitted timesheet.
  • Timesheet Review and Approval page - hours may be inflated with incidents or indirect time on pre-existing timesheets from Classic 
    CA PPM
There may be an existing timesheet created in Classic 
CA PPM
 that include incidents and/or indirect time. In the 
New User Experience
, incidents and indirect time entries are not available or supported. The expectation is not to see them on timesheets in the 
New User Experience
. The My Timesheet view shows the correct total hours, excluding the incidents and indirect time. The Review & Approve timesheet summary total hours is incorrect and includes the incidents and indirect time hours. On this page, these items are incorrect on the team member gauge, in the fly-out for the gauge, and the total summary. However, if this is a submitted timesheet and the user drills into the detailed timesheet grid, the correct information appears and excludes these items.
  • When selecting a project template, the Carousel displays, at most, 25 project templates
The 
New User Experience
 only displays, at most, 25 project templates in the carousel. As a workaround, search to find the specific project templates that you want to reduce the project template result set.
  • An unclear error message appears when the user does not have the correct rights to perform a task
If the user does not have the proper access rights, the 
New User Experience
 may display the following unclear error message:
API-1007 : You are not authorized to retrieve resource(s). Contact your system administrator for necessary security rights.
The access rights are not necessarily specific to the resource object. Instead, the rights are related to the operation that the user wants to perform.
  • When accessing links to the 
    New User Experience
     that are not directed to the Project and Timesheet home pages, and you are not logged in to the 
    New User Experience
    , you are still directed to the Project and Timesheet home pages
If you have a deep link that goes to a place other than your default home page in the 
New User Experience
, and you are required to enter your login credentials, you are still taken to your default home page.
Known Issues for Advanced Reporting
  • Advanced Reporting error when exporting the Project Status Summary Report Gantt chart to Excel (Paginated)
In Advanced Reporting, when you export the Project Status Summary Report Gantt Chart to Excel (Paginated), you receive an error. The report is not exported to Excel along with the Gantt charts. This is a known issue due to an Excel limitation of 255 columns.
  • Advanced Reporting window automatically minimizes when using Internet Explorer
When using 
CA PPM
 with Internet Explorer and when you click Advanced Reporting, the browser window automatically minimizes in the task bar. If you click the browser icon to maximize the window, and then click a reporting option (for example, Reports, View List), the browser window automatically minimizes again. You may also notice that the window is not minimized, but is hidden in the background behind something on your screen. As a workaround, open a new empty tab in Internet Explorer or minimize all desktop applications other than Internet Explorer.
Known Issues for Financial Management
  • Cost Plan List actions are removed if you add an action to the Cost Plan List Actions Menu
Actions on the Cost Plan List are removed if you add an action to the actions menu. Typically, you should be able to add an action to the Cost Plan List actions menu and the existing entries (Set Plan of Record, Submit Plan of Record for Approval, Copy Cost Plan, New from Investment Team, New from Task Assignments) would not be removed. Due to this known issue, these actions are removed if you add any action to the Cost Plan List actions menu. As a workaround, click Administration, Studio, Views. Filter by view=revmgr.costplanList::revmgr.costplanList and click Restore defaults.
Evaluate Before You Install or Upgrade
The Installation Checker (checkinstall) utility assesses an installation or an upgrade. The utility runs automatically at the start of an installation or upgrade and at the end of an upgrade attempt. You can also run it manually. The utility produces a report results file (precheck-results.html) in the <install-root>/checkinstall/check-logs directory.
Upgrade Action
: For best results, run the Installation Checker before starting the full installation and upgrade process. Carefully evaluate and resolve warnings before proceeding.
Run the Installation Checker Manually
Follow these steps:
  1. Extract the 
    CA PPM
    installer to the 
    CA PPM
    application server.
  2. Open a command prompt and navigate to the checkinstall directory located in the directory to which you extracted the installer.
  3. Invoke the checkinstall command:
    UNIX
    :
    sh checkinstall.sh
    Windows
    :
    checkinstall.bat
    You are asked for the Operator Username and Operator Email. This information refers to the user who is upgrading or installing and the email of the user. This information is stored as a record in the installation log.
  4. Verify the results.
    The results contain any warnings and errors and also indicate any customizations that you have made. Review the customizations and make adjustments for the upgrade as necessary.
Make Third-Party Jar Files Accessible to the Installer
Because of licensing restrictions for some third-party library JAR files (currently the jgroups-all.jar and the xinclude.jar), changes were made in how these files ship. The JAR files are shipped separately from the 
CA PPM
image in the installation media. The install.jar image does not contain the files mentioned. Any install packages for a previous version included in the install.jar also exclude the .jar files. For each release of
CA PPM
, the .jar files are bundled into a folder on the installation media containing third-party libraries .jar file. For Release 15.x, the file is named
thirdparty.libs.15.x.0.jar
.
Upgrade Action
: Retrieve the
thirdparty.libs.15.x.0.jar
file from the installation media. Place the .jar file in a location in your file system so that it is accessible to the installer.
Tip
: To keep the installer from prompting you for the file location, place the JAR file in the installation root directory. If you place the .jar file in another directory, the installer prompts you for the file location.
Upgrading Large Data Sets
If your 
CA PPM
upgrade processes a large volume of data, we recommend that you override the default memory settings that are used by the upgrade.
You can override the default memory settings for Release 14.4. Create a file that is named
memory.properties
and place it in the $cappm/config directory. Set the desired memory values in that file.
Here are the default values that the upgrade uses:
defaultScriptMaxMem=1024m defaultScriptPermGenMem=128m
Here are some sample settings in the
memory.properties
file:
defaultScriptMaxMem=2560m defaultScriptPermGenMem=512m
CA PPM
 Upgrade Overview 
Follow these steps:
  1. Perform the pre-upgrade requirements.
    1. Install the prerequisite third-party software. For the supporting operating environment information, see
      Compatibilities
      in the Release Notes
      The following important changes are included:
      -The Java runtime must be a supported 64-bit version.
      -The supported Oracle databases for Release 15.1 are Oracle 11.2.0.4 and 12.1.0.2.
      -The supported MS SQL Server databases for Release 15.1 are 2012 Enterprise Edition: Service Pack 3 and 2014 Enterprise Edition: Service Pack 1.
    2. Create a full backup of your database, file systems, and customizations (if applicable). To keep sequences in line, take a
      cold
      backup.
    3. Remove customer-added database triggers, stored procedures, indexes, views, and constraints before upgrading.
      As a result of the database schema changes for this release, most custom triggers, indexes, and constraints can cause the upgrade to fail. We recommend
      removing
      , not disabling, customer-added triggers.
  2. Perform the remaining pre-upgrade steps and then start the upgrade as detailed in
    Upgrade CA PPM
  3. Some important changes include:
    • The installation for an upgrade prompts you for the current and a target 
      CA PPM
      folder. You can specify the same folder or different folders. If you specify the same folder for both, the existing folder is renamed. Then, Release 15.1 is installed into an empty folder with the target folder name.
    • If you are installing on a different server, review the information about setting up the application server in
      Installing and Upgrading
      .
    • The HTTP and HTTPS Entry URL fields completed for the 
      CA PPM
      server in
      CA PPM
      System Administration (CSA) cannot be
      localhost
      when Jaspersoft is integrated with
      CA PPM
      . When you use Jaspersoft, the complete URLs must be entered on the Application subtab of the Properties tab for the 
      CA PPM
      server.
  4. Complete the following post-installation steps:
    1. Verify that all installation steps completed successfully by reviewing the post upgrade report that the installer generates.
    2. Review the
      CA PPM
      System Administration server admin.log and install.log for errors.
    3. Reapply any database and file system customizations.
    4. Run the Oracle Table Analyze Job from
      CA PPM
      after the upgrade is done to gather schema statistics. The expected time for this job to complete depends on the size of the database. We recommend that you run this job right after the upgrade and at off peak hours thereafter.
      If you use a custom statistics job, refer to the updated Oracle Table Analyze Job procedure in the
      CA PPM
      schema in Release 15.1 (CMN_JOB_ANALYZE_SP) and make necessary corrections in the custom statistics job.
  5. Upgrade your Advanced Reporting content or configure Advanced Reporting for the first time:
    1. Set up the Data Warehouse database and populate it with 
      CA PPM
      data.
    2. Install Jaspersoft and import the domain information for reporting.
  6. Install your current add-ins and connectors if an upgrade is desired.
    • Review
      Installing and Upgrading 
      for information about installing add-ins.
    • Back up your 
      CA PPM
      installation before installing each add-in so that you can restore the application if necessary.
    • Apply the Upgrade Ready content for those items that you are actively using.
      Consider the configurations that you have made to items before applying them. Applying modified items overwrites your configurations.
      Best Practice
      : If you modified stock 
      CA PPM
      content, copy the modified content before upgrading. Then, apply the new incoming stock 
      CA PPM
      content, and retrofit the modifications to the new content.
    • Read the PMO Accelerator Release Notes for important information about what has changed for the PMO Accelerator.
    • Review the
      System: PPM Content
      add-in available on the Content Add-ins page for upgrade-ready content. This page is available from the Administration menu. To accept the new Release 15.1 upgraded content, apply the changes.
  7. Review the Studio views and system content and manually upgrade as needed.
    The upgrade preserves all pre-existing Studio view configurations. If an existing view has configurations or if the object for the view is partitioned, the system does not automatically upgrade the view or the partition.
    To determine which views were not automatically upgraded, use the Studio Views list page.
    Use these tips to help you review the views:
    • The Last Version column identifies changes to stock views in Release 15.1.
    • If a view was automatically upgraded as part of the upgrade process, a checkmark appears in the Upgraded column. No further action is required.
    • If a view that changed in Release 15.1 was not upgraded due to pre-existing configurations, decide whether to apply the changed view.
      Look for views with the following column information:
      Last Version column=14.2 and the Upgraded column= unchecked.
  8. Verify your NSQL queries.
    During the upgrade, the checkinstall utility automatically verifies NSQL queries. Results are captured in the postcheck-results.html file of the checkinstall-results.zip file. This log contains the following information:
    • Query name
    • Query ID
    • Content Source
    • Query ID from CMN_NSQL_QUERIES of the query that failed validation
    This release contains database schema changes. To ensure that your custom portlets work, correct any invalid NSQL queries.
    For more information about the database schema changes, see Data Model Changes.
    Upgrade Action
    :
    If the query can be changed in Studio, complete these steps:
    1. Go to the NSQL tab for each failing query.
    2. Click the Preview button.
    3. Review the errors.
    4. Repair the broken query constructs or fields.
    5. Click the Preview button.
    6. Confirm that the NSQL query is valid.
      If the query is in use by active portlets and cannot be edited in Studio, complete these steps:
    7. Use the XML Open Gateway (XOG) to export the failing query.
    8. Correct the broken query constructs or fields.
    9. Use XOG to import the corrected query.
    10. In Studio, go to the NSQL tab for the imported query and click the Preview button.
    11. Confirm that the NSQL query is valid.
  9. Save the Upgrade Check Install Results Package.
    The upgrade process produces a zipped file that contains all of the artifacts that were created during the upgrade. Review the contents and save the zip package for future reference.
    The files are zipped into an archive that has a timestamp-encoded name (for example, checkinstall-results_2014-08-17_16-48-31.zip). This file is located in the checkinstall/check-logs directory, and if possible, the file is copied into the <target runtime dir>/logs/checkinstall directory.
Upgrade Suggestion for Niku 6.x, Clarity 7.x, and CA Clarity 8.x
As a best practice, we recommend the following steps for customers who are upgrading from older releases:
  1. Upgrade to 
    CA PPM
    12.1.1, 12.1.2 or 12.1.3.
  2. Verify that the upgrade is successful and run the CSA Health Report that is available from
    CA PPM
    System Administration.
  3. Create a full backup of the database and runtime file system.
  4. Proceed with the upgrade to Release 15.x.
MS SQL Server Database Compatibility Level
Release 15.1 supports database compatibility levels for SQL Server 2012 (119) and SQL Server 2014 (120). A new installation of Release 15.1 on SQL Server 2012 has the correct compatibility level of 110. If you are using SQL Server 2014 for Release 15.1, set the compatibility level to 120 from SQL Server Management Studio or use the following command:
EXEC SP_DBCMPTLEVEL <database>, 120
SQL Server 2005 compatibility level (90) has been removed and is no longer supported.
To identify the compatibility level, use the following query:
SELECT NAME DATABASENAME ,COMPATIBILITY_LEVEL COMPATIBILITYLEVEL FROM SYS.DATABASES
Upgrade Action
: None
Oracle Database Only PRJ_BLB_SLICES Table
The ID, UNIT, LAST_UPDATED_DATE and LAST_UPDATED_BY columns in the PRJ_BLB_SLICES table have been dropped. If you are using Oracle, the table is replicated before the columns are dropped. The replication requires you to verify that the tablespace that PRJ_BLB_SLICES occupies is large enough to accommodate the temporary size increase.
Upgrade Action
:
To determine if the tablespace can deal with this condition, have your database administrator (as sysdba) run the following query. Change the schema owner to the owner of the 
CA PPM
schema:
select SLC.owner, SLC.table_name, SLC.TABLESPACE_NAME, SLC.MB MB_NEEDED,  TBSPC.MB_FREE MB_FREE, SIZING.MAX_MB, SIZING.MB_USED, EXT.AUTOEXTENSIBLE FROM (select owner, table_name, NVL(round((num_rows*avg_row_len)/(1024*1024)),0) MB, TABLESPACE_NAME from all_tables where owner = 'CLARITY' and table_name = 'PRJ_BLB_SLICES') SLC INNER JOIN (select df.tablespace_name, (df.totalspace - tu.totalusedspace) "MB_FREE" from (select tablespace_name, round(sum(bytes) / 1048576) TotalSpace from dba_data_files group by tablespace_name) df, (select round(sum(bytes)/(1024*1024)) totalusedspace, tablespace_name from dba_segments group by tablespace_name) tu where df.tablespace_name = tu.tablespace_name) TBSPC ON (SLC.TABLESPACE_NAME = TBSPC.TABLESPACE_NAME) INNER JOIN (select distinct(autoextensible), tablespace_name from dba_data_files) EXT on (slc.tablespace_name = ext.tablespace_name) INNER JOIN (select tablespace_name , count(*) as no_of_data_files , sum(MAXBYTES)/(1024*1024)*count(*) as MAX_MB , sum(user_bytes)/(1024*1024) MB_USED , round((sum(user_bytes)/(1024*1024))/(sum(MAXBYTES)/(1024*1024))*100,2) PERCENT_USED from dba_data_files group by tablespace_name) SIZING ON (SLC.TABLESPACE_NAME = SIZING.TABLESPACE_NAME)
The following example shows the kind of results that the query returns:
OWNER TABLE_NAME TABLESPACE_NAME MB_NEEDED MB_FREE MAX_MB MB_USED AUTO-EXTENSIBLE CLARITY PRJ_BLB_SLICES USERS_LARGE 1306 5020 90000 15997 YES
If AUTOEXTENSIBLE is YES:
The tablespace for PRJ_BLB_SLICES can grow automatically up to the MAX_MB value. Ensure that the MAX_MB value is higher than the MB_NEEDED + MB_USED.
If AUTOEXTENSIBLE is NO:
Ensure that the MB_NEEDED value is less than MB_FREE. If the MB_NEEDED value is not lower, the database administrator can allocate or extend extra data files to the tablespace under the TABLESPACE_NAME column.
We recommend increasing the tablespace at least 20 percent more than is needed. The increase helps to ensure that the tablespace can accommodate standard data growth and the temporary replication.
Filestore and Search Index Location Changes
Two significant changes to the 13.x, 14.1, and 14.2 upgrade processes directly affect the filestore feature. The changes require you to act during the upgrade process to ensure that the filestore feature operates correctly after the upgrade.
The actions are necessary only if your files are not stored in the database. If files are stored in the database, no action is required.
You can determine if your files are stored in the database using the
CA PPM
 System Administration (CSA) application. Log in to CSA and navigate to the Documents and Search link under the Properties tab, then review the Store Files in Database property.
If the database is not the filestore repository, action is required. Failure to follow the recommended steps can lead to permanent loss of the filestore contents.
The following changes were made to the upgrade process in Version 13:
  • The upgrade process always installs to an empty destination folder. During the upgrade, files and folders that exist in the target installation folder are moved to a new location before the new files are installed. If the filestore folder is located in the runtime folder, it is moved with the other content (
    not recommended
    ). If the filestore is located outside the runtime folder (the
    recommended
    configuration), the filestore location is not moved or copied from the backup location.
  • The filestore and search index folder structures were altered to accommodate architectural changes in Version 13. This change requires action for all Release 13.x and 14.x upgrades, whether the filestore was located in the installation folder or not.
Your action depends on the following factors:
  • Where the filestore was before the upgrade
  • The target installation folder that is selected during the upgrade
The correction must be made immediately after the upgrade completes, before any files are added to the filestore. Any files added to the filestore before the correction is made must be manually preserved using the following steps:
  1. Use 
    CA PPM
    to retrieve the newly checked-in documents and save them to a temporary location on the file system.
  2. Perform the steps for the appropriate use case (A, B, or C) in the following Upgrade Action.
  3. To check the saved documents back into the 
    CA PPM
    filestore, use
    CA PPM
    .
  4. Execute the following commands from the <runtime>/bin folder:
    admin search recreate-index-files admin search recreate-index-data
Upgrade Action
: Complete the filestore and search index correction procedure.
Before you start, create a backup of the filestore so that recovery is possible in the event of an unexpected problem. Your document store could be used before this procedure can be completed. If so, the newly included documents must be added back to the filestore after you complete the correction procedure.
The following use cases illustrate the actions to take. To determine the correct course of action, use the filestore location and target installation folder.
Use Case A
  • Filestore location: The filestore was located in the 
    CA PPM
    runtime folder before the upgrade.
  • Target installation folder: The existing (preupgrade) 
    CA PPM
    runtime folder was selected as the target installation folder.
Before the upgrade process ran, the file or index folder was in the <runtime> folder. The upgrade process moved the file or folder to a folder named <runtime>_prev based on the chosen upgrade or installation option. The move resulted in the file or index folder being located in the <runtime>_prev folder. The file or index folder must be moved from the <runtime>_prev folder to another location because any subsequent upgrade attempt deletes this folder.
Perform these steps for this use case:
  1. If before the upgrade the filestore location was <runtime>/filestore, copy or move the folders under <runtime>_prev/filestore to this new path:
    <new directory>/filestore/clarity
    Where <new directory> is located outside of the upgrade resulting <runtime> directory. Having the location outside of the runtime folder follows best practices. Placing the folder outside the 
    CA PPM
    installation directory also ensures that this process is not repeated when 
    CA PPM
    is upgraded.
    Log in to the CSA application, navigate to the Documents and Search link under the Properties tab, and update the Filestore Directory location. For example, if the filestore path is <old clarity install directory>/filestore, modify the path to <new directory>/filestore.
    Do not append ‘clarity’ to the path in the CSA. The 
    CA PPM
    architecture adds this update internally.
  2. If before the upgrade the search index directory location was <runtime>/searchindex, copy or move the folders under <runtime>_prev/searchindex to this new path:
    <new directory>/ searchindex /clarity
    Where <new directory> is located outside of the upgrade resulting <runtime> directory. Having the location outside of the runtime folder follows best practices.
    Log in to the CSA application and navigate to the Documents and Search link under the Properties tab and update the Index Directory location. For example, if the filestore path is <old clarity install directory>/searchindex, modify the path to <new directory>/searchindex.
    Do not append ‘clarity’ to the path in the CSA. The 
    CA PPM
    architecture adds this update internally.
  3. Execute the following command from the <runtime>/bin folder:
    admin search recreate-index-files admin search recreate-index-data
Use Case B
  • Filestore location: The filestore was located in the runtime folder before the upgrade.
  • Target installation folder: A new, empty folder was selected as the target install folder.
Before the upgrade process ran, the file or index folder was located in the <runtime> folder. The upgrade process produced a different folder named <new runtime>. This process was based on the upgrade or installation option to select a different folder for the upgrade result than the current one. This choice has resulted in the file or index folder being located in the <runtime> folder.
Perform these steps for this use case:
  1. If before the upgrade the filestore location was <runtime>/filestore, copy or move the folders under <runtime>/filestore to this new path:
    <new directory>/filestore/clarity
    Where <new directory> is located outside of the upgrade resulting <runtime> directory. Having the location outside of the runtime folder follows best practices. Locating the folder outside the installation directory ensures that this process is not repeated in the future when 
    CA PPM
    is upgraded.
    Log in to the CSA application and navigate to the Documents and Search link under the Properties tab and update the Filestore Directory location. For example, if the filestore path is <old clarity install directory>/filestore, modify the path to <new directory>/filestore.
    Do not append ‘clarity’ to the path in the CSA. The 
    CA PPM
    architecture adds this update internally.
  2. If before the upgrade the search index directory location was <runtime>/searchindex, copy or move the folders under <runtime>/searchindex to this new path:
    <new directory>/ searchindex /clarity
    Where <new directory> is located outside the upgrade resulting <runtime> directory. Having the location outside the runtime folder follows best practices.
    Log in to the CSA application, navigate to the Documents and Search link under the Properties tab, and update the Index Directory location. For example, if the filestore path is <old clarity install directory>/searchindex, modify the path to <new directory>/searchindex.
    Do not append ‘clarity’ to the path in the CSA. The 
    CA PPM
    architecture adds this update internally.
  3. Execute the following command from the <runtime>/bin folder:
    admin search recreate-index-files admin search recreate-index-data
Use Case C
  • Filestore location: The filestore was located outside the runtime folder before the upgrade.
  • Target installation folder: The target installation folder is not relevant to this use case. These steps must be performed for all upgrades with an external filestore.
The file or index folder is not located in the <runtime> folder.
Perform these steps for this use case:
  1. If the previous filestore folder path is now located in <some folder>/filestore, copy or move the folders under <some folder>/filestore to this new path:
    <some folder>/filestore/clarity
  2. If the previous search index folder path is now located in <some folder>/searchindex, copy or move the folders under <some folder>/seachindex to this new path:
    <some folder>/seachindex/clarity
  3. Execute the following command from the <runtime>/bin folder:
    admin search recreate-index-files admin search recreate-index-data
No modification to the Filestore Directory or Index Directory properties is needed. You can view these properties from the Properties tab, Documents and Search subtab in the CSA application.
Do not append ‘clarity’ to the path in the CSA. The 
CA PPM
architecture adds this update internally.
Preserve Your File Directory Customizations
During the upgrade, you are prompted for the target installation directory. New preupgrade and postupgrade steps let you copy files to and from the 
CA PPM
directory using ant-based scripting. Use ant scripts to automate preserving and restoring customization in the 
CA PPM
directories.
Templates are provided in release-specific upgrade folders that are located in the installer root directory (at the same level as the install.bat file). The templates are:
preprocess-upgrade.xml
and
postprocess-upgrade.xml
.
Example of preprocess-upgrade.xml script
<project name="content" default="upgrade" basedir="."> <target name="upgrade"> <echo>Preserving customer specified files prior to upgrade from install.dir = ${install.dir}</echo> <if fileexists="${install.dir}" not="true"> <fail>Install dir not specified = ${install.dir}</fail> </if> <delete dir="upgrade_temp"/> <mkdir dir="upgrade_temp" /> <!-- Uncomment the copy below and list the files to be included for preservation --> <!--<copy todir="upgrade_temp"> <fileset dir="${install.dir}" > <include name="myfiles/my*.*"/> <include name="abb/*01.jar"/> <include name="a*01.jar"/> </fileset> </copy>--> </target> </project>
Example of postprocess-upgrade.xml script
<project name="content" default="upgrade" basedir="."> <target name="upgrade"> <echo>Restoring customer specified files after upgrade to install.dir = ${install.target.dir}</echo> <if fileexists="${install.target.dir}" not="true"> <fail>Install dir not specified = ${install.target.dir}</fail> </if> <!-- Uncomment the copy task below and list the files to be restored that were preserved in the preprocess-upgrade.xml script.--> <!--<copy todir="${install.target.dir}"> <fileset dir="upgrade_temp" > <include name="myfiles/my*.*"/> <include name="abb/*01.jar"/> <include name="a*01.jar"/> </fileset> </copy>--> </target> </project>