Clarity PPM 15.6 Change Impact and Upgrade

The Change Impact and Upgrade page highlights significant changes, required actions, known issues, and recommended options for customers upgrading from the previous release to cappm Release 15.6. Plan your cappm upgrade and determine the options that fit your business needs. Teams can also use this information to plan your new feature adoption, onboarding, and training efforts. 
Change Impact and Upgrade 
page highlights significant changes, required actions, known issues, and recommended options for customers upgrading from the previous release to 
Clarity PPM
 Release 15.6. Plan your 
Clarity PPM
 upgrade and determine the options that fit your business needs. Teams can also use this information to plan your new feature adoption, onboarding, and training efforts. 
 For example, you are upgrading from Clarity PPM Release 15.1 to 15.6. Review the changes in releases 15.2, 15.3, 15.4, 15.4.1, 15.5, 15.5.1, and 15.6 before and after you upgrade. To switch to the 
Change Impact and Upgrade
 page for each release, click the 
 menu at the top of this page. Check back often for updated content, especially if you downloaded a PDF or EPUB file. The English edition of this documentation is periodically updated with new information including new examples, explanations, corrections, and patch information.
To prepare for an upgrade to 
Clarity PPM
 Release 15.6, review the supported upgrade paths, features, enhancements, and required upgrade actions. The following information summarizes how the new changes introduced in this release impact your upgrade experience.
Click here to expand a more detailed Table of Contents...
Clarity PPM 15.6 Changes: New User Experience Features
New Ideas Page
Upgrade Action
: No action is required; however, as an administrator, revisit access right assignments at the instance, OBS, global, and PMO group levels. This feature includes a new 
Idea Management - Navigate
 access right which allows users to access the new Ideas page in the new user experience. The PMO System Administrator Security group includes this access right. All users in the group inherit the group access rights. Additional access rights determine which ideas the user can view or edit.
The Clarity PPM Brand is Back
With the acquisition of CA Technologies by Broadcom, the 
Clarity PPM
 product name, formerly rebranded as 
, has been restored in Release 15.6 and in the patch. The product is now branded CA Clarity Project and Portfolio Management, CA Clarity PPM, or simply, 
Clarity PPM
Upgrade Action
: No action is required. 
Historic references with mixed branding will continue to appear throughout the application and in the online documentation, community content, Support KB articles, videos, and other content.
  • Users upgrading from and previous releases can expect to see rebranded Login pages for Classic PPM and the 
    New User Experience
     and a new Clarity icon in web browser tabs. 
  • The copyright notice on the Login and About pages has been changed from CA to Broadcom.
  • On Classic and New UX pages, the CA logo has been replaced by the new 
    Clarity PPM
Timesheet Enhancements
When you add work items to a timesheet, the filter field to search by Task Name also supports searching by Task ID (Task Code). The following updates now appear on timesheets in the New User Experience:
  • The user interface text label has been updated and users can enter a portion of a task name or ID to view matching suggestions for tasks by name or ID (code). 
  • The column header in the search results for the task field now shows Task Name/ID and the values in each row appear in the Task Name / Task ID format (for example, Complete Project Plan / LM.011.050).
  • Additional changes appear on the timesheet details page where time entries appear. The column for the Project/Task work displays a Task Name (Task ID) format followed by Phase Name on the next line.
  • Task IDs are optional. When a task has no ID, only the task name appears.
Upgrade Action
: No action is required. After an upgrade, users automatically receive these updates.
Introducing the Phoenix UI Theme
The patch and Release 15.6 also introduce a new 
Phoenix UI
 theme designed to invite Classic Clarity PPM users into the new aesthetics and styling of the Clarity Modern UX (formerly introduced with CA PPM 15.1 as the 
New User Experience
). This release also includes a new matching theme in Jaspersoft and new report style and ad hoc report templates for the Modern UX.
Upgrade Action
: No action is required. The PMO Accelerator add-in includes matching new Jaspersoft Report style templates to support this optional new theme. The new templates are similar to the existing Teal and Gray theme.
To learn more about applying UI themes, see CA Clarity PPM Studio UI Themes in the Reference section of the documentation (English edition only).
 Button Name Changed to 
View Options
On the following pages, the Settings button has been renamed to View Options:
     (since the page is new this release, no net change impact here)
     (the global Tasks page, not the Project Tasks page)
    Roadmap Items
     (grid, board, and timeline)
    Custom Investments
    Custom Subobjects
     under Projects (including the system blueprint module for the 
    Status Report
     grid page)
Upgrade Action
: No action is required. Update any custom policies, procedures, or learning materials.
Screenshots on this page have been reduced to prevent clutter, long pages, and scrolling. To see more details, zoom-in (magnify your browser view) or right-click an image and select 
Open image in new tab
Clarity PPM 15.6 Changes: Classic PPM Administrative Features
Add and Adjust Timesheet Entries for Incidents With Greater Flexibility
In previous releases, you could not adjust a timesheet row for an incident if its parent application was closed for time entry or inactive. Users could 
 time against the same incident, but could not 
 the time entry because the row was read- only since the associated application was closed for time entry. As a workaround, you had to re-open the application for time entry.
In this release, adjusted timesheet rows for incidents allow editing when the parent investment is active or inactive, and when the Open for Time Entry setting is selected (open) or clear (closed).
Upgrade Action
: No action is required. You can enter time through a timesheet or through the incident record. In this release, you can also make corrective adjustments for incidents without the constraints dictated by the parent investment settings. To verify the new behavior, perform the following steps:
  1. In Classic PPM, click 
    Portfolio Management
  2. Create an application.
  3. On the 
    Application Settings
     subpage, clear the 
    Open for Time Entry
  4. On the 
    Incident Categories
     submenu, select any of the available categories to associate with the application that you created in an earlier step.
  5. On the 
     submenu, create an incident.
  6. Configure the resource (user) you are using to perform these steps. Select 
    Open for Time Entry
     and set 
    Track Mode
     set to 
  7. In the Classic PPM Timesheets list, open your timesheet and click 
    Add Incident
     (this feature is available only in Classic Clarity PPM).
  8. Enter time against the incident.
  9. Submit, approve, and post the timesheet.
  10. Edit the timesheet. You can now adjust the time entries for incidents. You can also adjust time entries even if the parent investment is inactive.
New CSA Properties for LDAP (On-Premise Only)
In previous releases, the LDAP - Synchronize Obsolete Users job could run over multiple days without completion. Your business users accessing reports and other users in your LDAP were not fully synchronized with CA PPM.
To enhance performance when adding, removing, or deactivating users from 
Clarity PPM
 based on LDAP group membership, on-premise editions of this release include two new options in Clarity System Administration (CSA):
  • Use Group Memberships
  • Group Identifier on User
Upgrade Action
: No action is required; however, on-premise administrators have two new options for synchronizing users between 
Clarity PPM
 and their LDAP:
    Use Group Memberships: 
    When you select this option, the LDAP - Synchronize Obsolete Users job uses the value of the new 
    Group Identifier on Users 
    option to perform the synchronization, improving performance.
    Group Identifier on Users
    : This new field allows you to specify a different reverse relationship from users to groups in your active directory. The value of this field is used only if you select Use Group Memberships. The default value is 
Full Updates of the Rate Matrix Extraction Job Now Remove Inactive Investments
In previous releases, running the Rate Matrix Extraction job with the following parameters did not remove inactive projects and non-project investment objects (NPIOs):
    Prepare Rate Matrix Data
    Update Rate Matrix Data
Inactive projects and NPIOs remained in the NBI_PROJ_RES_RATES_AND_COSTS table.
Upgrade Action
: No action is required; however, administrators can now expect the following behavior when running the Rate Matrix Extraction job.
  1. Select the 
    Prepare Rate Matrix Data
    Update Rate Matrix Data
  2. Clear the 
    Incremental Update Only
     check box. The application implements the new behavior only for full updates of the Rate Matrix Extraction job.
  3. When the job runs with these parameters, the existing table is truncated and then rebuilt with only matrix rows for 
     projects and NPIOs.
If the 
Incremental Update Only
 check box is selected, the rows for 
 investments remain in the table.
Datamart Impacts: 
The following related behavior impacts the Datamart Extraction and Datamart Rollup jobs. For 
 investments with changes that require matrix rates, the datamart tables might not have financial updates.
To see the final updated financial data for changes made while an investment is 
 and no rates exist in the Rate Matrix Extraction table, follow these steps:
  1. Activate the investment.
  2. Run the following jobs:
    • Rate Matrix Extraction (clear the 
      Incremental Update Only
       check box)
    • Datamart Extraction
    • Datamart Rollup
  3. You can now deactivate the investment. The updated data in the datamart tables remains unchanged.
Time Slicing Job PRTEAM Last Updated Date and Last Updated By Improvements
In this release, after the Time Slicing job re-slices data, it no longer updates the Last Updated Date or Last Updated By fields on the PRTEAM record because the job is only making an indirect update to the allocation data.
In previous releases, after running the Time Slicing job, the PRTEAM record could sometimes show that it was last updated by an inactive user in the audit trail. This behavior would result when all of the following steps occurred:
  1. User A logs in to Clarity PPM.
  2. User A makes an allocation change for another team member (User B) through their calendar.
  3. An administrator inactivates User B.
  4. Another active user (User C) logs in and runs the Time Slicing job.
In previous releases, when a resource calendar is updated, it causes the Time Slicing job to reslice allocation data based on the new resource availability. The Last Updated Date field is updated on the PRTEAM record because the Time Slicing job last processed the allocation data. The Time Slicing job does not update the Last Updated By field.
The old behavior made it appear as though an inactive user changed the record recently. The PRTEAM.last_update_date and CMN_AUDIT trail showed confusing timestamp information. In 15.6, the correct behavior now occurs. The record for User B on PRTEAM.last_updated_date should not reflect the date when the Time Slicing job last processed the record. Instead, the date when User A last updated the allocation appears.
Upgrade Action
: No action is required. 
This change supersedes any fixes made to resolve a previously known issue for 15.3 (DE32956). This fix was also back-ported to
Third-Party Security Updates
Every release, we evaluate product security including vulnerabilities associated with third-party components. This release includes approximately ten (10) updated third-party libraries and components.
Upgrade Action
: No action is required. New installations and upgrades to this release include updates to address any security issues that are reported and confirmed.
: In the majority of cases, a vulnerability detected in a third-party component did not expose CA PPM to the vulnerability; however, to uphold a proactive security policy for our customers, we updated and tested the new components for this release.
Configure Subscription Compliance (Enable Telemetry) for PLA Customers
A foundational element of the CA Enterprise Software Portfolio License Agreement (PLA) model, Telemetry support is built-in to your Clarity PPM SaaS PLA subscription. Both on-premise and SaaS customers can configure Clarity PPM to collect and send required PLA telemetry information. Non-PLA customers can opt-out of this monthly product consumption tracking.
Integrated telemetry in Clarity PPM 15.6 sends product usage and system configuration data to CA Technologies, a Broadcom Company (CA). This data helps CA gain insight into our customers' product usage, their software needs, and the features and platforms that are most commonly used. Telemetry collects no personally identifiable information (PII). Configuration is contractually required for PLA customers.
Upgrade Action
: After upgrading, administrators can configure Telemetry settings for PLA subscription compliance in Classic PPM. See Configure General System Settings.
Clarity PPM 15.6 Changes: Jaspersoft 7.1 Advanced Reporting Features
Jaspersoft 7.1 Upgrade
Upgrade Action
: After upgrading to 15.5.1 or 15.6, SaaS customers automatically receive Jaspersoft 7.1. On-premise customers on Release 15.6 or higher are now required to upgrade and take advantage of the new features and enhancements in 7.1. You cannot remain on Jaspersoft 6.4.2 due to known security issues and upcoming vendor end-of-support. When upgrading, observe the following changes:
    : The same Ehcache.XML file used with 6.4.2 can be applied to 7.1 (required in clustered environments).
    Jaspersoft Studio Pro
    : Redo the connections with Jaspersoft Studio Pro and the optional CA JDBC Adapter for Advanced Reporting.
    Changes to the Login Page
    : The layout of the reportservice login page changed in JasperReports Server 7.1. The CSS classes did not change; however, some default values were modified. If you customized the login page, verify that your customizations behave correctly in 7.1, and make any necessary changes. If you have not customized the Login page, this change does not affect you.
    Pipe | Character
    : Jaspersoft examples in documentation no longer include the pipe character ( | ) because new versions of tomcat do not support it.
    Tomcat Version
    : Tomcat 8.5.30 is strongly recommended due to performance issues with 8.5.31.
Jaspersoft 7.1 Missing Attribute Removal
After upgrading to 15.6 and Jaspersoft 7.1, customers also automatically receive the following Missing Attribute Removal enhancement. 
Upgrade Action
: No action is required. When attributes are removed in CA PPM, downstream Jaspersoft views and reports prompt you with the option to remove the attributes.
To observe the new behavior, perform the following steps
  1. Log in to CA PPM and navigate to Classic PPM Studio.
  2. Create a custom attribute for a project.
  3. Run the Load Data Warehouse job to populate the changes for the new custom attribute in the data warehouse.
  4. In 
    Advanced Reporting
    , create an adhoc view with the new custom attribute and save the adhoc view as a report.
  5. After some time, a user might delete the custom attribute from a project. When the Load Data Warehouse job runs, the attribute no longer appears in the data warehouse.
  6. In previous releases of Jaspersoft including 6.4.2, users saw an error message when they attempted to open the ad hoc view or report with the missing attribute. The report developer would then have to remove the attribute.
  7. In Jaspersoft 7.1, a new 
    Missing Data
     window appears and shows the missing attributes.
  8. To remove the attributes from the ad hoc views and reports at the data source, click 
    Remove Items
New Trending Reports
Trend reporting helps you identify overall patterns that shift over time. New installations and customers upgrading from 15.5.0 and previous releases, can work with two new trending reports.
    Project KPI Trends
    : The Project KPI Trends report was introduced in Release 15.5.1 as an example of the applied use of trending snapshots. Use the Project KPI Trends report to monitor key performance indicators and establish priorities. For example, track the quantity and severity of open risks, issues, change requests, and to-do items over time.
    Trended Metrics by Project
    : New in 15.6, the Trended Metrics by Project report serves as a second example of trend reporting. This example compares key financial data for core investments by fiscal period (in this example, by month).
Upgrade Action
: No action is required. The new reports are available to support your optional configuration of Clarity PPM for organizations that want to use the native Trend Reporting features powered by the Clarity PPM data warehouse. See 
Data Warehouse Trend Reporting
 in the 
Advanced Reporting with Jaspersoft
Clarity PPM 15.6 Changes: Data Warehouse Enhancements
MSSQL Load Data Warehouse Job
Similar to Oracle, we added MERGE logic in MSSQL to improve performance while loading the following fact tables in the Data Warehouse:
New Data Warehouse Fields
The following fields (columns) in the data warehouse (DWH) were added in this release for investments, projects, financials, tasks, time entries, risks, issues, changes. Advanced Reporting domains have also been updated.
DWH Table
DWH Column
Advanced Reporting Domains
Application, Investment, Project, Financial
Application, Investment, Project, Financial
Application, Investment, Project, Financial
Application, Investment, Project, Financial
Application, Investment, Project, Financial
Application, Investment, Project, Financial
Application, Investment, Project, Financial
Financial, Project, Resource
Financial, Project, Resource
Financial, Project, Resource
Change Request
Change Request
Time Entry
pr_usertext1 through 7*
*On the Project object, these seven (7) default User Text fields were not enabled for the data warehouse in previous releases. In 15.6, these 7 fields were added to the data warehouse and also to the Project domain for availability in Advanced Reporting.  
Transaction-Level Department and Location OBS Data
In previous releases, the DWH_FIN_TRANSACTION table in the data warehouse included department and location OBS data at the project-level and resource-level. In this release, the department and location OBS data structure fields are also included at the actual transaction-level.
Upgrade Action
: No action is required. The data warehouse in Release 15.6 stores department and location OBS data at the project, resource, and financial transaction levels.
To explore the changes in greater detail, expand the link below.
To observe the new behavior, perform the following steps
  1. Under Administration/Wip Settings set the location and department to Project Location and Project Department (default values).
  2. Set up a resource and financially enable the resource with a different Location and Department from the project below
  3. Set up a project and financial plan with grouping attributes Location and Department
  4. Enter a WIP transaction using the project and resource and Post
  5. Run a Full DWH Load and check that the proper Location and Department populated in WIP, and the financial plan
    (SELECT investment_location, investment_department, resource_location, resource_department, location, department, location_key, department_key FROM dwh_fin_transaction)
    (SELECT * FROM dwh_x_plan_act_per_facts)
    (SELECT * FROM dwh_fin_plan_period_facts)
  6. Under Administration/Wip Settings set the location and department to Resource Location and Resource Department
  7. Enter a WIP transaction using the project and resource and Post
  8. Run an incremental DWH Load and check that the proper Location and Department populated in WIP.
  9. The new values also appear in advanced reporting ad hoc views.
Use the following screen captures to guide you (the numbers indicate sequence and do not necessarily align with the steps above):
Clarity PPM Data Warehouse Now Includes Custom Investment Types
You can now select which custom investment objects and attributes you want to include in the data warehouse. By default, objects and attributes are excluded from the data warehouse.
Custom Investment objects enabled for the data warehouse each have their own new dimension table.
Clarity PPM 15.6 Changes: Integrations with MSP, OWB, Schedule Connect, and XOG
Java 11
This release requires Java 11. See also the JDK Support Timeline image below (subject to change).
Upgrade Action
: After upgrading to 15.6, upgrade clients for XOG, OWB, and Schedule Connect. They now use native Java 11 code and no longer require a separate JRE. Unless you upgrade from 15.5.1, Java 11 is new.
: The new JDK still has many of the same familiar administrative tools. They are now in the 
 folder. To learn more, see
CA PPM 15.6 and Java 11
: Oracle Java 8 is shipped with prior releases of CA PPM. Java 11 is shipped with 15.5.1 and newer releases. Oracle has announced end-of-public-support for the version of Java used by CA PPM 15.5.0 and earlier. Java 8, which was provided with releases of CA PPM prior to 15.5.1, has been superseded by Java 11 in Clarity PPM 15.5.1 and 15.6.
Customers may continue to run Java 8 in production and non-production CA PPM 15.5.0 and earlier environments after the End-of-Service Date.
 However, after July 31, 2019, CA Technologies will no longer provide any fixes, patches, service packs, updates, upgrades, programmatic changes, new features, or coverage for updated or new operating systems, browsers, or any additional components for Java 8. CA Support may submit potential security and vulnerability issues to Oracle Support for possible remediation; however, customers will be required to get any remediation to such vulnerabilities directly from Oracle. Customers can continue to contact CA Support after July 31, 2019, for troubleshooting issues potentially related to Java 8 on an "as-is" basis if installed in conjunction with a still-supported CA product. If a workaround cannot be determined, the problem will be deemed "irresolvable." We encourage you to plan for migration to CA PPM 15.5.1 as soon as it becomes available, so you can take full advantage of the features and enhancements this release has to offer. For CA PPM 15.5.1 and higher, we include Java 11, the latest version of Java provided by Oracle. Please note that Java 11 does not work with and is not supported by CA PPM 15.5 or earlier releases.
No customer action is required to use Clarity PPM with Java 11
: Clarity PPM embeds Java under the terms of a commercial contract with Oracle. Because CA (a Broadcom Company) distributes this Java code to you as a customer of the Clarity PPM solution, you do not need your own separate contract for Clarity PPM Java compliance. However, as a customer developing your own software products, you might need your own commercial contract with Oracle or a Java provider. As a customer, you can continue to acquire a JDK from Oracle if you need for your own applications. Consult your team. Also note that, in the future, it is 
 that Clarity PPM might begin using OpenJDK.As a customer, you cannot use Clarity PPM releases, patches, or components for any other purpose than to update Clarity. For example, you cannot reverse engineer, copy, or otherwise apply Clarity deliverables to update your own internal use of Java. 
XOG: New 
 Attribute in Import Files for Projects and Investments
In previous releases, a XOG import (write) file, specifically for a project or non-project investment that included the optional 
 attribute and associated resources who were also being allocated to a team through the same XOG import file, would cycle through all the assignments in the investment. This behavior could result in performance issues, especially during attempts to import large numbers of resources (for example, more than 10,000).
  • When adding a resource to a team for an investment in the new or classic user interface, the application appends the ETC or actuals to the previously-generated slice curve.
  • When adding a resource through the XOG, the existing time-scaled value (TSV) curves are unknown and cannot be accessed; instead, the XOG import causes the application to regenerate all TSV curves for all assignments in the investment.
Clarity PPM 15.6 improves XOG performance by introducing a new 
 XOG attribute:
  • If set to 
    , the XOG import does not process the aggregated TSV values; instead, administrators would run the Investment Allocation job to update the aggregated totals.
  • If the attribute is set to 
     or excluded from the import file, the functionality remains the same as the previous release.
Upgrade Action
: No action is required; however, if you plan to import assets, applications, and other types of investments with a large number of resource assignments, follow these steps:
  1. Include the new 
     attribute and set it to 
     in your investment-level XOG file. 
  2. Example
  3. After the import, run the Investment Allocation job to update the aggregated totals.
OWB: Open Workbench Improvements
In this release of Clarity PPM 15.6, the following Open Workbench client application improvements are introduced:
    Cell Text Wrapping and Sizing
    : When reducing previously wrapped text on multiple lines to a shorter string, the cell size is also reduced as expected. A workaround in previous editions was to click another tab to trigger the cell to resize itself.
    Word Wrapping Increases the Row Size
    : In tasks with long names, word wrapping now splits the string into several lines and adjusts the height to show the full cell. In OWB clients from previous releases, the word wrapping split the string into several lines but the height was not adjusted. Because the size of the row did not dynamically expand the height, the text was hidden.
    Rows Do Not Overlap
    : Overlapping or cropped text rows no longer appear when your computer display is set to 
    . The following image shows an example of the problem as it appeared in a previous release:
Clarity PPM 15.6 Changes: Integrations with Rally (CA Agile Central)
Improved Handling of Milestones
In 15.5.1, if you removed 
 milestones from a portfolio item or user story in Rally (Milestone field becomes null) all your removed milestones were not removed in the corresponding project and tasks in Clarity.
In 15.5.1, if you removed 
 milestones from a portfolio item or user story in Rally (Milestone field is not null) the removed milestones were removed in the corresponding project and tasks in Clarity.
In 15.6, milestones in integrations are improved.
Upgrade Action
: No action is required. Users can expect the following behavior after an upgrade:
  • Deleted CA Agile Central (Rally) milestones are also deleted from the Clarity PPM Project Properties - Main - Agile Summary page.
  • In the previous release, a known issue retained the last agile milestone added in CA Agile Central (Rally) on the Clarity PPM (then branded CA PPM) Project Properties - Main - Agile Summary page.
To assist you with user acceptance testing (UAT) for your upgrade to Clarity PPM 15.6, we provide a general series of steps and detailed steps to illustrate and help you validate the new behavior:
General Steps:
  1. Create an integration of type 
    Portfolio Item
     between Clarity and Rally with a Rally-to-Clarity synchronization direction.
  2. Create a project in PPM. Run the sync job to create a matching initiative in Rally.
  3. Create a milestone and assign it to the initiative.
  4. Create a feature under the initiative. Create a new milestone and add it to the feature.
  5. Run the sync job and verify the milestone is added to the PPM project and task.
  6. Delete the initiative and feature milestone in Rally.
  7. Run the sync job.
    The milestone is now removed from the PPM project and task.
Detailed Steps:
  1. Create an Agile Central integration in CA PPM with a Rally-to-Clarity synchronization direction.
  2. Create a new project in Clarity PPM and navigate to the CA PPM Project: - Properties - Main - Agile Summary page.
  3. Enter the integration created in Step 1 within the “Agile System.”
  4. Select the 
     check box.
  5. Click 
  6. Click on the 
     menu at the top right.
  7. Select 
    Synchronize Agile Central
     to create the initiative in Rally.
  8. Navigate to the CA Agile Central (Rally) environment.
  9. Click on the Initiative ID to open the initiative.
  10. Add two milestones and click 
  11. Navigate back to CA PPM and navigate to the Agile Summary page.
  12. Click the 
     menu and select 
    Synchronize Agile Central
     to sync the initiative.
  13. Navigate to the CA Agile Central (Rally) environment.
  14. Click on the 
    Initiative ID
     to open the initiative.
  15. Remove all milestones currently added.
  16. Click 
  17. Navigate back to CA PPM and navigate to the 
    Agile Summary
  18. Click the 
     menu and select 
    Synchronize Agile Central
     to sync the initiative.
Clarity PPM 15.6 Changes: General Changes and Other Potential Impacts
IPv6 Network Compatibility Restrictions
The following section applies only to on-premise environments.
CA PPM 15.5 and higher releases are certified to operate in an IPv6 networking environment with restrictions. Other configurations of CA PPM using IPv6 are likely to work but have not been certified. For mixed environments with IPv6 and IPv4, the server instance uses two network interface cards, one configured for IPv6 and the other for IPv4. We performed our certification testing on an isolated private IPv6 environment that is not accessible to other networks.
During PPM installation in IPv6 environments, you are prompted for the correct multicast and bind address. The following entries provide examples:
IPv6 Mulitcast
: ff0e::75:75
Red Hat Enterprise Linux Configurations with Oracle
We support mixed mode IPv6 installations of CA PPM, mail server, and Jaspersoft in Red Hat Enterprise Linux (RHEL) configurations with Oracle.
    RHEL OS Version
    : 7u5
    App Server
    : Apache Tomcat 8.5.33 (64-bit)
    : Oracle Enterprise Edition
    JasperReports Server
    : 7.1
IPv6 Notes and Known Issues
  • CA PPM supports pure IPv6 and mixed mode. Jaspersoft only supports mixed mode IPv6.
  • We have tested PPM on a private network where the mail server is not accessible. This is expected to work; however, it was not a tested component.
  • Components that connect to an external network outside of the isolated IPv6 environment were not tested. These components include an integrated mail server and integration with CA Agile Central. Not tested does not mean it does not work.
  • Due to issue DE38980, the 
    New User Experience
     does not work as expected when an IPv6 address is used in the URL.
    Workaround: Use Host Name instead of IPv6 address.
  • Due to an unknown issue, the Jaspersoft URL provided in CA PPM System Administration (CSA) does not work with IPv6 addresses.
    Workaround: Use Host Name instead of IPv6 address.
  • Due to issue DE38981, a problem with DBLINK does not allow you to save a data warehouse link when IPv6 is configured, resulting in a Load Data Warehouse job failure.
    Workaround: Connect to DWH-Database. CREATE DATABASE LINK PPMDBLINK CONNECT TO <schema> IDENTIFIED BY <password> USING '<user>';
Upgrades from CA PPM 15.3 to 15.6 on RHEL
We do not recommend attempts to integrate any IPv6 components into earlier releases and then upgrade to 15.5 or higher. IPv6 was not supported in 15.3 and earlier releases. Upgrade to 15.4 or higher using IPv4 and then switch to IPv6 in your new environment. If your requirements mandate an attempt to force an upgrade from 15.3 to 15.4 or higher in an IPv6 environment, follow these steps:
  1. Verify your RHEL OS, app server, and database version numbers meet the requirements listed above.
  2. Start the upgrade. The following error is likely to appear:
    Error: Failed to initialize Context properties java.sql.SQLNonTransientConnectionException: [CA Clarity][Oracle JDBC Driver]
  3. To resolve the error, update all entries in the following files: 
    update config/properties.xml update bin/ (or admin.bat) update {install.dir}/.setup/scripts/db.macros.xml
Locate all instances of the following entry: 
<jvmarg value=""/>
Replace all instances of this entry from 
<jvmarg value=""/>
Oracle Database Changes
New Oracle 12c Multitenant Support and Encryption Options
Oracle 12c introduces multitenancy (MT), pluggable database (PDB) capabilities, and new encryption options.
Oracle Multitenant architectures for next-generation cloud databases deliver isolation, agility, and scale. A multitenant container database can hold many pluggable databases. An existing database can simply be adopted with no application changes required. Oracle Multitenant fully complements Oracle Real Application Clusters, Oracle Active Data Guard, and other options.
CA PPM officially supports Transparent Data Encryption (TDE) at the tablespace level. Limited support is available for JDBC traffic between the application and the database.
Upgrade Action: 
To implement an MT architecture, follow the steps in the Install CA PPM topic. A summary of the complete steps appears below as a convenience.
  1. As a database administrator, install and configure your Oracle MT enabled database. You can create a container in a test environment for CA PPM, create your PDB, directory, and permissions, and query your PDB and resolve any connection issues.
  2. Make the following change in CSA:
    1. Select the 
      Specify URL
       check box.
      JDBC URL
       field appears with default values that include an 
       assignment. For example:
    2. Change 
    3. Set the 
       parameter to the name of your PDB.
The following image shows a new configuration example:
Data Model Changes
To view a summary of the data model changes for this release including the data warehouse, see 
Schema Changes 
 in the English edition of the documentation.
Known Issues for Release 15.6
The following section lists the known issues at the time this release was delivered.
Series of Five (5) Related Known Issues When Grouping Data in Grids That Support New Group By Functionality
Rows With Null Dates Should Be Grouped Under None
Instead of appearing under a None group, rows with no date are grouped as if the date were today.
DE47882: Negative Sign Does Not Appear in Group By Column
Grouping by negative numbers doesn’t show the negative sign.
DE47883: Decimal Group By Column is Empty for Null Values
Grouping rows by a field with decimal values shows an empty text box for null values. Expanding the empty grouping results in an 
API invalidAttrValue
 error and an unresponsive page.
DE47963: Rows With Midnight Finish Dates At the End of a Month Are Grouped In the Next Month
When a date with a midnight date (such as the Finish Date on the new Ideas page) occurs at the end of the month, the Group By feature displays the record in the following month. For example, when grouped, a row with a Finish Date of Feb 28, 2019 appears under the collapsed March 2019 group.
DE47965: Drag-n-Drop column in Group By row doesn't return the field back to the same position after the Group By field is removed or replaced
Workaround: Add column to Group By row via the column menu
: Slow Performance When Submitting Large Cost Plans for Budget Approval
Due to architectural limitations, an expected performance lag might be observed with large cost plans during submission of budgets for approval.
: Custom Investment Attributes Enabled for the Data Warehouse Are Not Included in Jaspersoft Domains
Custom investment objects enabled for the data warehouse each have a new dimension table. However, the custom attributes for those custom investment objects enabled for the data warehouse are not automatically included in the Jaspersoft domains. To resolve this minor limitation with Jaspersoft ad hoc reporting, report developers and users can build custom Jaspersoft Studio reports or custom domains against the data warehouse.
DE37990: XOG or SOAP Integrations Invoking WSDL Queries
The following potential known issue applies only to customers upgrading from 15.3 or a previous release where certain conditions listed below are satisfied. Due to a bug fix in 15.4 (DE37990) inherited by newer releases (including 15.6) that restores correct behavior, your legacy external integration scripts that invoke WSDL queries from the XOG, SOAP, or other means could experience the following problems, requiring corrective action on your part after an upgrade from 15.3 or older releases (at the base level or any patch level) to 15.4 or higher, including 15.6.
To illustrate the problem, consider whether the following PPM integration scenario applies to you:
  • You maintain an integration tool that interfaces with CA PPM to read and write data.
  • You use NSQL queries to read data. You might import projects, tasks, incidents, or even configuration data such as lookup field values that are based on dynamic NSQL queries.
  • You use slicing (paging) to limit the response size and rely on the slice return value to indicate how many more pages exist.
  • You invoke a SOAP request for any NSQL query with multiple results. For example, you make a XOG read request using SOAP on a slice size that is smaller and lower than the total results. Or, you enter a slice size that does not divide the total results evenly (
    total results 
     slice size > 0
The last page retrieved in the result set (final slice) could have a slice size that no longer matches the requested size, but is instead, the returned number of items. In CA PPM 14.4, this was not the case. The slice size returned was always the requested one, even if fewer items were retrieved. CA PPM 15.4 and higher restores this functionality.
Upgrade Action
: If this scenario applies to your organization, advise your integration developers to examine their code for calculating when the next page exists. As a workaround, they might already be storing the requested page size. The size element in the response was corrected in 15.4 and newer releases to represent the 
returned records count
 instead of the 
requested size
In 15.4 and higher, the NSQL web service query limit can only be controlled up to the internal limit of 50,000 for the maximum results returned. You can still run a query that pulls more data than this by requesting it in chunks. For example, in 75,000 total possible results, you could get up to 50,000 on the first pull, and then the next pull would get the remaining 25,000.
: The bug fix for DE37990 resolved a serious issue where the MAX_FETCH_LIMIT governor could be overridden in WSDL query calls, producing incorrect slice totals and results. Bypassing that necessary governor limit also permitted a single user action to create a 
 condition to bring down the application service. Release 15.4 and higher releases include this bug fix.
Change in Status Report Status Lookup Values
The following subtle change applies only to customers upgrading from 14.3 or earlier releases (as previously announced, mainstream support for those releases has expired).
Starting with Release 14.4, the default 
Status Report Status
 lookup values changed from 
Minor Variance
Needs Help
 and from 
Significant Variance
At Risk
. The 
On Track
 value remained the same. See the PMO Accelerator Release Notes in the 14.4 edition of the English documentation set.
Internet Explorer 11 Not Supported for New User Experience Features
Classic PPM still supports IE 11; however, the 
New User Experience
 cannot extend backward compatibility with any old browser technology, including IE 11.
This is not a known issue with CA PPM. Instead, it is a known issue with IE 11. Microsoft has invested in a new browser, Microsoft Edge.
: If users ignore the support requirements and attempt to use IE 11 with the 
New User Experience
, the following problems could occur:
  • Defective features or memory leaks (with no scheduled fixes from Microsoft)
  • Missing browser framework support for new REST API capabilities
  • Poor appearance or slow performance with HTML 5 and new Angular components
  • Links to other sites stop working or show messages indicating you need to update your browser
For example, using IE 11, you could cause your roadmap timeline to stop working, the staffing pages might not load all resources, and other problems could occur that appear to be 
 until users realize they are using old unsupported browser technology to access a completely new drag-and-drop feature-rich web application interface. For best results when viewing the modern user experience pages in CA PPM, switch to a new browser such as Edge, Firefox, or Chrome.
Cannot Upgrade on Oracle Until Security License and MD5 Package Are Enabled
  1. Contact your database administrator or Oracle to obtain the advanced security license (OAS) required only if using DBMS_CRYPTO.
  2. Enable and grant explicit permissions to dbms_obfuscation_toolkit.md5 (also provided with your Oracle installation).
  3. Start the upgrade to 15.6.0.
FIPS Support Not Available in CA PPM 15.6
FIPS is not supported. 
Upgrade Action
: Disable FIPS in your current release before upgrading to CA PPM 15.6. If you require FIPS, delay your upgrade plans until a fix or workaround is available.
: After an upgrade, system administrators would typically not re-generate a new keystore and would continue to use their older keystore. Ideally, JDK 11 should be able to read older keystores generated by lower JDK, openjdk, or openssl versions. However, after an upgrade to 15.5.1 or higher, verification of the BCFIP.jar signature fails. Bouncy Castle (our encryption provider) does not support FIPS with JDK 11.
As an administrator, if you do not disable FIPS, you might receive the following error in the logs:
 java.util.jar.JarException:   file:/fs0/niku/1551runtime/lib/bc-fips.jar not signed by trusted signer
: Upgrading customers would need to reset any configuration changes they made to enable FIPS 140-2 mode of operation in previous releases before upgrading to 15.6. If you did not disable FIPS before the upgrade to 15.6, you will likely encounter an error. 
: JRE is no longer part of JDK 11. When a fix is found, you might need to copy the FIPS provider jar (bc-fips.jar) to 
 instead of 
. Remember to modify the security providers list in the properties file at 
 instead of its old Java 8 location at 
Known Issue with Synchronization of Custom Attribute Values Between a Custom Investment and a Roadmap
A known issue prevents you from attempting to sync a matching custom attribute defined on an abstract custom investment object inside a roadmap.
  • This problem occurs even though your matching attributes share the same API alias for their lookups, as required. 
  • Default system attributes such as 
     can be added to a roadmap item for a custom investment and share the same lookup API ID; however, the attribute values do not synchronize as expected.
  • The problem can be observed in a variety of settings with or without other adjustments to clipping and date settings. 
  • The entire sync fails; even other fields (like benefits) will not work.
Workaround 1
: Do not use the sync custom attributes feature until the issue can be resolved in a future patch, service pack, or release.
Workaround 2
: Remove or change the API Attribute ID for the roadmap item attribute so that it no longer matches the investment attribute. Ironically, this change restores the attribute sync.
Workaround 3
: Define the attributes directly on your custom investment, project, or idea.
A similar related known issue with synchronization corrupts any saved view that includes the affected field. Your roadmap grid might fail to appear. As a temporary fix, switch to a known good view and delete any affected views. Add the field back without attempting to synchronize it with the parent investment attribute.
Known Issue with Fresh Installations of Jaspersoft 7.1
In on-premise environments, you might observe the following 
Failed to execute: create index 
entry in the installation logs during a new installation of Jaspersoft 7.1.0 on Oracle 11g R2 or 12c:
[exec] [exec] init-js-db-pro:
[exec] [exec] [echo] For JDBC driver the artifactId and version properties are set:
[exec] [exec] [echo] maven.jdbc.artifactId=ojdbc8
[exec] [exec] [echo] maven.jdbc.version=
[exec] [exec] [echo] Specified JDBC driver jar exists
[exec] [exec] [advanced-sql] Executing resource: /fs0/clarity1/install_cd/ca_ppm_jaspersoft_7.1.0/buildomatic/install_resources/sql/oracle/js-pro-create.ddl
[exec] [exec] [advanced-sql] 0 rows affected
[exec] [exec] [advanced-sql] 
Failed to execute: create index
 idx46_jiresfldr_hidden_idx on JIResourceFolder(hidden)
[exec] [exec] [advanced-sql] java.sql.SQLException: ORA-01408: such column list already indexed
[exec] [exec] [advanced-sql] 0 rows affected
[exec] [exec] [advanced-sql] Executing resource: /fs0/clarity1/install_cd/ca_ppm_jaspersoft_7.1.0/buildomatic/install_resources/sql/oracle/quartz.ddl
: You can ignore this entry. The warning appears to be alerting you about a duplicate index creation scenario; however, it is not a valid warning.
  • This warning has no impact on your installation and does not affect any Jaspersoft 7.1 functionality. 
  • CA Engineering teams confirmed that all the DDL commands are successfully executed after the reported warning.
  • The warning only appears on new Oracle installations; it does not occur with supported versions of Microsoft SQL Server 
Installation and Upgrade Dependencies
The install and upgrade scripts in this release introduce the following dependencies in the listed chronological order:
Install/Upgrade of This Component:
Requires This Component:
Clarity PPM
  • Data Warehouse Configured
  • Load Data Warehouse Job Completed
New User Experience
  • PMO Accelerator Add-in Installed
Install PMO or APM add-ins
  • Data Warehouse Configured
Review Cancelled Jobs After Upgrade
Please review any Clarity PPM jobs that are in the Canceled state after your upgrade is complete. Please pay special attention to any canceled jobs that were previously recurring jobs. Sometimes, after an upgrade, job parameters change and the jobs move to a canceled state. If you don't proactively review canceled jobs, you will only notice them after you receive escalations from the business.
Supported Upgrade Paths for Release 15.6
To upgrade 
 to this release (15.6), your current release must be 14.4 or higher. The 15.6 installer can backup and upgrade your data from supported older releases. 
  • If you have Release 14.3 or older, your release is no longer supported. Upgrade to Release 15.2 or 15.3 first, and then upgrade to 15.6.
  • You cannot upgrade to Release 15.6 
     from Release 14.2 with Jaspersoft 5.6.1 or from Release 14.3 with Jaspersoft 6.1.0. The Jaspersoft 6.4.2 or 7.1 upgrade does not support those configurations. Your 
     upgrade is still supported. For example, upgrade to 14.3 and Jaspersoft 6.4.2 first. Then upgrade to 15.6 and upgrade to Jaspersoft 7.1.
  • You can upgrade from a previous release even if you have no Jaspersoft reports environment configured. The data warehouse is required; however, reporting is not required. You can elect to upgrade from 14.x and perform a fresh installation of your reports environment.
  • To upgrade from earlier 13.x releases, it often helps to upgrade to 14.3 or 14.4 first and skip the Advanced Reporting component. This approach simplifies the troubleshooting and restart process if an upgrade step fails. Then, from 14.x, you can upgrade to 15.6 and install Jaspersoft 7.1 for Advanced Reporting.
: The installer detects how many incremental upgrade steps are required to update your installation to the latest release. If two or more, you are prompted to decide if you would like the installer to save automated backups at each step. For example, from 15.3 to 15.4, from 15.4 to 15.5, from 15.5 to 15.5.1, and from 15.5.1 to 15.6.
If you have installed any patches on the base version, verify that you applied the latest supported cumulative patch before and after you upgrade. Patch maintenance before and after upgrades is important for troubleshooting, security fixes, and general system health.
Follow these steps
  1. Select your current release from the 
     menu at the top right of that docops page.
    For example, select 15.1 and verify you installed the patch or select 15.3 and verify that you installed the patch before starting your upgrade to 15.5.1. After the upgrade, install the latest 15.5.1 patch.
 You might experience issues if you attempt to upgrade directly from an unsupported patch level. For best results, follow a supported upgrade path. To learn more, contact CA Support or CA Services. You can also visit the CA PPM Community to collaborate with other community members about your specific questions.
CA PPM Upgrade Overview 
Follow these steps:
  1. Perform the pre-upgrade requirements.
    1. Install the prerequisite third-party software. For the supported operating environment information, see 
       in the Release Notes
    2. Create a full backup of your database, file systems, and customizations (if applicable). To keep sequences in line, take a 
    3. Remove customer-added database triggers, stored procedures, indexes, views, and constraints before upgrading.
       Most custom triggers, indexes, and constraints can cause the upgrade to fail. We recommend 
      , not disabling, customer-added triggers.
  2. Perform the remaining pre-upgrade steps and then start the upgrade as detailed in 
    Upgrade CA PPM
    . This documentation is available only in the English edition of the documentation set.
  3. Some important changes include:
    • The upgrade prompts you for current and target 
      Clarity PPM
       folders. You can specify the same folder or different folders. If you specify the same folder for both, the existing folder is renamed. The new release 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 
      Install CA PPM
      . This documentation is available only in the English edition of the documentation set.
    • The HTTP and HTTPS Entry URL fields completed for the server in 
      Clarity PPM
       System Administration (CSA) cannot be 
      when Jaspersoft is integrated with 
      Clarity PPM
      . When you use Jaspersoft, enter the complete URLs on the Application subtab of the Properties tab for the 
      Clarity PPM
  4. Complete the post-upgrade steps:
    1. Verify that all installation steps completed successfully by reviewing the post upgrade report that the installer generates.
    2. Review the 
      Clarity PPM
       System Administration server admin.log and install.log for errors.
    3. Reapply any database and file system customizations.
  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 
      Clarity PPM
    2. Install Jaspersoft and import the domain information for reporting.
  6. Install and upgrade your choice of add-ins and connectors.
    • Back up your 
      Clarity 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 
      Clarity PPM
       content, copy the modified content before upgrading. Then, apply the new incoming stock 
      Clarity PPM
       content, and retrofit the modifications to the new content.
  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 manage the views:
    • The Last Version column identifies changes to stock views in this release.
    • 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 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.4 and the Upgraded column= unchecked.
    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 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
    Typically, each release contains database schema changes. To ensure that your custom portlets work after the upgrade, correct any invalid NSQL queries.
    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, 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.
MS SQL Server Database Compatibility Level
If you are using SQL Server 2014 for this release, set the compatibility level to 120 from SQL Server Management Studio or use the following command:
EXEC SP_DBCMPTLEVEL <database>, 120
Oracle Database Only PRJ_BLB_SLICES Table
The ID, UNIT, LAST_UPDATED_DATE and LAST_UPDATED_BY columns in the PRJ_BLB_SLICES table were dropped around the time CA PPM 14.2 was released. If you are using Oracle with Clarity 13.x or 14.x, 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
: Before upgrading from a 13.x or 14.x release, you can determine if the tablespace can deal with this condition. As a database administrator (as sysdba) run the following query. Change the schema owner to the owner of the 
Clarity PPM
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:
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.
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.
Custom Processes, Scripts, and Other Customizations
CA PPM cannot upgrade any unsupported customized content. Customizations must be disabled and may need to be redesigned and re-implemented to work with changing product functionality.
After an upgrade, unless you disable them, your customizations might result in errors or fail to work as expected.
Follow these steps
  1. Identify your custom content. For example, you have one or more custom processes with custom GEL scripts that modified timesheet status attributes in a previous release.
  2. Acknowledge the customizations and recognize that the upgrade scripts might not support the custom content. Even if the custom content is upgraded, it may no longer work as expected. For example, your custom process references an object or attribute that has changed in the new release.
  3. As an on-premise administrator, the checkinstall script provides a warning for customizations that it detects pre-upgrade. You can see these warnings or the referenced logs for insight into the types of customizations that can negatively impact your upgrade experience. For example:
    WARNING: Possible schema customizations have been found. Any customizations to the system are the responsibility of the customer to maintain and are not supported. To upgrade, all customizations must be reviewed, changed, or removed as needed before the upgrade. After a successful upgrade, the customizations may be added back to the system. The possible customizations found are listed in the following log files:
    check‐logs/database_customization_triggers.txt check‐logs/database_customization_indexes.txt check‐logs/database_customization_tables.txt checklogs/database_customization_constraints.txt
  4. As an on-demand (SaaS) administrator, you do not see these warnings or the referenced logs. These example messages provide insight into the types of customizations that can negatively impact your upgrade experience.
  5. In on-premise or SaaS environments, turn off your customizations before the upgrade. After the upgrade, reintroduce the customizations and test them in the Classic PPM interface. Optionally, verify the impact of the customization behavior on the 
    New User Experience
  6. In addition to database objects, also evaluate attribute values. Review the Oracle and Microsoft SQL database and data warehouse changes (see the Reference section in the English documentation). Validate if any of your customizations depend on any dropped, changed, or new attributes.
: Some customers have experienced errors with legacy custom content. After disabling the custom process, script, or other legacy custom content, the 
New User Experience
 provided the functionality with no net loss to end users. We recommend that you perform an analysis comparing the value of CA PPM features in a complete COTS/SaaS solution against the value of developing your own unsupported customizations.