Change Impact and Upgrade

ccppmop158
HID_HID_release_info_change_impact_od
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.8. 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 information see Hardware and Software Compatibility Specifications
For installation and upgrade related information see Installing and Upgrading
For example, you are upgrading from Clarity PPM Release 15.3 to 15.8. Review the changes in releases 15.4, 15.4.1, 15.5, 15.5.1, 15.6, 15.6.1, 15.7 and 15.7.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 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.8, 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.
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.
2
Hierarchy Enhancements
Create and Manage Custom Metrics for Hierarchies
You can use the powerful roll-up feature and hierarchy card metrics to ensure you can see the total cost to implement a program, a strategy, a product, an investment, or any other hierarchy. Clarity PPM allows you to roll up hierarchy card metrics using either an aggregation or calculation method. Hierarchies include a new capability to define Aggregation or Calculation metrics.
GT
Hierarchy roll-up is automated when defined metrics are applied to an investment type. While aggregation metrics roll up within the entire hierarchy across all investments, calculation metrics apply to a single investment. Calculation Metrics perform basic mathematical operations on stock attributes, custom attributes, and aggregation metrics and display the value on a hierarchy card.
  • Aggregation metrics roll up within the entire hierarchy across all investments while calculation metrics apply to a single investment
  • Hierarchy aggregation or calculation metrics support create operations and delete operations. You can edit the metric name but not the definition of the metric. You have to delete a metric and create a new metric if you want to make minor changes to your metric and avoid duplication.
  • Hierarchy aggregation or calculation metrics cannot be created or updated via XOG or Classic Clarity PPM.
  • Field level security (FLS) is not applied to information displayed in the hierarchy.
  • Attributes configured as a hierarchy card metric are rounded up and displayed.
  • Attributes configured as a hierarchy card field are not rounded up and displayed as is.
  • The Hierarchy aggregation and calculation metrics is a new functionality that is only applicable to the New User Experience.
To learn more about hierarchies, see New User Experience: Create and Edit Hierarchies.
Upgrade Action
: No action required. You can use this capability to create aggregation and calculation metrics for your existing hierarchies. 
Create Custom Attributes for the Hierarchy Object
You can now create custom attributes for the Hierarchy object in Clarity PPM. These attributes will be available for inclusion in the hierarchy list grid, Details panel, column panel, and filters.
GT
To learn more about hierarchies, see New User Experience: Create and Edit Hierarchies.
Upgrade Action
: No action required. You can use this capability to create custom objects and view them within your existing hierarchies.
Configure Tree Cards Based on Investment Type
You can select the various custom or stock lookup attributes that will be displayed as the card title, card fields, and card metrics for specific investment types. Clarity PPM allows you to select different attributes to different investment types. For example, you can see Planned Cost and Planned Benefit for ideas and see Planned Cost and Actuals for projects.
GT
To learn more about hierarchies, see New User Experience: Create and Edit Hierarchies.
Upgrade Action
: No action required. When you upgrade to this release of Clarity PPM, all your investment types will include the same title, field, and metrics that you configured in Clarity PPM 15.7.1. You can now update these details for different investment types based on your business needs.
Set the Color of Investment Cards
You can select the custom or stock attribute that the board can use for the color of each card. Your selection is applicable to all the cards in the hierarchy.
GT
To learn more about hierarchies, see New User Experience: Create and Edit Hierarchies.
Upgrade Action
: No action required. Work Status will be the default attribute for your hierarchies. You can select a different attribute after you upgrade to Clarity PPM 15.8.
Import Investments by using a Simplified Interface
You now use the Import button to select a single investment type and select all the relevant investments that you want to add to the hierarchy. If you use the back button to navigate back to the hierarchy before importing the investments, you will lose all your selections.
GT
To learn more about hierarchies, see New User Experience: Create and Edit Hierarchies.
Upgrade Action
: In Clarity PPM 15.7.1, you could click the Import button once and select multiple items from Ideas, Projects, and Custom Investments. This behaviour is no longer applicable in Clarity PPM 15.8. You now click the Import button and select an investment type. You then select all the relevant investments and click the ADD button to add the investment items to the hierarchy. You then click the Import button again to select a different investment and add investment items.
Export Hierarchies as a PDF File
You can select a hierarchy and export the complete hierarchy tree to a PDF file.
  • Clarity PPM does not support the PDF export for double-byte languages in this release.
  • Clarity PPM does not support PDF for languages such as French that use spaces as delimiters in this release.
GT
To learn more about hierarchies, see New User Experience: Create and Edit Hierarchies.
Upgrade Action
: No action required. You can export your existing hierarchies as PDF files. 
The following video describes the various enhancements that are made to hierarchies in this release.

This video will not be available when you download the documentation in PDF format. Click here to watch the video on YouTube.
Enhancements for Administrators
Manage Saved Views
Clarity PPM
allows you to save and modify multiple views that help you achieve your business goals. Some of the key actions a user can perform are:
  • Save an existing configuration in the grid, board, or timeline layout as a view
  • Access views saved by other users
  • Mark relevant views as favorites so that you can access them easily
  • Search for specific views
  • Delete your views
SavedViews1
The Clarity PPM administrator can also assign the Views – Administer access to a resource. Any resource with this access right can:
  • Assign specific views as default views for all users
  • Delete views created by other users
  • When administrators define multiple default views then the views are listed in alphabetical order.
  • When a new user navigates to the grid view that does not have the default view then they will see out of the box layout.
  • Only a saved view can be defined as the default view.
To learn more about saved views, see Common Components.
Upgrade Action
: The View panel has been updated. You will now see your views categorized into Defaults, Favourites, and Others. When you save a new view, it is automatically saved as a Favourite. You can use the Manage option to select and clear favorite views. A Clarity PPM administrator can assign the Views – Administer rights to a user. Then the user can then assign specific views as default views for all users.
The following video describes how to manage saved views in this release.

This video will not be available when you download the documentation in PDF format. Click here to watch the video on YouTube.
New User Experience: Secure Field Level Access
You can now secure fields to ensure only specific groups of users can access specific fields or attributes. As a blueprint administrator, you need to configure all the secured attributes for ideas or projects in blueprints and display or hide them based on the access rights.
FieldLevelSecurity
You can display or hide specific fields in ideas or projects at the group level. All users who belong to the specific group can access the secured fields. However, as the administrator, you can view all the attributes when you configure blueprints. The new field-level security feature lets you provide users with access to secured fields and hide them as necessary. Users who have access to the secured attributes, can view them in both ideas or projects board and grid view.
  • Field level security always takes precedence over Instance, or OBS, or Global rights in a project or idea.
  • Field level security is applicable to both ideas and projects.
  • Field level security is
    not
    applicable to Hierarchy.
For more information about field-level security, see Secure Field Level Access.
Upgrade Action
: No action required. You can upgrade to Clarity PPM 15.8 and secure fields to ensure only specific groups of users can access specific fields or attributes. As a blueprint administrator, you need to configure all the secured attributes for ideas or projects in blueprints and display or hide them based on the access rights.
The following video describes how to secure field level access in this release.

This video will not be available when you download the documentation in PDF format. Click here to watch the video on YouTube.
Create Processes for Custom Investments and Roadmaps
The Roadmaps and Custom Investment objects have been enhanced to support processes. You can now invoke processes based on creation or updates to custom investments and roadmaps. Customers can now use a process to push a roadmap item to another system, such as Rally, for execution. Customers can also use processes to build automation to track and monitor custom investments.
  • Roadmaps are event enabled to allow processes to run against it.
  • Roadmap and Custom Investments will appear as an option under the primary object for processes.
  • Processes can run when you create and update of roadmaps and custom investments.
  • Roadmaps are automatically event enabled after upgrade. Customers have the option to “uncheck” the event enabled flag.
  • When you create custom investments they are automatically event enabled. The event enabled flag cannot be modified after creation.
  • Processes executed against a roadmap or custom investment can only be seen in Classic Clarity PPM.
  • Processes built with action items still require you to act on it in Classic Clarity PPM.
  • Processes cannot be run on roadmap items. However, process start condition can use roadmap, roadmap items, or roadmap item dependency attributes.
  • If you change the name of a custom investment then the “Event Enabled” flag gets unchecked.
  • If you create an action item process then the notification link to the Roadmap or Custom Investment does not work.
  • There is no option to start a process “On Demand” even if you select that option in the process definition. You can run these processes by using the “Execute a Process” job.
Upgrade Action
: Roadmaps are automatically event enabled after you upgrade. Customers have the option to clear the event enabled flag.
The following video describes the process enablement of roadmaps and custom investments in this release.

This video will not be available when you download the documentation in PDF format. Click here to watch the video on YouTube.
Financial Management Enhancements
Budget Plans in Custom Investments
The Custom Investment Financials module now supports budget plans. You can now submit cost plan for approval as budget plan for your custom investment type. For example, a custom investment can be submitted with a high-level budget or a more detailed cost-benefit analysis. As work is executed, actual costs are captured and forecasts are revisited to track performance against the budget. To learn more about custom investment budget plans, see Manage Custom Investment Financials.
Also, the saved views are now shared across the financial modules of different investment types. For example, if you save a view in the Budget Plan grid for a custom investment, the same view is applied to the Budget Plan grid for ideas and projects. To learn more about saved views, see Manage Custom Investment Financials.
Upgrade Action
: No action required. The Custom Investment types blueprint has been updated to include the new Financials module in the default layout.
Budget Plans in Ideas
The Idea Financials module now supports budget plans. You can now submit cost plans for approval as budget plans for an approved idea. For example, an idea can be submitted with a high-level budget or a more detailed cost-benefit analysis. As work is executed, actual costs are captured and forecasts are revisited to track performance against the budget. To learn more about idea budget plans, see Manage Idea Financials.
Also, the saved views are now shared across the financial modules of different investment types. For example, if you save a view in the Budget Plan grid for an idea, the same view is applied to the Budget Plan grid for projects and custom investments. To learn more about saved views, see Manage Custom Investment Financials.
Upgrade Action
: No action required. The Ideas blueprint has been updated to include the new Financials module in the default layout.
New Financials Module for Projects
The New Projects Financials module is based on the Clarity PPM generic grid. You can quickly analyze projects from the new projects financials module by using some features of the generic grid and perform actions such as:
  • Customize the grid and save the views. Saved views are shared across the financial modules of different investment types.
  • Filter the data in the grid based on the business requirements.
  • Use the menu option to take quick actions on the cost plans and budget plans.
  • Use the Group By option to segregate related rows view with aggregated subtotals wherever applicable.
  • Use the column panel to show or hide attributes on the layout.
  • Export the various cost plans, cost plan details, budget plans, and budget plan details along with the data in the grid to a CSV file.
  • Edit data associated with cost plans and budget plans directly in the grid or by using the details layout.
  • The previous financials module based in Clarity PPM is now renamed as
    Financial Plans
    and is added to the default layout for the standard blueprint.
  • An administrator can decide whether Financial Plans (old financials) or Financials (new financials) module appears when users open a project.
  • The new projects financials module must be manually added to the default layout for the standard blueprint. To learn more about the new projects financials module, see Manage Financial Plans Using the New Financial Module.
Upgrade Action
: The Clarity PPM administrator needs to decide whether Financial Plans (old financials) or Financials (new financials) module appears when users open a project.
Create Project Cost Plans and Budget Plans Using the New Financials Module
The new projects financials module supports cost plans and budget plans.
You can create cost plans for projects by using the generic grid layout. You can create a manual cost plan by using the in-line edit option or populate from allocations or populate from assignments. You can also set a cost plan as a plan of record. To learn more about project cost plans, see Manage Financial Plans Using the New Financial Module.
After the cost plan is designated as the POR, submit the POR for approval as budget plan for a project. When the POR is approved, it becomes the budget plan for the project. To learn more about project budget plans, see Manage Financial Plans Using the New Financial Module.
Upgrade Action
: The "Planned to Actuals" and the "Planned to Forecast" "views" applies only to the Financial Plans module.
The following video describes the enhancements that are made to financials for investment objects in this release.

This video will not be available when you download the documentation in PDF format. Click here to watch the video on YouTube.
Timesheets Enhacements
Timesheets Grid - Virtual Timesheets
In order to drive adoption, managers require the proper tools to quickly locate and manage timesheets across multiple periods. In this release, you can view all open timesheets that are created based on the time period that is assigned for the tasks. This will enable managers to filter for open timesheets across multiple active time periods and prepare missing time report directly from the configurable Timesheets grid. You will be able to see all the un-submitted timesheets for which you have the following instance rights:
  • Resource Enter Time
  • Resource Approve Time instance rights
  • Timesheets – approve all and Timesheets – Edit all
Scenario 1:
Mike - a project contributor wants to plan his work for the entire month of July. He needs to get a view of all the open timesheets for July. Doing so helps Mike estimate and plan his workload for the forthcoming weeks and collaborate better with his team. Mike can view all his open timesheets and update them as needed. The following procedure helps Mike to view his open timesheets and enter time for the respective weeks accordingly.
Scenario 2:
Consider a scenario where 100 users are configured for open for time entry. None of the users have navigated to their timesheets to enter time–In this situation, from the (15.7.1) Timesheets grid, Derrick a resource manager does not have the visibility into how many (out of the 100 users in this example) have not entered time because the (15.7.1) Timesheets grid did not include the expected 100 rows for each user's timesheet. The issue has been resolved and the (15.8) Timesheets grid now includes virtual Timesheets providing visibility into how many users have not entered time –allowing Derrick to prepare a missing time report directly from the configurable Timesheets grid.
The Timesheets grid only displays active timesheets – The Review and Approve grid displays timesheets irrespective of their status. For example, active and inactive. The Timesheets grid does not include virtual timesheets for inactive periods.
For more information, see View and Manage Timesheets From Grid Layout
Upgrade Action
: No action required. Project managers and other stakeholders can use the Virtual Timesheets feature in the Timesheets grid.
Resource OBS filter for Timesheets
The Resource OBS filter is introduced in the Timesheets grid in this release of Clarity.
Example:
Derrick the resource manager wants to view all the timesheets that he owns and the timesheets that he needs to review for approval from the timesheets grid. With the Resource OBS filter for Timesheets, Derrick can now filter timesheets using Resource OBS, locate resources from specific locations of his organization, and save his current search as a Saved View so that others in his team can use the same view later.
The Resource OBS attribute is only available as a filter option in the Timesheets grid. The Resource OBS attribute is not available within the column panel for inclusion in the Timesheets grid or the flyout.
Upgrade Action
: No action required. Project managers and other stakeholders leverage the Resource OBS filter to locate resources from specific locations in the organization.
Timesheets Grid - Employment Type
Derrick is a resource manager. He wants to quickly review and approve his team’s timesheets based on their employment status whether they are contractual or are on his organization's payroll. The employment type attribute is now available for Derrick to be able to filter resources based on whether they are employees or contractors. Derrick can also select Employment Type from the Details panel to configure the column in the Timesheets grid. Derrick can now do the following:
  • View Employment Type lookup as an attribute in the Timesheets Grid.
  • Filter data using the Employment Type attribute.
  • Multi-select the values in Employment Type lookup and filter data.
  • View Employment Type in Timesheets Grid and the Details panel.
If My Timesheets is configured to allow end-user column configuration, by design the Resource OBS or Employment Type attributes are not available.
Upgrade Action
: No action required. Project managers and other stakeholders can now approve their team’s timesheets based on their employment status.
Delete Duplicate Timesheets Job
In limited customer cases, Clarity erroneously creates duplicate timesheets for a given time period. Customers requested the capability to help identify duplicate timesheets associated with a single time period/resource and remove them from the system in order to improve their internal timesheet audit processes. The new job helps the administrator identify the duplicate timesheets associated with a single time period and a resourceID and removes them from the system. Like all Clarity jobs, it can be executed manually or via a pre-determined schedule.
Upgrade Action
: No action required. Administrators can now identify the duplicate timesheets associated with a single time period and a resourceID and remove them from the system.
The following video describes the enhancements that are made to timesheets in this release.

This video will not be available when you download the documentation in PDF format. Click here to watch the video on YouTube.
Roadmap Enhancements
Import Roadmap Items by using OBS - Infinite Scroll (Enhancement)
Infinite scroll support is now available when using an OBS to import Projects, Ideas or Custom Investment to a roadmap. You can now be able to scroll through the entire OBS, using infinite scroll, and select and import the respective investments as roadmap items.
Upgrade Action
: No action required.
Roadmap List Enhanced to use Common Grid
The Roadmap list has been refactored and now incorporates the common grid toolset with the following capabilities:
  • Saved views
  • Robust filtering
  • Group By
  • Export to CSV
  • Add custom attributes to roadmap object for inclusion in grid, fly-out, column panel, and filters.
Upgrade Action
: No action required. You can use the capabilities of the Clarity PPM common grid.
The following video describes the enhancements that are made to roadmaps in this release.

This video will not be available when you download the documentation in PDF format. Click here to watch the video on YouTube.
Demand Management Enhancements
Staffing Ideas
Units.jpg
You can use the grid in the STAFF module to identify and add people, roles, teams, and even non-labor resources by name or ID. The STAFF module is built using the same common component that is used in Projects. You can ask your administrator to use blueprints to add the STAFF module to your custom investment item.
Some key activities you can perform by using the STAFF module are:
  • Add people, roles, teams, and even non-labor resources by name or ID
  • Use PER-PERIOD METRICS field to view a time-scaled series of time-sliced data for allocations
  • Set the hard of soft booking type for roles and resources
  • Replace a role with a different role, a team, or a resource.
  • Replace a resource with a different resource, team, or a role.
  • Replace a team with a different team, a resource, or a role.
Upgrade Action
: The Standard blueprint associated with your Idea will include the STAFF module. Clarity PPM will not update any user-defined blueprints. You need to request your administrator to create a copy of the Standard blueprint and assign the STAFF module to your ideas.
The following video describes the introduction of staffing in ideas in this release.

This video will not be available when you download the documentation in PDF format. Click here to watch the video on YouTube.
UI Enhancements
Drill-Down Into Investments
You can click an investment and drill-down to view specific details. When you want to go back to the investment home page where all investments are listed, you can simply click the breadcrumb on the top-left corner.
Upgrade Action
: No action required.
The following video describes the various enhancements that are made to board view in this release.

This video will not be available when you download the documentation in PDF format. Click here to watch the video on YouTube.
DWH Enhancements
Calculated Risk and Requested Manager Added
Calculated Risk and Requested Manager attributes have been added to the data warehouse. These attributes will be added when you upgrade to Clarity PPM 15.8 and run the Load Datawarehouse job.
Upgrade Action
: These attributes will be added when you upgrade to Clarity PPM 15.8 and run the Load Datawarehouse job.
The following video describes the enhancements that are made to the data warehouse in this release.

This video will not be available when you download the documentation in PDF format. Click here to watch the video on YouTube.
Generic Enhancements
Updated End User License Agreement
In this release, the end-user license agreement (EULA) is updated in Clarity PPM - Clarity System Administration (CSA).
Upgrade Action
: No action required.
The copyright information is updated in the following areas:
  • Classic Clarity PPM and Clarity PPM New User Experience
    • Login page
    • About section
    • Forgot Password Page (Applicable Only for New UX)
  • Clarity System Administration (CSA)
    • Login page
    • Footer (Applicable ONLY for CSA)
  • Scheduler applications such as Microsoft Project and Open Work Bench (OWB), XML Open Gateway (XOG), Update Copyright information on Classic/New UI
    • Splash screens copyright  message for the client installers
    • About page - OWB
    • Installer popup - OWB
    • Installer - MSP
    • Installer - XOG
    • Schedule Connect popups
Upgrade Action
: No action required.
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 Clarity 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 Clarity PPM, switch to a new browser such as Edge, Firefox, or Chrome.
Dashboards Not Available in Google Cloud Platform
The Project Management Schedule Dashboard and Project Management Cost and Effort Dashboard portlets have been deprecated in the Google Cloud Platform. Please review this KB article for more information.
Users that use Spanish (Peru) locale will now have the period symbol as a decimal separator.
Change
: Users that use the "Spanish (Peru)" locale will now have the period "." symbol as the decimal separator instead of the comma "," symbol.
Impact
: If the user keeps the Peru locale and tries to use the comma as the decimal separator the symbol will be ignored and it will cause entered values to be saved as large integers instead of the expected value with decimal digits. If desired, the user can choose a different locale in account settings that uses the comma as the decimal separator.
More Details
: The Official Institute of Taxation of Peru uses "." as its decimal separator. Therefore Java (JDK 11.0.5) has been fixed to honor the period symbol instead of a comma. For more details on the Java fix reference their KB article.
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.
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 the translated text.
Workaround
: Switch your Clarity PPM account settings to one of the supported languages listed in the Release Notes.
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.8
Please review the table to identify the minimum supported release from which you can upgrade to the latest version of Clarity PPM.
Clarity PPM Version
Minimum Supported Version for Direct Upgrade
15.8.0
15.3
15.7.1
15.3
15.7.0
15.2
15.6.1
15.0
15.6.0
15.0
15.5.1
14.3
15.5.0
14.3
15.4.1
14.1
15.4.0
13.2
15.3
13.2
15.2
13.2
15.1
13.2
  • If you have Release 14.3 or older, your release is no longer supported. Upgrade to Release 15.4 first, and then upgrade to 15.8
  • You cannot upgrade to Release 15.8
    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.8 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, from 15.6 to 15.6.1,  from 15.6.1 to 15.7, and from 15.7 to 15.7.1, and from 15.7.1 to 15.8
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 help 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.8. After the upgrade, install the latest 15.8 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 (On-Premise Only)
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  (On-Premise Only)
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  (On-Premise Only)
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 2016 for this release, set the compatibility level to 130 from SQL Server Management Studio or use the following command:
EXEC SP_DBCMPTLEVEL <database>, 130
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  (On-Premise Only)
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-Premise Only)
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'