Clarity PPM 15.7 Change Impact and Upgrade

ccppmop157
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.7. 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.7. Review the changes in releases 15.4, 15.4.1, 15.5, 15.5.1, 15.6, 15.6.and 15.7 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.7, 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.
HID_HID_release_info_change_impact_od
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 New User Experience: Project Management Enhancements
Manage Projects Effectively by Using the Timeline (beta) Layout
Group By.jpg
You can create and manage all project tasks and their relationships in the Timeline layout. The Timeline view is divided into a Work Breakdown Structure (WBS) on the left and a timeline on the right. The timeline view enables you to review the project plan in a hierarchical display. You can then add, edit, or delete tasks directly in the hierarchical display. You can also select a task, open the DETAILS panel, and edit the task.
Upgrade Action:
No Action Required. When you open the Tasks module, you will automatically see the Timeline Layout. Since this is the first phase of the Timeline layout, you can only see Task Name, Start Date, Finish Date, Status, ETC in the WBS section. Also, the period in the Timeline layout is relative to the project start and finish dates. To learn more, see New User Experience: Project Phases, Milestones, Tasks, and To Do Items.
Replace Existing Staff Member or Assignee in Projects
Staff.jpg
You can use the Staff grid and the Assignment grid to replace staff members in projects. You can make the following replacements in the Staff grid:
  • 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:
No Action Required. In Clarity PPM 15.6.1, you could not use the Staff Grid in projects to replace staff members. You can now use in-line edits to make all replacements in the Staff grid and the Assignments grid. Remember that when you replace a staff member who has actuals on a project with another staff member, the original staff member remains in the Staff grid and the replacement is added and assumes the remaining ETC.
Perform Hard Allocations in the Project Staff Grid
Group By.jpg
You can enter both soft allocations and hard allocations in the Project Staff grid. You can use hard booking to confirm that the resource is committed to the project. The booking status is mixed when a resource is both soft and hard allocated to the project, or the soft allocation for the resource does not match the hard allocation. This allows project and resource managers to collaborate and make accurate staffing decisions.
Upgrade Action:
No Action Required. Remember that the Hard Allocation action is available only if the Allow Mixed Booking project management setting is checked in Classic PPM. Also, you cannot select "Mixed" in the Booking Status field. You will get an error message.
To learn more about Mixed Bookings, see see New User Experience: Staff a Project Team
Drag and Drop Cards on the Board Layout for Projects
Group By.jpg
You can view projects as cards, which you can arrange with drag-and-drop precision on a Board layout with columnar swim lanes.
Upgrade Action:
No Action Required. The Board layout will automatically be available on the Projects page. Remember that you cannot open a project directly from the Board layout. You need to navigate to the Grid layout to open a project.
To learn more about our generic board-view component, see Getting Started with the New User Experience.
Launch Clarity PPM Gantt and External Schedulers by using the Actions (Three-Dot) Menu
You can use the three-dot Actions menu in the Tasks module to launch PPM Gantt or an external scheduler (Microsoft Project or Open Workbench). The Actions menu also allows you to export the project plan as a CSV file from the Grid layout.
Group By.jpg
Upgrade Action:
No Action Required. The Actions menu is now available across all layouts in the Projects Tasks module.
To learn more about using the Actions menu, see New User Experience: Project Phases, Milestones, Tasks, and To-Do Items.
Clarity PPM New User Experience: Generic Enhancements
Individual Members Can Enter Time For Tasks Assigned to Teams
Individual resources, who are members of a team, in Clarity PPM can discover and enter time for tasks assigned to their team. A project manager can approve their timesheets and create a custom report to review the time submitted by individual users. The project financials will reflect the team's actuals based on the time entered by individual members of the team.
Upgrade Action:
Prior to this release, only those users with the rights to ‘enter time for others’ could enter time for a task assigned to a team. From Clarity PPM 15.7 onwards, individual resources, who are members of a team, can discover and enter time for tasks assigned to their team.
Group By.jpg
Some key points to remember are:
  1. In case the project task is assigned both to an individual who is a part of the team, and the team itself, the user will see the same task twice in the timesheet. The labels associated with the task help individuals distinguish the tasks.
  2. The Cost Plan for the project displays actuals for the Team resource based upon time entry by individual team members.
  3. The Data Warehouse has been modified to help you identify the resources who have contributed to the team time entry. Please review the Data Warehouse section of the Change Impact Guide to learn more about the modifications.
Enhancements to the DETAILS Panel
The DETAILS Panel is available as two-column layout enabling you to easily and quickly edit data in Clarity PPM. The layout can be resized to take up 75% of the screen and the width is persisted for users across pages in the New User Experience. You can now have more than one field per row in the Details column and can resize fields horizontally. You can also resize string fields vertically if the field is greater than 80 characters. The fields available in the Details panel are associated with your view.
Group By.jpg
Upgrade Action:
Prior to this release, the DETAILS panel was available in a single-column layout. When you upgrade to Clarity PPM 15.7, you will see all the fields aligned on the left side of the DETAILS panel. You can rearrange the fields based on your requirements.
Some key points that you need to remember are:
  • Clarity PPM Roadmaps, Task List, and the Project Financials modules do not support the two-column DETAILS panel in this release.
  • When you configure a multi-value lookup, ensure you configure it to take up both the columns of the DETAILS panel, else data will not be displayed.
To learn more about our generic board-view component, see Getting Started with the New User Experience.
Create New Records from the Board and Grid Layout
From Clarity PPM 15.7 onwards, whenever you create a new record from the board layout, the DETAILS panel is automatically displayed. The panel includes all the fields that you have configured and also includes all the required fields, without defaults, needed to create a new record. After you populate the required fields, Clarity PPM refreshes the DETAILS panel and creates a new record. You can then continue editing the record and close the DETAILS panel after finalizing your changes.
When you create a new record from the Grid layout, the required fields without default values are automatically added to the grid.
Group By.jpg
Upgrade Action:
Prior to Clarity PPM 15.7, you would be able to use the "quick-create" functionality on the board:
  • When all required fields had default values
  • The system specified the value for the "Name" required field (ex:  New Task)
This "quick-create capability" has been removed in Clarity PPM 15.7. If you want to use the quick-create functionality in Clarity PPM 15.7, you need to supply a default value for the Name field in Classic Clarity PPM. For example, if want to continue the quick-create ability on the task board, you will need to go to the Task object in Classic Clarity PPM and add New Task as the default value for the Name field.
Some key points you need to remember while creating new records in the Board layout are:
  • Your record will be lost if you leave or refresh your current view without completing all mandatory fields.
  • Any required field that has a default value defined will not be auto-displayed and you will need to add that field manually to the DETAILS panel to change its value.
  • If you configured your DETAILS panel to display specific fields, the required fields are added at the end of the list.
  • If you configured your DETAILS panel to display a multi-value lookup field, it will be displayed a single row and will not appear unless you expand the field to take up more than one row.
  • To learn more about our generic board-view and grid view components, see Getting Started with the New User Experience.
Select Relative Period Dates for Projects, Ideas and Custom Investments
The Staff, Assignment, Cost Plan, and Cost Plan Details modules now have the option to define periods as relative dates. Let's take the example of projects. The Start Period can be set to Project Start and the End Period can be set to Project Finish. When you save your view with these settings, the same view can be applied across all your projects. When you open each project, the Project Start and Project Finish will automatically assume the start and end date of that particular project.
Group By.jpg
Upgrade Action:
No Action Required. The Relative Period dates will be available for use in Projects, Ideas, and Custom Investments.
You can view and edit stock and custom URL attributes in the New User Experience. You can continue to use processes in Classic Clarity PPM to set and lock the value of URL attributes. The updated value of the URL attributes will be reflected in the New User Experience.
Group By.jpg
Upgrade Action:
Ensure that you API-enable the relevant custom URL attributes that you access in the New User Experience.
Support for Static Dependent and Parameterized Lookups
Clarity PPM New User Experience supports stock and custom static dependent lookups such as Investment Type and stock and custom parameterized lookups such as Project Type and Project Category. The lookups are supported in common grids, DETAILS panel, boards, and filters in the New User Experience.
Upgrade Action:
Ensure that you API-enable the relevant custom URL attributes that you access in the New User Experience.
Some key points that you need to remember while using static dependent lookups are:
  • Static dependent lookup will appear in New User Experience once API alias value is populated
  • Static dependent lookup can be added to board cards.
  • The Static dependent lookup field in grid layout will display the hierarchical structure as a long path.
  • The Grid layout cell will display the highest and lowest values in the hierarchy with ellipsis in the middle.
Some key points that you need to remember while using parameterized lookups are:
  • Parameterized lookups will appear in New User Experience once API alias value is populated
  • Parameterized lookups lookup can be added to board cards.
  • When you use parmeterized lookups in filters, then the filter will display all possible options.
To learn more about static dependent and parameterized lookups, see Getting Started with the New User Experience.
Enhancements to the Common Grid
The common grid in Clarity PPM has been enhanced to provide the following key capabilities:
  • Column panel search and drag-drop capabilities
  • Excel-like calculation in grid status bar
  • Enhanced Group By functionality
Upgrade Action:
No Action Required. The new features available with the common grid will be automatically available to you when you upgrade to Clarity PPM 15.7.
Enhanced Filtering Capability
The filtering capability in Clarity PPM 15.7 has been enhanced to support the OBS Unit mode, parametrized lookups, static dependent lookups, money, and URLs. You can also filter Tasks and To-Dos by using the Project ID in the Tasks page within a project.
Upgrade Action:
No Action Required. You can start using OBS Unit mode, parametrized lookups, static dependent lookups, money, and URLs in filters from Clarity PPM 15.7 onwards. To learn more about the filtering capability, see Getting Started with the New User Experience.
Create and View Teams in the Resources Page
This release includes the new Resources page with the standard grid layout for creating and viewing teams in the New User Experience. The new Resources grid supports familiar filters, sorting, column selection, settings, and saved views. Resource Managers and administrators can now create teams directly in the Clarity PPM New User Experience.
Group By.jpg
Upgrade Action:
Prior to Clarity PPM 15.7, you could create teams in the Administration Page of the New User Experience. Administrators can grant a new
Resource Management – Navigate
access right (view-only license type) that allows users to click the new Resources page in the main menu. To learn more about creating teams, see New User Experience: Configure Teams on the Resources Page.
Customize Clarity PPM Notification Templates
The hard-coded header and footer associated with the notification templates have been removed. Many customers rebrand Clarity PPM during their implementation and can now send out notifications with only their brand messaging to provide a more personalized experience.
Upgrade Action:
Some of the key points you need to remember when you upgrade to Clarity PPM 15.7 are:
  • Hardcoding of Clarity PPM and copyrights no longer exist in the email notification HTML template.
  • The default value of the Email header field is Clarity PPM.
  • The default value for the email footer field will include the Broadcom copyright details. This will be in English and not translated to any other language
  • You can change the default values to your preferred phrasing and language.
  • When you upgrade to Clarity PPM 15.7, your customized header and footer values will not be overwritten.
  • To learn more about customizing notification templates, see Configure Notifications and Notification Templates
Clarity PPM New User Experience: Demand Management Enhancements (Ideas)
Convert an Idea to a Project
Once you have evaluated an idea, determined it has value, and approved it, you can convert it to a project by using a project template. When you convert an idea to a project, you get options to:
  • Copy Financials: Allows you to include any financial data for the idea in the conversion to the project.
  • Copy Team: Allows you to include any resource or role staffing data from the idea to the project.
Group By.jpg
Upgrade Action:
No Action Required. Some key points you need to remember while converting ideas to projects are:
  • After converting an Idea to a Project, the Idea status (in the Grid & Board layouts) is updated to ‘Converted’.
  • After converting an Idea to a Project, the Project Grid and Board can be configured to include the “Originating Idea” column for added visibility.
  • If you copy the Idea Team while converting an idea to a project, the resulting project will have roles associated with both the idea and the project template chosen during the conversion process.
Create Cost Plans for Ideas
You can create cost plans for ideas by using the standard grid layout in the Clarity PPM New User Experience. You can create a manual cost plan or populate from allocations if you have resources associated with an idea. You can also set a cost plan as a plan of record and submit it for approval.
Group By.jpg
Upgrade Action:
No Action Required. Some key points you need to remember are:
  • The Cost Plan List and Cost Plan Detail pages support including custom attributes in both the grid and DETAILS panel.
  • Ideas can have multiple cost plans.
  • If an Idea has existing cost plans in Classic PPM, they are automatically included in the Cost Plan List view in the New User Experience.
  • You can add new cost plans by using the in-line edit option.
  • You can select a cost plan as the plan of record by using the grid action menu, the grid column, or the DETAILS panel.
  • To learn more about using cost plans with ideas, see New User Experience: Manage Idea Financials.
Create Custom Sub Objects for Ideas
You can now associate an API Attribute ID with idea sub-objects that you created in Classic PPM. These sub-objects will be available as modules in the idea blueprint. You can add these modules to an Idea blueprint and associate appropriate ideas with that blueprint. This will ensure that you can configure customized layouts for ideas based on different business needs.
Group By.jpg
Upgrade Action:
Ensure that you API-enable relevant custom sub-objects so that they are available in the New User Experience. To learn more about ideas, see New User Experience: Capture, Develop, and Approve New Ideas.
Drag and Drop Cards on the Board Layout for Ideas
You can now view ideas as cards, which you can arrange with drag-and-drop precision on a board layout with columnar swim lanes. Some key capabilities available in  the Board layout are:
  • Ability to customize your board view by configuring board/card options and defining picklists
  • Ability to edit a project by selecting a card and using the DETAILS panel.
  • Ability to save your configurations as a view that can be shared with other users.
Upgrade Action:
No action required. The board layout will be displayed when you navigate to the Ideas page. Ensure you create your own picklists to help visualize your ideas. To  learn more about ideas, see New User Experience: Capture, Develop, and Approve New Ideas.
Clarity PPM New User Experience: Custom Investments Enhancements
Create Custom Sub-Objects for Custom Investments
You can now create custom sub-objects for custom investments and add attributes to the sub-object. The API Attribute ID for new sub-objects will be automatically assigned. You can now associate an API Attribute ID with custom investment sub-objects that you created in Classic PPM. These sub-objects will be available as modules in the custom investment blueprint. You can add modules to a Custom Investment blueprint and associate appropriate investments with that blueprint. This will ensure that you can configure layouts for custom investments based on different business needs.
Group By.jpg
Upgrade Action:
You need to provide an API alias for the custom investment sub-object. The sub-object will then be automatically available in the custom investment blueprint as a module. Ensure that you add this module and publish your blueprint to make the sub-object available to users.
To learn more about custom investments, see New User Experience: Configure Custom Investment Types.
Create Cost Plans for Custom Investments
You can create cost plans for custom investments by using the standard grid layout in the Clarity PPM New User Experience. You can create a manual cost plan by using the in-line edit option and set it as a plan of record.
To learn more, see New User Experience: Manage Custom Investment Financials.
Add Links to Custom Investments
The Links module has been introduced in Custom Investment blueprint, which allows you to add link categories and links to custom investments.
Group By.jpg
Upgrade Action:
The Links module has not been localized in Clarity PPM 15.7. Customers using English can use this feature. To learn more see, New User Experience: Create and Edit Custom Investments.
Clarity PPM New User Experience: Roadmaps Enhancements
Sync Project Capacity Attributes in Roadmaps
When you sync roadmaps with projects, you can select between syncing allocations or assignments. If you select assignments, Clarity PPM will use add the ETC and the Actuals for the project to calculate assignments and synchronize the project with the roadmap. When you import a project as a roadmap all the relevant data associated with the project is imported as roadmap attributes. When you synchronize a roadmap, it only updates the attributes you selected in the Sync Linked Items window.
Group By.jpg
Upgrade Action:
The Allocations option is selected by default. When you clear the Capacity checkbox, the Assignments and Allocations options are disabled. To learn more about synchronizing project attributes in Roadmaps, see New User Experience: Top-Down Planning with Roadmaps
Roadmap Timeline Enhancement
The Roadmap timeline view has been enhanced to provide you options on how to view the text within the roadmap item. The Show Text Overflow option allows you to have control over how much roadmap item name is displayed and allows you to better interact with roadmaps. Clearing this option will trim the roadmap item name to within the length of the roadmap item
Group By.jpg
Upgrade Action:
For the new or upgrading customer, the Show Text Overflow option is checked to mimic the existing behavior.
Some key points that you need to remember are:
  • Trimming the roadmap item name could result in difficulty in identifying the specific item.
  • The length of the roadmap item name depends on the size of the roadmap item.
  • Any name that is trimmed ends with an ellipsis.
  • When the Show Text Overflow option is not checked then any roadmap item listed as a milestone (without start date) will not have their name displayed.
Clarity PPM Rest APIs Support
Announcing Support for REST APIs
Clarity PPM now supports the dynamic new REST API infrastructure behind its expanded New User Experience feature set.
Support for CORS
Network administrators commonly apply same-origin restrictions to network requests. These restrictions prevent a client-side web application from obtaining data retrieved from another origin and also limit unsafe HTTP requests that can be automatically launched toward destinations that differ from the original running application. With CORS, our REST APIs response can include an Access-Control-Allow-Origin header with the original value of the request acting as a key to allow access to the resource content. As an administrator or developer, you can validate that the key-value and origin for the request match. This feature was launched as a BETA in Clarity PPM 15.6.1 `
Support for REST API Keys
You can configure the REST API key authentication features to enable business users to integrate data between the Clarity PPM New User Experience and other client applications. Integration architectures can allow users to authenticate through the REST API and accomplish specific Clarity PPM actions without going into the user interface. Through API keys, user SSO credentials, access rights, and status settings match their API token. This feature was launched as a BETA in Clarity PPM 15.6.1
Upgrade Action:
No upgrade impact. You can use the Swagger documentation to learn more about APIs in Clarity PPM.
To learn more about the interactive REST API documentation and REST APIs in Clarity PPM, see REST API: Documentation for Authorized Developers.
Datawarehouse Enhancements and Reporting Enhancements
Data Warehouse Enhancements
Group By.jpg
The Data Warehouse has been modified to include two new tables for team definition object:
  • DWH_INV_TEAM_DEF - One row per team
  • DWH_INV_TEAM_MEMBER - One row for each member on a team
The Data Warehouse has also been modified to include two new columns to Resource dimension table DWH_RES_RESOURCE:
  • TEAM_DEF_KEY
  • IS_TEAM
The table contains one row for each resource or team.
Upgrade Action:
No upgrade impact. You can use the new data warehouse modifications to prepare a custom report which will identify which resources spent time on a task assigned to a team.
Reporting Enhancements
Group By.jpg
The New Customization Overview Report is available in Jaspersoft. It allows you to view:
  • a list of the custom objects and attributes
  • a list of the custom DB objects
  • a list of custom Gel scripts
  • a list of custom NSQL objects (queries and portlets)
  • a list of the custom reports
Upgrade Action:
You need to upgrade the PMO Accelerator add-in after you upgrade to Clarity PPM 15.7 to view the Customization Overview report.
Administrative Enhancements
Enable Manual Sorting for System-Restricted Static Lookups
Administrators can use the new
Reorder Values
tab to manually sort lookup values so they lookups can be effectively used in the New User Experience.
Example
: You can use the Reorder Values tab to reorder the values of the Task Status lookup so that it can be used when you use the board layout in the Tasks module for projects.
Group By.jpg
The following system lookups have been updated to include the Reorder Values tab:
  • Task Status
  • Microsoft Project Task Status
  • Project (Financial) Status
  • Investment Object State
  • Track Mode
  • CPM Type
  • Investment Object Progress
Upgrade Action:
No upgrade impact. You can edit the lookups to reorder them based on your business requirements.
Clarity PPM 15.7 Changes: Additional Changes and Potential Impacts
DE51322: Filters Missing for Saved Views: Projects and Ideas Grid
When you upgrade to Clarity PPM 15.7 from Clarity PPM 15.6.1, the filters associated with a saved view for the Projects grid and Ideas grid are lost.
Steps to Reproduce:
  1. Log into the Clarity PPM 15.6.1 New User Experience.
  2. Navigate to the Projects page or the Ideas page.
  3. Create a couple of filters on the page and save a view.
  4. Upgrade to Clarity PPM 15.7.
  5. Log into the Clarity PPM 15.7 New User Experience.
  6. Navigate to the Projects page of the Ideas page.
  7. Load the Saved view you created in Clarity PPM 15.6.1.
  8. You will see the saved views but the filters would be missing.
Resolution: Please review KB Article 140146 to upgrade successfully and avoid this issue.
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 Clarity 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
      checkbox.
      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
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.7
The following section lists the known issues at the time this release was delivered.
DE50516: Cards are not visible when individually removing the CARD FIELD that is not the last field from the right
In View Options, when you update the card fields and remove the first card field nothing will display on board. This can happen when there are multiple fields selected and any one of the fields is removed from the configuration (except the last field).
Steps to Reproduce:
  1. Log in to the New User Experience.
  2. Click on any board layout (Project, Idea, Custom Investment, or Task).
  3. Click on View Options and navigate to CARD FIELDS.
  4. Remove the first card field. The other cards in the board disappear.
Expected Results: Board should always display cards along with the fields mentioned in card fields.
Actual Results: In card fields on removing the first field, the other cards in the board disappear.
Workaround: Clear all fields in the View Options and re-select the ones you want on the view.  If the view configuration cannot be corrected, delete the current view so the default view can be loaded.
DE50719: Timeline INSERT or NEW item disappears in Filtered State
Steps to Reproduce:
  1. Log in to the New User Experience.
  2. Go to a Project and open the TASKS module. Then open the Timeline layout.
  3. Add a filter to see filtered results.
  4. Select INSERT SIBLING or INSERT CHILD or ADD new task. The task does not appear.
  5. Remove the filter and see the newly created task
DE50592: Not Able to Drag Newly Created Cards on a Custom Investment
You will not be able to drag cards on Chrome, Firefox, and the Edge browser.
Steps to Reproduce:
  1. Log in to the New User Experience.
  2. Open a custom investment and navigate to the Board layout.
  3. Click on a Custom Investment board.
  4. Create a new card and try to drag that card.
Expected Results: You should be able to drag the card.
Actual Results: You will be unable to drag the newly created card.
Workaround: Refresh the page and drag the card.
DE50764: A One-Day Task Created on the Task Board Shows Up as a Milestone on the Timeline
Steps to Reproduce:
  1. Log in to the New User Experience.
  2. Open a project and navigate to Tasks module and open the Board layout.
  3. Create a new task - either by clicking the + button or by clicking on the New Card in any lane.
  4. Name the task and use default values for other options.
  5. Navigate to the Timeline layout.
Expected Results: The newly created task will show up as a Gantt Bar.
Actual Results: The newly created task shows up as a Milestone icon.
DE50663: DETAILS Panel Width Expands When You Edit Fields on the DETAILS panel and Misaligns Column PickerTab
Steps to Reproduce:
  1. Click on grid to open DETAILS panel.
  2. Click on any field with a dropdown.
Expected Results: The DETAILS panel should not expand.
Actual Results: The DETAILS panel will expand.
DE50774: DEFAULT Timeline Monthly Fiscal Period Labels Are Not Showing
When you navigate into any project for the first time and views the Timeline layout, the user expects to see the labels of the Monthly Fiscal Periods of the Default Entity. Currently, the labels are not showing up. If the user changes the view options to Quarters, then back to Months, then the monthly labels now appear only for that project. You would have to do this workaround for each project to get these labels to appear. If the user is on a specific view and then deletes this view, it goes back to the default view and the labels disappear!
Steps to Reproduce:
  1. Log in to the New User Experience.
  2. Open a project and navigate to Tasks module and open the Timelines layout. The timeline area does not show the default monthly fiscal period labels.
  3. Open another project and navigate to Tasks module and open the Timelines layout. The timeline area does not show the default monthly fiscal period labels.
  4. In the second project, change the View Options to 'Quarters', then change back to 'Months' and save the view. This project now has the monthly labels
Expected Results: The timeline area should show the default monthly fiscal period labels.
Actual Results: The timeline area does not show the default monthly fiscal period labels.
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.
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.7.
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.7
To upgrade
directly
to this release (15.7), your current release must be 15.2 or higher. The 15.7 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. First upgrade to 15.2 or a higher version, and then upgrade to 15.7.
  • You cannot upgrade to Release 15.7
    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.7 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 and from 15.6.1 to 15.7.
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.7. After the upgrade, install the latest 15.7 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 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  (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'