Clarity PPM 15.6.1 Change Impact and Upgrade

 
ccppmop1561
This 
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.1. 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.3 to 15.6.1. Review the changes in releases 15.4, 15.4.1, 15.5, 15.5.1, 15.6, and 15.6.1 before and after you upgrade. To switch to the 
Change Impact and Upgrade
 page for each release, click the 
Versions
 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.1, 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.
 
1
 
 
HID_HID_release_info_change_impact_od
 
HID_release_info_change_impact_op
 
Click here to expand a more detailed Table of Contents...
 
 
2
 
 
Clarity PPM 15.7 Onward - OracleJDK will be replaced with AdoptOpenJDK
Java Image
Clarity PPM will discontinue product updates related to Oracle Java, beginning 
August 19, 2019
. This will allow our development team to focus on adding value to future product releases.CA Technologies, a Broadcom Company (CA), continues to support its products and stand by the terms and conditions set forth in the license agreements between CA Technologies and its customers. 
Existing customers may continue to run and use releases that include Oracle Java components in production and non-production environments
. However, to address any future Java security and vulnerability issues that may arise, it may be necessary for customers to install a service pack or upgrade to a newer release of Clarity PPM that supports AdoptOpenJDK.This change does not impact Jaspersoft, which will continue to support Java 8. 
 
Clarity PPM 15.6.1 Changes: New User Experience Features
New Navigation to View Project Grid and Project Tiles
In this release, you can view projects in the following ways depending on your access rights:
  • Project Tiles: 
    Displays a quick visual overview of the projects that you must track frequently for an overall status and monitoring. The 
    Project Management - Tiles Navigate
     access right allows users to access the Project Tiles page in the New User Experience where projects appear as tiles. The page includes only the project tiles that the user has permission to access.
  • Projects: 
    Lists your projects and related details in a common grid layout. The 
    Project Management - Navigate 
    access right allows users to access the Projects page in the New User Experience where projects appear in a grid. The user sees only the projects that they have permission to access.
 
Upgrade Action
: As an administrator, review the access rights granted to project managers, team members, and other stakeholders. See 
Access Rights Reference
 and New User Experience: Manage Project Lifecycle.
Export Project Details in CSV File
The new Project grid provides you with the option to download the currently visible projects and their details to a CSV file. All the columns that are visible in the current grid are exported to the CSV file.
Upgrade Action: 
No action required. See 
Export Grid Data to a CSV File
 in Getting Started with the New User Experience.
Export to CSV Enhancements
In this release when your current view for a grid includes greater than 500 rows, a new background job completes your export to the CSV file. When you export 500 or fewer rows, your CSV export file is produced immediately. The Classic PPM user interface supports CSV file exports containing up to 25,000 rows and the 
New User Experience
 now supports CSV exports up to 250,000 rows.
Upgrade Action: 
No action required. See 
Export Grid Data to a CSV File
 in Getting Started with the New User Experience.
 
Manage OBS Attributes in Project, Staff, and Idea Grids
In this release, the 
New User Experience
 lets you work with Organizational Breakdown Structure (OBS) attributes in the Project, Staff, and Idea grids. You can also add the respective OBS column in the grid and can make inline edits to OBS values. You can associate, update, and dissociate a project with Department, Location, Organizational, and Default Resource OBS units. You can now associate Staff OBS with Staff from the common grid view.
Upgrade Action
: As an administrator, ensure that the respective object attribute is associated with the specific object in Classic PPM Studio. See 
Associate Projects with OBS Units
 in New User Experience: Create, Open, and View Projects
Associate Ideas with OBS Units
 in Capture, Develop and Approve New Ideas, and 
Add Staff OBS Column to Staff Grid
 in New User Experience: Staff a Project Team.
New Task Assignments for Projects
As a project manager or scrum master, you can now manage task assignments and monitor estimate-to-complete (ETC) values for your team members directly inside a project. Take advantage of new filters, saved views, and your choice of assignment attributes that appear as columns. Familiar grid features are also available including grouping, sorting, and exporting to CSV. 
When you group by assigned resource, task, or owner, the application aggregates time-scaled values such as ETC, EAC, and actuals for cost or effort. Exit group-by mode to edit TSV values. For example, you can edit task assignment per-period ETC values. You can also enter one total amount and have the application spread it evenly across multiple per-period segments.
Upgrade Action
: No action is required. The necessary changes happen automatically. To use these new features, review the following list:
  • The 
    New User Experience
     uses the existing business rules from Classic PPM for adding, editing and deleting assignments.
  • Select from a list of available resources, roles, or teams using the same project assignment pool setting used on the Project Task page. (On the Task Details panel, often called the flyout, click Staff.)
  • Search by resource name, ID, or primary role.
  • You can view Effort data in units of hours or FTE.
  • The application auto-grants rights when you assign a resource. Review the access rights for each staff member after you add them in the New UX or replace them in an assignment using Classic PPM.
  • To add the new Assignments page to your projects, configure the blueprint with the new Assignments module. The first four (4) modules appear as icons at the bottom of each project tile. See the following examples:
 
image2019-4-24_13-54-19.png
 
Custom Investment Types
New installations and upgrades from 15.4.1 and previous releases experience custom investment types as a new feature. Customers who upgrade from 15.5, 15.5.1, or 15.6 might already have existing custom investment type objects. 
Upgrade Action
: No action is required. The necessary changes happen automatically. As an administrator, review access right assignments for your users after the upgrade. As a custom investment business user, contact your administrator to confirm your access rights are up-to-date.
The Clarity PPM Brand is Back
With the acquisition of CA Technologies by Broadcom, the 
Clarity PPM
 product name, formerly rebranded as 
CA PPM
, has been restored in 15.5.1.1 and higher. The product is now branded Clarity Project and Portfolio Management or simply, 
Clarity PPM
Upgrade Action
: No action is required.
  • Users upgrading from 15.5.1.0 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
     branding.
Historic references with mixed branding might continue to appear throughout the application, in client applications, and in the online documentation, community content, Support KB articles, videos, and other content.
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
.
New Links Tab on the Task Details Panel
You can now create external links for tasks on the Project TASKS page.
Upgrade Action
: No action is required.
Copy Task Links from Templates (Classic PPM and New UX)
In this release, any links you had in Classic PPM tasks inside project templates are copied when and where appropriate. 
Upgrade Action
: No action is required.
  • When you create a project from a template in Classic PPM or the 
    New User Experience
    , the application copies associated tasks including their links.
  • When you select 
    Copy Task from Template
     on the Classic PPM Tasks page or the Classic PPM Gantt chart, the application copies any links in those template tasks.
  • This functionality includes all task types (standard, key tasks, milestones, and fixed duration).
  • This functionality includes tasks copied from templates in Classic PPM processes or through the XML Open Gateway (XOG).
Improved Grouping By Dates
In this release, the grouping of rows of grid data by a Date attribute is improved. In the previous release, the default grouped date format was month, day, and year (for example, Apr 17, 2021). In addition, instead of grouping themselves into a 
None
 group, rows with no date value appeared to be grouped as if their date value were set to today's date (for the current user session).
 
Upgrade Action
: No action is required. After an upgrade, users can group by a Date field and the default date format will show YYYY-MM (for example, 2021-04, 2021-05, 2021-06). This standard format improves the appearance of grouped and sorted rows spanning multiple months and years. Date fields with no value appear under the 
None
 grouping.
 
 
The label for the 
None
 group is not translated if you switch your application language settings. The 
None
 group always appears at the bottom of the sort order.
Project Task List, Board, and Grid Enhancements
The TASKS page no longer includes the list, grid, and board layouts all on one page. The layouts are now divided as follows:
  •  
    TASK LIST
    : This new blueprint module and page contains the traditional WBS-inspired task list with phases, milestones, and tasks.
  •  
    TASKS
    : This blueprint module and page contains the Kanban-inspired task board with columns and cards as well as the improved task grid layout.
 
image2019-5-24_15-8-31.png
 
 
Upgrade Action
: No action is required. After the upgrade, observe the following default behavior and options:
  • By default, all projects include the TASKS page with the grid and board. (Technically, all projects associated with templates that subscribe to the Standard Project blueprint inherit the new TASKS page since the Standard Project blueprint always included the task module.)
  • The Standard Project blueprint does not include the new TASK LIST page. 
  • As an administrator, configure your project blueprints to include the TASKS module, the TASK LIST module, or both modules.
  • The set of columns that you had in place on the project task board in a previous release is preserved. After the upgrade, your arrangement is converted to a local picklist named 
    Converted Columns
  • New installations or upgrades from environments where you left the standard default set of columns now use the Status attribute for the default COLUMNS setting on the board layout.
  • If the Converted Columns picklist does not appear after upgrade for a specific project, it indicates the project never used the old task board with its single set of columns.
  • After an upgrade, any colors that were set on the cards in the previous release columns are not carried forward. You can define a color for each column in the new 
    Converted Columns
     picklist.
  • By default, task cards on a board show the same fields as your old task board.
  • By default, the task board view uses the Status attribute values for columns; however, the color values default to blank (white on white).
  • Task boards and grids now honor the money and number decimal display values set in your current saved or unsaved view.
  • Only the new TASK LIST module supports the options for opening tasks in a Gantt view or optional integrated scheduler (OWB or MSP) directly from the page.
  • The new task grid includes new view options for per-period metrics.
  • In previous releases, the project task board supported just one set of columns. In this release, you can configure named picklists to divide tasks into columns.
TSVs in Grids
In this release, you can adjust the start and end periods for the columnar display of time-scaled values (TSVs) known as 
per-period metrics 
in grids. All per-period metrics use the system default entity fiscal period definitions. These per-period metrics are available on the project STAFF and ASSIGNMENTS pages (and blueprint modules of the same name). You can select a range of periods in the view options and save various configurations for use across all projects.
For example, you can display data for twelve monthly periods. When you switch to quarters, the application adjusts the grid to show four quarters. The application shifts to the closest matching start or end time period. 
 
image2019-4-12_18-40-22.png
 
 
Upgrade Action
: No action is required. This behavior occurs by default.
 Two or more attributes could have the same name or label in the user interface but represent different data types. For example, in Release 15.6.1 the Assignment object shows 
Actual Cost
 as a 
Money
 data type and 
Actual Cost
 as a 
time-varying
 attribute for the actual cost curve data that appears in per-period metrics. Other examples include 
Actuals
ETC
, and 
ETC Cost
.
Inline Edits in Group By Mode
In this release, you can expand one group at a time and can make inline edits in grid rows or in the Details panel.
Upgrade Action
: No action is required.
Subtle User Interface Enhancements
Imperceptible to most users, subtle user interface enhancements are included in this release. The light gray background of the action bar above grids has been changed to white. Board layouts no longer appear with nested borders, bevels, or  shadows around columns (swim lanes). This release also introduces more consistent treatments for visual elements and icons. 
Several popular examples are included in the following table:
Previous Release
This Release (15.6.1)
 
image2019-5-29_15-27-39.png
 
 
image2019-5-29_15-27-58.png
 
 
image2019-5-29_15-28-44.png
 
 
image2019-5-29_15-29-25.png
 
image2019-5-29_15-28-53.png
 
 
image2019-5-29_15-29-58.png
 
 
image2019-5-29_15-30-28.png
 
 
image2019-5-29_15-32-12.png
 
 
image2019-5-29_15-32-32.png
 
Upgrade Action
: No action is required. Users might need to update their notes, job aids, or training materials for new or changed icons in this release.
Expanded Availability of Attributes for Projects, Ideas, and Custom Investments
This release provides an expanded selection of data attributes for financial managers and business users with appropriate access rights. As an administrator, you can configure these attributes in one or more blueprints that, in turn, define their availability in grids and set their appearance on the Details panel (also known as the 
flyout
) in projects, ideas, and custom investment types.
Upgrade Action
: No action is required. All API-enabled attributes for projects, ideas, and custom investments are available in the following possible scenarios:
  • administrators can configure these attributes on blueprints
  • users can show or hide the available attributes in grids (through the Column panel)
  • users can filter, group, sort, or export data with these attribute values 
 
The following financial and related non-financial attributes are now available
Actuals Sum for Labor Resources
Alignment
Approver
Budgeted Benefit
Budgeted Benefit Finish
Budgeted Benefit Start
Budgeted Breakeven
Budgeted Capital %
Budgeted Capital Cost
Budgeted Cost
Budgeted Cost Finish
Budgeted Cost Start
Budgeted IRR
Budgeted MIRR
Budgeted NPV
Budgeted Operating %
Budgeted Operating Cost
Budgeted Payback Period
Budgeted ROI
Budget equals Planned Values
Calculate Financial Metrics
Cost Type
Department
Default Resource OBS Unit
Fast Track
Financial Status
Goal
Initial Investment
Is system value for Reinvestment Rate
Is system value for Total cost of Capital
Investment Class
Location
Objective
Override Value for Reinvestment Rate
Override Value for Total cost of Capital
Planned Benefit
Planned Benefit Finish
Planned Benefit Start
Planned Breakeven
Planned Capital %
Planned Capital Cost
Planned Cost
Planned Cost Finish
Planned Cost Start
Planned IRR
Planned MIRR
Planned NPV
Planned Operating %
Planned Operating Cost
Planned Payback Period
Planned ROI
Purge Flag
Required
Set Planned Cost Dates
SLA
Sponsor
Status Comment
Status Indicator
System Value for Reinvestment Rate
System Value for Total Cost of Capital
WIP Class
The names of the following financial attributes have also been updated in this release:
 
 
Original Attribute Name
 
 
New Attribute Name in 15.6.1
 
Equipment Transaction Cost Source
Equipment Cost Matrix
Equipment Transaction Rate Source
Equipment Rate Matrix
Exchange Rate Type - Equipment
Equipment Exchange Rate Type
Exchange Rate Type - Expense
Expense Exchange Rate Type
Exchange Rate Type - Labor
Labor Exchange Rate Type
Exchange Rate Type - Material
Material Exchange Rate Type
Expense Transaction Cost Source
Expense Cost Matrix
Expense Transaction Rate Source
Expense Rate Matrix
Labor Transaction Cost Source
Labor Cost Matrix
Labor Transaction Rate Source
Labor Rate Matrix
Material Transaction Cost Source
Material Cost Matrix
Material Transaction Rate Source
Material Rate Matrix
The names of the following resource allocation attributes for tasks, teams, and assignments have also been updated in this release:
 
 
Original Attribute Name
 
 
New Attribute Name in 15.6.1
 
Available Finish
Finish
Available Start
Start
Open
Open for Time Entry
Clarity PPM 15.6.1 Changes: Classic and New UX Languages
Change in Supported Languages
Classic PPM, the 
New User Experience
, and reports no longer support the following languages:
  • Catalan
  • Chinese-Simplified
  • Chinese-Traditional
  • Czech
  • Danish
  • Dutch
  • Finnish
  • Hungarian
  • Korean
  • Norwegian
  • Polish
  • Russian
  • Swedish
  • Turkish
Upgrade Action
: Advise users to select one of the following supported languages after their upgrade to 15.6.1:
  • English
  • German
  • Spanish
  • French
  • Italian
  • Japanese
  • Brazilian Portuguese
To change your personal language settings, see Personalize CA PPM: Change Password, Account Settings, Notifications. 
Clarity PPM 15.6.1 Changes: Classic PPM Administrative Features
Governor Limit Configuration Changes
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 the majority of users.
In this release, governor limits are now managed in the database.
 
Upgrade Action
: After an upgrade, all of the following changes take place:
  • Your previous 
    governor.properties
     file is deleted. As an on-prem administrator, you might have edited this file. As a SaaS customer admin, you might have requested changes through CA Support.
  • Any changes you made, even if you stretched a limit beyond its recommended maximum, are preserved in the new settings. However, your settings might now be flagged as violations.
  • Any custom scripts that managed governor limits are removed.
  • Any missing entries are replaced by new system default settings.
  • As an administrator of a previous release, you could disable (not recommended) a governor entry using a -999 value in the governors.properties file. Any disabled governor in your properties file is carried forward as disabled in the new release. However, a disabled or inactive governor is treated as a violation because it is not able to do its job to optimize performance by restricting users.
  • Your governor limits are now available through the database. As an on-prem administrator, you can use admin commands to manage the limits. As a SaaS customer admin, we recommend that you do not change these default settings. 
  • The new admin commands report back the current status of the governor in the system. These commands allow you to enable or disable a governor, and change certain values. You can also reset a governor to its system default recommended values, or reset all governors.
  • Admin commands are not available for changing certain critical limits and are designed to enforce a max restriction on the number of limits you can override.
Multi-Currency Configuration Changes
In previous releases, your single or multi-currency configuration was preserved after an upgrade, and in 15.6.1, that is still true. However, the way you configure multi-currency has changed.
  • After you install 
    Clarity PPM
     or upgrade a single currency setup, you have the ability to switch to a multi-currency setup.
  • As has always been the case, a multi-currency setup cannot be changed back to a single-currency setup.
 
Upgrade Action 1
: As an on-premise administrator or SaaS operator, refer to the following table to familiarize yourself with these changes.
Previous Releases:
Changes Made in 15.6.1:
You could enable multi-currency in CSA.
For on-premise administrators, the 
Multi-Currency Enabled
 check box has been removed from CSA.
You could run the following commands and restart application services:
cd $CLARITY_HOME/database/sql/ dbpatch -install -file SET_MULTICURRENCY.xml -apply
 
isMulticurrencyEnabled
 has been removed from 
properties.xml
 
In the past, an on-prem admin or a SaaS operator verified your multi-currency settings were preserved after an upgrade.
In 15.6.1, on-premise and SaaS administrators can enable multi-currency as a self-service option the same way. As an application administrator (or any user with sufficient rights), you can adjust this one-time setting yourself.
Before your upgrade, if you enabled multi-currency, you might have many transactions in different currencies.
After an upgrade, no changes are made to your transactions. The same transactions appear after your upgrade.
The following image shows the removal of the 
Multi-Currency Enabled
 check box in Clarity PPM System Administration (CSA):
 
image2019-4-12_10-30-52.png
 
 
Upgrade Action 2: To configure your Clarity PPM environment to use multi-currency, follow these steps:
 
  • If multi-currency was already in use before your upgrade, it is still used after your upgrade. No action is required.
  • If multi-currency was not used in your previous release and you upgrade (or you perform a new installation), the option to set multi-currency is now available inside the application.
Verify that your organization wants to enable multi-currency before selecting this option; once you enable it and click 
Save
, you cannot revert to single-currency.
  1. Log in to Classic PPM.
  2. Click 
    Administration
    Finance
    Processing
    :
    1. Select 
      Use Multi-Currency
      .
    2. If the 
      Use Multi-Currency
       checkbox is disabled and unchecked, contact your administrator. 
    3. If the 
      Use Multi-Currency
       checkbox is disabled and checked, it means you upgraded from a multi-currency system or another administrator already selected this option. Once enabled, the option cannot be undone.
  3. Click 
    Save
    . Your Financial Setup now includes links for Currency Codes and Foreign Exchange Rates.
The following image shows the new available setting with an on-screen text tip to guide you:
 
image2019-4-12_10-36-47.png
 
The following image shows the disabled (grayed-out) read-only check box after you have decided to use multi-currency:
 
image2019-4-12_10-37-40.png
 
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 anyway.
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.1 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.
REST API Attribute ID Naming Rule
The Synchronize Matching Custom Attributes feature introduced the ability to synchronize custom attribute values between your investments and roadmap items. To minimize potential conflicts between your attributes and system attributes, a new naming rule supplements the existing uniqueness constraint for the ID. In this release, the API Attribute ID for your custom attributes must begin with a lower case letter and underscore (x_). For example: 
z_category
 
Clarity PPM applies this new naming rule only when you use Studio or the XML Open Gateway (XOG) to attempt to enter a new API Attribute ID or change an existing one. 
Upgrade Action
: No action is required. Any IDs from a previous release are upgraded as is. After upgrading, administrators can continue using those IDs or update them to the new naming standard. Observe the following post-upgrade behavior:
  • Any custom seeded attributes in the PMO or Agile add-ins are created in Roadmap Item objects and use the new naming convention.
  • To enforce this new naming rule, the Classic PPM Studio application displays an error message to remind you to enter a compliant unique ID.
    image2019-5-23_14-25-8.png
     
REST API Keys
Upgrade Action
: This BETA feature is not supported in production environments. You might experience impacts if you were an authorized beta customer or partner using REST API keys in 15.6 test environments and now want to upgrade to 15.6.1 test environments. You can also use the information below to help you prepare for 15.6.1 data migrations to other environments (test to staging) or to prepare for the 15.7 upgrade.
  • System backups and restores from a source system to a target system retain the API Key access that you had on the source system. If you want to reset the target system, delete all of the API keys on the target system and change the salt key on the target system. 
  • For debugging, make a copy of the production system and use it in dev or test to profile an issue. After an upgrade or migration, we recommend that you change the salt key since you don't want data from production accidentally going into dev or test and vice-versa.
  • The system supports specifying your own additional salt as a system property per environment.
  • Each new installed or upgraded instance of Clarity PPM contains a new salt key.
Clarity PPM 15.6.1 Changes: Jaspersoft 7.1 Advanced Reporting Features
Jaspersoft 7.1 Upgrade
Upgrade Action
: After upgrading to 15.5.1 or 15.6.1, 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:
  • Ehcache
    : 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
    .
 
image2018-12-7_10-4-42.png
 
Missing Time Report Improvements
In previous releases, Time Period parameters did not repeat the Current Period, Previous Period, and Next Period in the chronological list of dates. These time periods only appeared at the top of the list. A user would observe a gap in the chronological list since these periods already appeared at the top.
In this release, the time periods also appear in the chronological list allowing users to select them either at the top or in the context of all available periods in the full chronological list. This release also removes the pre-defined WHERE clause that prevented the time periods from appearing in the chronological list. 
Upgrade Action
: No action is required. The Missing Time report now shows the time periods in both places. This report is accessible under Advanced Reporting or Reports and Jobs.
 
report_fix.png
 
Jaspersoft Administration: Added Support for ActiveMQ
Previous releases did not support clustered deployments. Starting with 15.6.1, Clarity PPM supports ActiveMQ for master-slave cluster configuration to provide high availability (HA) and fail-over. Jaspersoft Ehcache now works with a fail-over protocol.
  • You can configure Active MQ with one master and multiple slave PODs. Your ActiveMQ cluster must be deployed as part of your PPM Jaspersoft deployment only and in the same namespace (OSE project).
  • ActiveMQ should be sized properly based on the Jaspersoft cache replication volume.
Upgrade Action
: For your hybrid cloud migration journey, CA (a Broadcom company) provides CA PPM SaaS and other CA cloud solutions. We also recognize that some customers might deploy and manage a customized AWS or Microsoft Azure configuration. As a CA PPM administrator, you can take the following high-level steps:
  1. After you upgrade, switch to JDBC ping. Multiple PPM app services can communicate with each other using JDBC ping.
  2. Single-server Jaspersoft environments can communicate with the PPM database server using a direct JDBC connection.
  3. You can also configure replicated caching for JasperReports server with JMS.
On Azure, AWS, Google Cloud, and other public clouds where multicast is disabled and JDBC ping is enabled, support for clustered Jaspersoft configuration was previously not supported. Limited support is now available for using Java Message Service (JMS) for Jaspersoft server ehcache replication.
JMS is a mechanism for interacting with message queues. Open source options for Linux and Windows include Apache ActiveMQ and Oracle Open MQ. With JasperReports 6.1.0 or higher, Ehcache replication over JMS is now available and supported. (In our tests and in this documentation, we used ActiveMQ 5.12.1.)
With the Ehcache JMS replication module, your organization can leverage your message queue investment for caching.
  • Each cache node subscribes to a predefined topic, configured as the <topicBindingName> in 
    ehcache.xml
    .
  • Each replicated cache publishes cache Elements to that topic. Replication is configured per cache in accordance with the Ehcache standard replication mechanism.
  • Data is pushed directly to cache nodes from external topic publishers in any language. After the data is sent to the replication topic, it is automatically picked up by the cache subscribers.
Clarity PPM 15.6.1 Changes: Data Warehouse Enhancements
Improved Capture of Load Data Warehouse Audit Table History
When troubleshooting periodic delays associated with the extract, transform, and load (ETL) jobs that populate your Clarity data in the data warehouse (collectively referred to as the Load Data Warehouse job), the following improvements are now available:
  • Stored procedures and views associated with the new captured audit data
  • Audit and error data is written to the following tables:
    • dwh_cmn_error_message
    • dwh_config_audit
    • dwh_config_settings
  • Historic table data is written to the following tables:
    • DWH_CFG_SETTINGS_HISTORY: The history table for dwh_cfg_settings for the last 30 days. Stores settings and summary configuration details like timeslice rollover for each Data Warehouse run job.
    • DWH_CFG_AUDIT_HISTORY: The history table for dwh_cfg_audit for the last 30 days. Includes load start/end time and  row counts for each table loaded  in the Data Warehouse
    • DWH_CMN_ERROR_MSG_HISTORY: The history table for dwh_cmn_error_message for the last 30 days. Stores Data Warehouse load job failure details such as error message, error number,  SQL command,  and table name
    • DWH_CFG_SETTINGS_HISTORY_SEQ: The table created to track the next sequential number in MS-SQL only.
    • DWH_CFG_SETTINGS_HISTORY_S1: The table for the sequence in Oracle configurations.
  • Table data older than 30 days is purged
 
Upgrade Action
: No action is required. When you run the Load Data Warehouse job in full or incremental mode, the new history tables are populated with the data from the previous job. Data accumulates in the history tables for 30 days until it is purged. The new historic tables are not included in the dwh_cfg_audit table data used in the Load Data Warehouse Audit Dashboard introduced in 15.6. Approximately eleven (11) security tables and views are also excluded. Note that your error message table may be empty for multiple runs and could often show no captured error data.
Resource Skills, Interest Levels, and Proficiency Levels Added to Data Warehouse
In this release, the following resource skills hierarchy data tables in the Classic Clarity PPM database are also available for loading, refreshing, and reporting in the data warehouse:
  •  
    DWH_LKP_RES_SKILL
    : Resource Skills lookup table
  •  
    DWH_RES_SKILL_MAPPING
    : Resource Skills mapping table (maps resources to their skills)
  •  
    DWH_RES_SKILL_MAPPING_LN
    : Resource Skills mapping language table
  •  
    DWH_LKP_PROFICIENCY_LEVEL
    : Proficiency Level lookup table
  •  
    DWH_LKP_INTEREST_LEVEL
    : Interest Level lookup table
 
Upgrade Action
: No action is required. 
Financially Active Resource Attribute Added to Data Warehouse
In this release, the 
Financially Active
 stock system attribute for all resources is available in the data warehouse (in the DWH_RES_RESOURCE table). Full or incremental instances of the Load Data Warehouse job now update the current value of this setting for all resources. 
 
Upgrade Action
: No action is required.
 
image2019-4-12_16-44-13.png
 
Clarity PPM 15.6.1 Changes: New PMO Status Reporting Attribute
The PMO Accelerator add-in commonly installed with Clarity PPM includes a new attribute inside Tasks, Risks, Issues, and Change Requests. 
 
Attribute Name
Include in Status Reporting
 
Attribute ID
odmd_rpting
 
Data Warehouse Column
odmd_rpting
 
API Attribute ID
isIncludedInStatusReporting
 
 
image2019-3-29_18-7-8.png
 
Users can select the new 
Include in Status Reporting
 check box to mark the task, risk, change, or issue. Reports and portlets can then capture the marked items for appropriate attention and team status discussions.
 
image2019-3-29_18-10-43.png
 
Upgrade Action
: To install the new task, change request, issue, and risk views with the new attribute, select the following upgrade-ready views in your post-upgrade PMO Accelerator content add-in:
  • Task Object Property Views
  • Risk Object Property Views
  • Change Object Property Views
  • Issue Object Property Views
Clarity PPM 15.6.1 Changes: Integrations with MSP, OWB, Schedule Connect, and XOG
Microsoft Project (MSP)
This release no longer supports MSP 2013, 2013 SP1, or the legacy MSP driver. Although we do support click-to-run editions of 2016 or 2019, this support does not include MSP Online. 
Upgrade Action
: See the Release Notes for details.
Java 11
This release requires Java 11. See also the JDK Support Timeline image below (subject to change).
 
image2018-11-19_17-37-54.png
 
Upgrade Action
: After upgrading to 15.6.1, upgrade clients for XOG, OWB, and Schedule Connect. They now use native Java 11 code and no longer require a separate JRE. Unless you are upgrading 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 
$JAVA_HOME/bin
 folder. To learn more, see https://docs.oracle.com/en/java/javase/11/tools/.
 
CA PPM 15.6.1 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, 15.6, and 15.6.1
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 your upgrade to the latest release of Clarity PPM as soon as it becomes available, so you can take full advantage of the newest features and enhancements. Clarity PPM 15.5.1 and higher includes Java 11, the latest version of Java provided by Oracle. : Java 11 does not work with and is not supported by CA PPM 15.5 or earlier releases.
Continue to Use Java 8 for JasperReports 7.1
: Your advanced reporting environment still uses Java 8.
Clarity PPM 15.6.1 Changes: Integrations with 
CA Agile Central
 
New Agile Add-in Attributes for Roadmap Items
The following changes do not occur in Rally; however, they do represent changes in the available agile add-in for Clarity-Rally integration. The following new attributes are now available for Roadmap Items and support synchronization with agile project attributes:
  • Accepted User Stories
  • Accepted Story Points
  • Agile Investment Category
  • Agile Planned Finish
  • Agile Planned Start
  • Agile Release
  • Agile Risk Score
  • Agile State
  • Agile Value Score
  • Estimated Story Points
  • Estimated User Stories
  • WSJF Score
Clarity PPM 15.6.1 Changes: Additional Changes and 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
 
bindAddress
=fe80::cb8b:3483:cddd:bca3
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)
  •  
    Database
    : Oracle Enterprise Edition 12.2.0.1.0
  •  
    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.1 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/admin.sh (or admin.bat) update {install.dir}/.setup/scripts/db.macros.xml
Locate all instances of the following entry: 
<jvmarg value="-Djava.net.preferIPv4Stack=true"/>
Replace all instances of this entry from 
true
 to 
false
:
<jvmarg value="-Djava.net.preferIPv4Stack=false"/>
Oracle Database Changes
New Oracle 12c Multi-tenant Support and Encryption Options
Oracle 12c introduces multi-tenancy (MT), pluggable database (PDB) capabilities, and new encryption options.
Oracle Multi-tenant architectures for next-generation cloud databases deliver isolation, agility, and scale. A multi-tenant container database can hold many pluggable databases. An existing database can simply be adopted with no application changes required. Oracle Multi-tenant 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.
      The 
      JDBC URL
       field appears with default values that include an 
      SID
       assignment. For example:
       jdbc:clarity:oracle://my_ppm_server:1818;
      SID=niku;
       BatchPerformanceWorkaround=true;
       InsensitiveResultSetBufferSize=0;
       ServerType=dedicated;
       supportLinks=true 
       
    2. Change 
      SID
       to 
      ServiceName
      .
    3. Set the 
      ServiceName
       parameter to the name of your PDB.
The following image shows a new configuration example:
 
image2018-10-15_10-40-58.png
 
Clarity PPM Documentation Changes
In June 2019, documentation previously available at docops.ca.com migrated to techdocs.broadcom.com. 
This change impacts not only 15.6.1, but also all previous releases of CA Clarity PPM 13.x, 14.x, and 15.x.
Upgrade Action
: Review the following impacts.
  1.  
    Pre-Upgrade
    : Before starting an upgrade, review the documentation for Clarity PPM now available at https://techdocs.broadcom.com.
  2.  
    During the Upgrade
    : For the latest documentation updates, tips, options, and troubleshooting information, visit the new support, community, and documentation sites available at broadcom.com.
  3. Post-Upgrade
    : After the upgrade, be sure to advise your business users about this change. Update your bookmarks and any links stored in other applications. Although links might redirect, do not rely on that behavior alone because eventually redirected links will expire.
  4. Online Help
    : When users click Help inside the Clarity PPM application (New UX and Classic PPM pages), the application opens the best matching online help page and attempts to redirect you to techdocs.broadcom.com.
Data Model Changes
To view a summary of the data model changes for this release including the data warehouse, see 
Schema Changes 
under
 Reference
 in the English edition of the documentation.
Known Issues for Release 15.6.1
The following section lists the known issues at the time this release was delivered.
 
 
4
 
4
 
 
DE49226: Project STAFF Page and ASSIGNMENT Page Hard Allocation Per-Period Metrics Do Not Display any Columns
A known issue does not allow you to use the Hard Allocations per-period metric in view options on the project STAFF or ASSIGNMENTS page grids.
Steps to Reproduce:
  1. Log in to the New User Experience.
  2. Open a project and click the 
    STAFF
     page or the 
    ASSIGNMENTS
     page.
  3. Click 
    View Options
     and select 
    Hard Allocations
    Period Type
    Start Period
    , and 
    End Period
    .
Expected Results: Columns appear for the per-period metrics for hard allocations.
Actual Results: Per-period columns for hard allocations do not appear.
DE49382: New UX: Cannot Preview or Print PDF Status Reports
Without the required fonts, some systems, especially Clarity application servers running Linux, might display the following error when users try to generate a status report in the New User Experience:
 
image2019-6-14_16-0-15.png
 
Administrators and Support staff might see the following errors in the logs:
 
ERROR 2019-05-10 12:07:43,280 [https-abcd-nr2-8443-exec-32] ppm.rest   (clarity:PH5:1245__2CF509-3811-47F4-9412-CEEC:PPM_REST_API) 
Exception processing request for resource [statusReportPublisher],   query string [/private/statusReportPublisher] 
java.lang.InternalError: java.lang.reflect.InvocationTargetException 
at java.desktop/sun.font.FontManagerFactory$1.run(FontManagerFactory.java:86) 
at java.base/java.security.AccessController.doPrivileged(Native Method) 
 
Workaround
: Contact your administrator, OS vendor, licensed font provider, or IT department to verify your server (status report PDFs are generated server-side, not client-side) has the following fonts or font substitutions in place:
  • Arial
  • Courier New
  • Times New Roman
To support users who set their Clarity PPM language to Chinese, Japanese, or Korean, (only Japanese is supported for Release 15.6.1) verify your server has the following fonts or font substitutions in place:
  • MS Gothic
  • Gulim and GulimChe
  • SimSun
  • Google NoTo Sans and NoTo Serif
The API-1019 error code can also mean you are attempting to use a Studio attribute in the New User Experience that does not have a valid REST API alias name.
DE49225: TSV Finish Period Date can be set to occur before Start Period Date which causes issues in Grids
  1. Navigate to any Project Staff Grid
  2. Click on View Options
  3. Select Allocations in Per-Period Metrics
  4. Select Months for Period
  5. Start Period is set to current month by default
  6. Select Finish Period that is earlier than start - example 2010-05
Expected: Perhaps a warning or error or even re-setting Finish To current Start Period
Actual: No Error. TSV does not display in grid; however, if the Allocation Totals are configured in the Grid, user is unable to edit them. Other issues could occur.
The 'totals' field appears editable and the user can enter a value, but the value bounces back to the original value without any error.  
Workaround
: To ensure there are no side-affects to this type of configuration, select a Finish period equal to or greater than the start period or clear out the per-period metrics.
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.1) 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.1.
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 
    modulo
     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 
java.lang.OutOfMemoryError
 condition to bring down the application service. Release 15.4 and higher releases include this bug fix.
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 
random
 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.1.
Known Issue Due to Dropped Support for Languages
This release no longer supports the following languages:
Catalan
Czech
Danish
Finish
Hungarian
Dutch
Norwegian
Polish
Russian
Swedish
Turkish
Chinese-Simplified
Chinese-Traditional
Korean
As a result, a user might see a raw text label or English text in the user interface instead of translated text.
Workaround
: Switch your Clarity PPM account settings to one of the supported languages listed in the Release Notes.
Known Issue: Replacement Capability Not Available in the Project STAFF Grid
In this release, the ability to replace a resource, role, or team in the STAFF grid is temporarily unavailable. This feature was introduced in 15.6, is temporarily unavailable in 15.6.1, and is planned to be restored in a future release. 
Workaround
: In the main menu, click 
Staffing
 to perform replacement actions or use Classic PPM with or without the optional Channels feature.
Export to CSV Shows No Per-Period Metric Data Unless Totals Column is Present
The project STAFF and ASSIGNMENTS grids use the Totals and Per-Period Metrics columns for ETC, ETC Cost, Actuals, and Actual Cost.
  • If the Totals column and the Per-Period Metrics columns are configured on the grid, the Export to CSV file feature works as expected. 
  • If you don't have the Totals column configured in the grid, the export does not work as expected (all per-period metric columns are blank).
Workaround
: In the grid, click Column Panel and add the Totals column to the grid layout before using Export to CSV.
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=12.2.0.1.0
[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 
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.
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:
Upgrade 
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
Supported Upgrade Paths for Release 15.6.1
To upgrade 
directly
 to this release (15.6.1), your current release must be 14.4 or higher. The 15.6.1 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.1.
  • You cannot upgrade to Release 15.6.1 
    directly
     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 
    indirect
     upgrade is still supported. For example, upgrade to 14.3 and Jaspersoft 6.4.2 first. Then upgrade to 15.6.1 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.4 to 15.5, from 15.5 to 15.5.1, from 15.5.1 to 15.6, and from 15.6 to 15.6.1.
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 
    Versions
     menu at the top right of that docops page.
    For example, select 15.1 and verify you installed the 15.1.0.9 patch or select 15.3 and verify that you installed the 15.3.0.5 patch before starting your upgrade to 15.6.1. After the upgrade, install the latest 15.6.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. You can also visit the CA PPM Community to collaborate with other community members about your specific questions.
Pre-Upgrade: Run the Installation Checker
The Installation Checker (checkinstall) utility assesses any installation or 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.
 
Follow these steps:
 
  1. Extract the 
    Clarity PPM
     installer to the 
    Clarity 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 
Clarity 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 
Clarity 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 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 file in another directory, the installer prompts you for the file location.
Upgrade Large Data Sets
If your 
Clarity 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 this release. Create a 
memory.properties
 file 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
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
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.
Pre-and-Post-Upgrade: Preserve Your File Directory Customizations
During the upgrade, you are prompted for the target installation directory. New pre-upgrade and post-upgrade steps let you copy files to and from the 
Clarity PPM
 directory using ant-based scripting. Use ant scripts to automate preserving and restoring customization in the 
Clarity 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>
Post-Upgrade or Post-Install: Optimize Oracle 12c Performance
On local installations of Oracle 12c R1 or R2, you might detect a regression issue with Oracle 12c when ORDERED hint is used in structured queries. An Oracle bug in 12c R2 can degrade performance if the optimizer is set to 12.2.0.1.
  • For systems using Oracle 12c R1 (12.1.0.2), no further action is required.
  • For systems using Oracle 12c R2 (12.2.0.1), you can optimize performance by setting the optimizer to 12.1.0.2. We recommend applying this optional local fix.
 
Follow these steps
  1. From a command prompt in Oracle, enter the following lines:
    sqlplus / as sysdba ALTER SYSTEM SET "_fix_control" = '17800514:0'; Exit;
  2. Run the following command:
    ALTER SYSTEM SET OPTIMIZER_FEATURES_ENABLE= '12.1.0.2' SCOPE=BOTH;
  3. Verify that your Oracle 12c R2 initialization file parameters appear similar to the following example:
    *._fix_control='17800514:0' *._optimizer_multi_table_outerjoin=FALSE *.audit_file_dest='/fs0/oracle/12201/12c/admin/niku/adump' *.audit_trail='DB' *.cluster_database=FALSE *.compatible='12.2.0.1' *.control_files='/fs0/oracle/12201/12c/oradata/niku/CONTROL01.CTL','/fs0/oracle/12201/12c/oradata/niku/CONTROL02.CTL' *.cursor_sharing='FORCE' *.db_block_size=8192 *.db_name='niku' *.diagnostic_dest='/fs0/oracle/12201/12c/admin/niku/udump' *.dispatchers='(PROTOCOL=TCP) (SERVICE=nikuXDB)' *.local_listener='LISTENER_NIKU' *.nls_comp='BINARY' *.nls_date_format='YYYY-MM-DD HH24:MI:SS' *.nls_language='AMERICAN' *.nls_sort='BINARY' *.nls_territory='AMERICA' *.open_cursors=1000 *.optimizer_adaptive_plans=false *.optimizer_adaptive_reporting_only=TRUE *.optimizer_adaptive_statistics=FALSE *.optimizer_features_enable='12.2.0.1' *.optimizer_inmemory_aware=FALSE *.pga_aggregate_target=4G *.processes=1000 *.remote_login_passwordfile='EXCLUSIVE' *.session_cached_cursors=1000 *.sessions=1536 *.sga_target=80G *.streams_pool_size=536870912 *.trace_enabled=TRUE *.undo_tablespace='UNDOTBS1'