Change Impact and Upgrade

Change Impact and Upgrade
page highlights significant changes, required actions, known issues, and recommended options for customers upgrading from the previous release to
. Plan your
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 compatibility related information see, Hardware and Software Compatibility Specifications
For installation and upgrade related information see Installing and Upgrading
For example, you are upgrading from
Release 15.5 to
. Review the changes in releases 15.5, 15.5.1, 15.6, 15.6.1, 15.7, 15.7.1, 15.8, 15.8.1, and 15.9 before and after you upgrade. To switch to the
Change Impact and Upgrade
page for each release, click the
menu at the top of this page. Check back often for updated content, especially if you downloaded a PDF 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
, 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.
15.7 Onward - OracleJDK will be replaced with AdoptOpenJDK
Java Image
With effect from August 19, 2019,
has discontinued product updates related to Oracle Java. 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
that supports AdoptOpenJDK. This change does not impact Jaspersoft, which will continue to support Java 8.
This page includes the following sections:
New Clarity Mobile App 3.1.0
The Clarity 3.1.0 mobile app has been released on the iOS and Android platforms. Project Managers and other stakeholders with the relevant access rights can use the app to review and approve timesheets for three time periods namely previous, current, and next.
While the Clarity 3.1.0 mobile app supports Clarity and higher releases, you can only approve timesheets if you are on Clarity 15.9.2 or higher releases. The Mobile - Approve Time - Navigate access right has been introduced in Clarity 15.9.2 to support the mobile timesheet approval feature.
To learn more about the Clarity 3.1.0 mobile app, see New! Clarity Mobile App Version 3.1.0.
New Clarity Rally Integration

Organizations can use the new and improved Clarity-Rally integration to ensure data flows seamlessly between the two applications.
The new and improved Clarity-Rally integration is:
  • Easily extensible and configurable
    : You can map objects and attributes between Clarity and Rally to ensure the integration meets your specific requirements.
  • Simple to maintain
    : The integration can be set up and maintained by Clarity administrators who have basic Classic PPM knowledge.
  • Validated and Supported by Broadcom
    : You don’t need to perform regression testing after every release.R
Some of the key steps you need to perform the integration are:
  1. Complete the relevant prerequisites to configure the integration.
  2. Create an Integration Object to integrate Clarity with a specific Rally instance.
  3. Create an Integration Mapping.
  4. Run the Import Integration Mapping job, to fetch all Rally portfolio item type objects and their associated attributes.
  5. Define valid Object mappings.
  6. Define valid Field mappings.
  7. Specify a Clarity Investment that would map to an Object in Rally.
  8. Execute the Synchronized Mapped Information job to synchronize data between Clarity and Rally.
  9. Review Clarity’s Staging Table to understand the changes to be pushed from Rally to Clarity.
Upgrade Impact
: Customers can continue to use both the new Rally integration and the Rally Portfolio Item Hierarchy, Investments, or (Clarity) Timesheet integrations if warranted. If a customer has configured an "Agile" integration, there is no impact on that existing integration after the upgrade. The new jobs (e.g., Import Integration Mappings, Synchronize Mapped Information, and Import Staging Tables) are set as incompatible with the old jobs (e.g., Synchronize Agile Central and Create Agile Central Investments) to prevent them from running simultaneously.
Key Points to Remember
  • If the Import Integration Mapping job is not run after creating a new Integration Mappings instance, the Clarity and Rally Objects will not be available in their respective pull downs. If you create new custom attributes (in either Clarity or Rally), the Import Integration Mapping job must be run to ensure they are available in the field mapping grid
  • After the Synchronize Mapped Information job is run, the user will be auto-granted access to the Staging Tables.
  • The Integration Mapping (view, edit, and delete) Global Access rights are automatically added to the PMO System Administrator group. This back-end process enables access to the Staging Tables.
To learn more about the new Clarity-Rally integration, see Clarity Connections - Rally Integrations.
Accessibility Enhancements

The following Clarity components are compliant with the 4 aspects of compliance in the form of Visual, Responsive Design, Keyboard, and Screen Reader support:
  • View Options (Grid)
    • Money & Number decimal display, Per-Period Metrics Periods, Start Period, End Period, Totals Columns
  • Saved Views
    • Manage and Save As
  • Item Action Bar (multi-select grid)
    • Select All, Deselect All, Edit, Mark for Deletion, Clear Deletion
  • Color Picker - Pick List Color
  • Toaster Message
  • Generic Filter
  • Layout Switch (Board, Grid, Timeline)
  • Attachment (Grid)
  • Search
  • Overall Usability improvements
    • Updated People and Action Icons
    • Banner UX Style Updates
    • Column Panel – Expand / Collapse All sections
For more information on the supported components and level of compliance, see Accessibility Features in Clarity.
Upgrade Action:
No action required.
Enhancements to Investments

Using Mixed Bookings on the Staffing Page
Clarity now supports mixed booking in the Staffing Workspace. In many organizations Project Managers (PM) input soft-booked allocations for all the resources required for a given project and its duration. Project Managers are capturing ‘planned’ allocations. Resource managers have a conversation with the PM to gain alignment and then convert planned (soft) allocations to committed (hard) allocations. The conversation typically occurs on a quarterly cadence which results in a mixed booking.  A team member is mixed-booked when the planned allocation and hard allocation are not equal.
You can enable Mixed Bookings in Classic PPM on the Project Management settings page. In the previous releases, the Staffing Workspace was available in read-only mode after you turned on mixed booking. In this release, you will see the Hard Allocations checkbox on the Resource to Investments and Investments to Resources view. To learn more about the Staffing Workspace, see Clarity: Request Resources and Roles to Staff Investments.
Upgrade Action
: No action required. When you upgrade to this release, and you have mixed bookings enabled, you will be able to use the Staffing workspace.
Key Points to Remember:
  • The Telescope functional design has not changed with the introduction of Hard Allocation in the Staffing workspace.
  • Telescope capability continues to use (planned) allocations and does not include (committed) hard allocation information.
Risks Issues and Changes Modules Available for All Investments
In previous releases, you could manage risks, issues, and changes for investments by using two approaches:
  1. You manage Risks directly for each project by using various Risk attributes and calculating a risk score. Ideas and Custom Investment included a Risk field.
  2. You use Risk, Issues, and Changes modules in projects to create a detailed list of risks impacting your projects.
In this release, the following changes have been made to enhance your risk management experience
  1. If you manage risks directly for each investment, you can use a new calculated attribute Risk Score that has been introduced in this release. 11 new contributing attributes have also been introduced (Resource Availability Risk, Supportability Risk, Technical Risk, Sponsorship Risk, Organizational Culture Risk, Objectives Risk, Interdependencies Risk, Implementation Risk, Human Interface Risk, Flexibility Risk, Funding Risk). Since Risk Score is a calculated attribute, you can populate the Risk Score by population any of 11 attributes that contribute to the Risk Score. These attributes are available for all investments.
    The risk attributes associated with the project object have been depreciated. Clarity will synchronize the values between the deprecated attributes and the new attributes for one year before announcing end-of-support for the Risk attribute and the associated contributing factors. Classic PPM Views will continue to use deprecated risk attributes.
  2. If you plan to create a detailed list of risks then you can use the Risks, Issues, and Changes modules for projects, ideas, and custom investments. These modules were previously available only for projects.
  3. New Create, Edit, Delete, and View access rights have been introduced in this release. Administrators will need to add the Risk, Issues, and Changes modules to the blueprint and provide you the relevant access rights to interact with the modules.
Upgrade Impact
: You need to consider the following points while upgrading to this release:
  • After upgrading to Clarity15.9.2, the custom and standard blueprints associated with Idea and Custom Investment automatically include the Risks, Issues, and Changes modules.
    • If you want to hide these modules from the Standard Blueprint (Ideas and Custom Investments), you can leverage the Business Rules functionality.
    • If you want to remove these modules from custom blueprints, you can edit the blueprint and remove them so that they are not visible to the end-user.
  • If you have edited the Risk attribute in your environment to update the formula calculating Risk, your Risk Score, and Risk attributes will show different values in Clarity. Ensure you update the Risk Score attribute to reflect how you calculate Risks in your organization.
  • Administrators will need to provide users the global access rights to view Risk, Issues, and Changes post-upgrade to ensure they can leverage these modules.
Key Points to Remember
  1. RICs Sub-objects (modules) are not available for Classic PPM NPIOs (including Ideas).
  2. Classic PPM NPIOs properties will not be updated.
    1. Customers can configure properties, lists, and filter views, in Classic PPM, if they want to use the new Risk attributes
To learn more about the Risk, Issues, and Changes, see, Clarity: Manage Risks, Issues, and Changes for Projects.
New Scrolling Widget and Enhanced Options for Viewing Totals
You will see a scrolling per-period metrics widget on the Staffing module. You can click front and back arrows on the widget to quickly cycle through the data for various periods. Your Start Period and End Period settings will update the widget and as you cycle through periods in your widget, the Start Period and End Period will also be updated. You can also define if you want to see Sum of Periods or Grand Totals in the Totals column. If you select Grand Totals, Clarity will continue to display the Totals for the entire duration of your investment even when you cycle through various periods by using the widget.
  • Sum of Period displays the Total (e.g., allocation) for the number of periods in the grid (configured via View Options).
    • Example – If an Investment has a duration of 12 months; the grid is configured to display 6 months; Sum of Periods is selected – the Totals column will sum up the (e.g., allocation) 6 months displayed in the grid.
    • With Sum of Periods selected, the Totals field is editable.
  • Grand Total displays the Total (e.g., allocation) for the duration of the Investment regardless of how many periods are displayed in the grid (configured via View Options).
    • Example – If an Investment has a duration of 12 months; the grid is configured display 6 months; Grand Totals is selected – the Totals column will sum up the (e.g., allocation) for the 12 months of the investment
    • With Grand Total selected, the Totals field is not editable with periods in view
The scrolling per-period metrics widget will not be displayed until the user has selected at least one Per-Period Metrics in View Options.
Upgrade Impact
: No Impact. You will see the new widget on all the grids where per-period metrics are supported.
New Timeline Layout for the Tasks Module
You can use the new and enhanced Timeline layout to create and manage tasks. The Timeline layout is divided into a Work Breakdown Structure (WBS) on the left and a task timeline on the right. Both the WBS and the task timeline show you all the sub-level tasks associated with the selected project/investment item. Some key enhancements made to the timeline are:
  • You can use the COLUMNS tab to add fields to the WBS section.
  • The summary bars are shaded based on the completion of tasks associated with it.
Upgrade Impact
: In the previous release, the Timeline layout displayed fiscal periods. In this release, the Timeline layout supports Calendar periods. Hence, when you upgrade, existing tasks will be displayed in Calendar periods on the Timeline layout.
Key Points to Remember
  • The Timeline includes the WBS column as a fixed column that cannot be hidden or moved to another column position in the grid.
    • There is another attribute “WBS Sort’ which users can optionally add as a column in the table with the timeline in view – and save the configuration in a View
  • Within the Timeline, the "% Complete" progress bar is displayed for all tasks, including summary Tasks
    • The color of a Timeline bar is driven by Task Status
    • The “shading” of a Timeline bar is driven by Task % Complete
To learn more about the Timeline layout, see Clarity: Project Phases, Milestones, Tasks, and To-Do Items.
Mark Investments for Deletion
You can now mark an investment (Project, Idea, Custom Investment) for deletion in Clarity by using the Mark for Deletion action button. When you mark an investment for deletion, Clarity sets the Purge Flag field. The relevant stakeholders can now review all the investments that are marked for deletion. Once they are satisfied, they can run the Delete Investments and Time Reporting Period job to delete the relevant investments.
Before you mark an investment for deletion ensure that:
  • The financial status of the investment is set to Closed to prevent new transactions.
  • The investment status is set to Inactive.
  • No process instances are currently running on the investment.
You need to have the <investment> - Delete - All global access right and “Edit” access rights for investments that you want to mark for deletion. The following access rights have been introduced in this release to facilitate the deletion of investments from Clarity.
  • <Custom Investment> - Delete - All
  • Idea - Delete - All
The Mark for Deletion option is specific to Clarity. This functionality does not impact the Mark for Deletion option in Classic PPM.
Key Points to Remember
  • Any user with 'Delete – All (Global)' and 'Edit' access for Custom Investments, Ideas, or Projects, will have the ability to use the Mark for Deletion option.
  • When the 'Delete Investments and Time Reporting Periods' job is run, the system will delete the investment and all related data.
  • If an Investment has timesheet actuals and the
    Project Management
    llow Marked Investments with Timesheet and Transaction Data to be Deleted
    checkbox is NOT selected, you will see a message indicating that the investment cannot be marked for deletion.
To learn more about deleting investments, see Close, Deactivate, and Delete Projects and Investments.
Upgrade Impact
: No Impact. After you upgrade to this release, you will be able to mark investments for deletion.
Enhancements to Roadmaps

The Roadmaps functionality has been enhanced to leverage the Board, Grid, and Timeline layouts utilized throughout Clarity. Roadmaps leverage the Clarity common grid to ensure you can use functionality like filter, search, saved views, DETAILS panel, support for custom attributes, and export to CSV. The Board view now allows the user to configure additional content to be displayed on the Board Card and save the information to a view. The Timeline view layout now includes the DETAILS panel which allows you to easily edit roadmap items.
Upgrade Impact
: Some key points to remember when you upgrade to this release are:
  • Users can select their own Start Period and End Period by using View Options. This will help them view roadmap items beyond the duration of the roadmap.
  • The Scenario comparison option is not available in this release.
  • The search option has been enhanced so that you can locate any attribute associated with roadmap items.
  • All three layouts include the DETAILS layout to help users edit roadmap items.
  • You can select calculated number attributes as metrics in the Timeline layout and as Targets in the Grid.
  • Clarity roadmaps now support TSVs.
  • The Roadmaps grid has been enhanced to display per-period metrics.
  • Users cannot search or configure TSV’s in the DETAILS panel
  • Roadmaps now support Global Settings (Hours, Days, FTE). The only exception is when you specify a target. Since that value you define is not an attribute in Clarity, it will not automatically be updated based on your setting.
To learn more about roadmaps, see Clarity: Top-Down Planning with Roadmaps.
Key Points to Remember
  • Large String - Rich Text attributes will now synchronize to Roadmap Items from linked Investments
  • The Roadmap grid now includes the Add Row icon enabling users to create Roadmaps with required fields.
  • The New Roadmap pop-over does not support the “required field” flow. If you attempt to create a new Roadmap that has required fields, and the required fields are not visible in the New Roadmap pop-over, the user will not be able to create a new Roadmap and is presented with a toaster message. Users can use the Add Row icon to create a new Roadmap in order to populate required fields.
Expanding the Capability of To Do's

Clarity allows you to create to-do items for a phase, a milestone, for a task to break down the work into smaller activities. The new To Dos page displays all the To Dos assigned to you across various investment types in Clarity.
Clarity has introduced the following global access rights in this release:
  • To Do - Navigate
  • To Do - Create - All
  • To Do - Delete - All
  • To Do - Edit - All
  • To Do - View - All
These access rights are assigned to the Viewer license type in Clarity.
Upgrade Impact
: After upgrading to this release of Clarity, you will need to assign users the appropriate To Do access rights.
  • In previous versions, users did not need any additional rights to access To Dos. After you upgrade, you will need to assign the relevant To Do global create, delete, edit and view access rights to users. This will ensure users can access To Dos, in the Tasks details panel, without experiencing any errors.
  • To have users access the new To Do workspace you will need to assign the To Do - Navigate access right along with the other new To Do global rights.
  • The To Do's Scorecard has been deprecated and is not available in this release.
Key Points to Remember:
  • To Dos are implemented as a Studio Object but cannot be leveraged in Classic PPM.
  • The To Dos Object is not enabled for use with BPM processes.
  • The Data Warehouse uses the new To Dos tables.
  • To Dos stock attributes are Name, ID, Owner, Due Date, and Completed
    • The To Dos ID field supports auto-numbering
    • To Dos do not support the ability to create Sub-Objects.
  • The To Dos Due Date has no limitations and can fall outside of an investment's Start and Finish Dates.
  • When a To Dos is copied over from a template, Clarity populates the To Dos Due Date with whatever is in the Due Date field (e.g., blank or actual) prior to copy.
To learn more about the new To Do's page, see Clarity: Track and Edit To Dos
Business Rules for Investments and Custom Master Objects

Administrators can create business rules Clarity Blueprints to control the modules or sections displayed to end-users. Let’s consider an example where the administrator wants to show the Executive Summary section on the Properties module only when the following conditions are met:
  • The user is a member of the PMO portfolio manager group The
  • ROI is greater than 200%
  • The Corporate Priority is high
  • The project is active
In such scenarios, administrators can leverage business rules to achieve this outcome.
When you create a business rule, you define:
  • Conditions
  • Actions
  • Action Targets
Upgrade Impact
: No Impact. You can start using the Business Rules functionality after upgrading to this release.
Key Points to Remember
  • Business rules are not a replacement for security rights.
  • Attributes hidden, as part of rules hiding sections, can still be viewed in the object grid view.
  • Business rules do not control the “Detail” fly-out display as those are defined by individual users.
  • Rules will not be applied to the blueprint till they are enabled.
  • Rules are part of the blueprint and cannot be moved between environments as they do not have blueprint API or XOG support.
  • If the rule does not have at least one condition and one action defined, the rule cannot be enabled.
  • Incomplete rules can be saved but not enabled.
  • Rules cannot use the attachment, RTF, Money, and URL attributes for conditions.
  • If a section or module used in a rule is deleted, and that rule only had an action related to that section or module, then the rule will automatically be disabled if you open the rule
To learn about business rules, see Clarity: Configure Blueprints for Projects.
Customer Requested Enhancements

Inactive Departments Hidden from OBS and Department Lookups
Classic PPM now has the Active attribute with the Department OBS. In certain scenarios, where your organization changes its departments, you can set clear the Active checkbox associated with the department to hide it in Classic PPM and Clarity. You can still see the inactive departments for existing investments. However, when you browse to select a new OBS, the inactive departments will not be available.
Upgrade Impact
: After upgrade to Clarity 15.9.2, all existing departments will have their “Active” flag set to true. You can then clear the Active flag associated with departments you want to hide. Also, te new “Active” flag in departments is added to the object but not to the views. After upgrade customers will need to manually add that flag to their “Department Properties” and “Department List” views before setting the value.
Key Points to Remember:
  • Setting the new flag controls if the department will be displayed in the following lookups:
    • Department Lookup
    • Department OBS
    • Department
    • Resource OBS
    • Staffing Workspace
    • Staff OBS Unit in Project Staff Module
  • Department XOG has been updated to use the new “Active” flag
  • Deactivated departments will still be displayed where they were populated.
  • The deactivated department cannot be set for existing or new object instances.
Multi-Select Update Available for Grid Layout
You can edit multiple records on the Grid layout. When you select multiple records and click the Edit button, a bulk edit window will be displayed. The window includes all the fields that were displayed in the grid. You can update the relevant fields and click Save to commit your changes. In case, certain fields cannot be updated due to internal business rules, those changes would be ignored.
  • Attachment fields cannot be changed during bulk edit.
  • The starred fields cannot be edited by using bulk edit.
  • If the grid has Group-By mode enabled, the multi-select bulk edit mode is not enabled.
  • The Attribute grid used to configure field-level security does not support the multi-select feature.
Upgrade Impact:
No impact. You can upgrade to this release and start using the Bulk Edit capability.
To learn more about Clarity grids, see Common Components
Links Module Available for Ideas
The Links Module is now available for Ideas. Users can now add links to the idea or create a new category and add links specific to that category. To learn more about editing blueprints for ideas, see Clarity: Configure Blueprints for Ideas.
Upgrade Impact
: When you upgrade to the latest release, the Standard and custom blueprints will automatically include the Links module. The Links module in Ideas works exactly the same as “Custom Investment Type” links and does not support any parameters.
  • If you want to hide this module from the Standard Blueprint for Ideas, you can leverage the Business Rules functionality.
  • If you want to remove the module from custom blueprints, you can edit the blueprint and remove the module so that it is not visible to the end-user
Delete Permissions Separated from Edit Permissions
You can now segregate delete permissions from edit permissions. Every object now has the following new rights available:
  • Global Delete All
  • OBS Delete
  • Instance Delete
Now when a user creates a new object instance, they will not be able to delete it without the delete access rights.
Upgrade Impact
: When you upgrade to the latest release, Clarity will grant delete rights to all users who currently have edit rights to an object. When you grant a user the delete right, Clarity will not give users view or edit permissions.
API Alias Attribute Added to the Field-Level Security Grid
Customers wanted more information about attributes when enabling field-level security. Error message in Clarity displays API attribute ID which could only be seen in Classic PPM.
Attributes only showed “Attribute ID” which is not the same as the API ID assigned to the attribute. From Clarity 15.9.2 onwards, customers can easily view and configure field-level security based on API attribute ID.
Upgrade Impact
: No impact. When you upgrade to the latest release of Clarity, you will be able to see API Attribute ID on the Attributes grid.
Create Project from Template

Clarity has introduced the ability to define the create screen when creating a project from a template. This will force users to populate required fields when creating a project from a template. A new “Create from Template" configuration module has been added to the “Project” blueprint. Every project blueprint will have the ability to define which fields are displayed to the user when they create a new project using that blueprint.
When you convert an idea to a project, Clarity will now use the new “Create from Template” modal based on the blueprint assigned to the selected template. Three additional options are displayed to copy team, financials, or Risks, Issues, and Changes.
Upgrade Impact
: No impact. This feature will be available to you when you upgrade to the Clarity 15.9.2 release.
Key Points to Remember:
  • Any studio-defined required fields, not included in the “Create from Template”, will automatically be added to the create modal if the attribute does not have a default value. Attributes will be displayed alphabetically based on the name.
  • Required fields will have default value populated in the create screen based on the following logic:
    1. Value from the project template
    2. If the template does not have value populated then display the value from the studio definition
    3. Display null value if no value is found in the template or studio.
Data Warehouse Enhancements

Data warehouse and Reports Include New Functionality Offered by Roadmaps
The Data warehouse table dwh_rdm_item_position has been renamed to dwh_rdm_picklist_position. The dwh_rdm_item_position name will not be available. All the other Data warehouse tables for roadmaps will remain the same.
In the Roadmap report, the Swimlane and the Color By input controls now include custom attributes. The list and the board options in Clarity are also included. The previous default items namely Type, Status, and In Plan are now available by default. However, you can still select them in Board Options if needed.
Add Picklists Available in Investments for Data Warehouse
The DWH_INV_PICKLIST table is now a lookup table for picklists. The object_code_key column includes the investment associated with the picklist. DWH_INV_PICKLIST_POSITION table carries the investment association.
Risks, Issues, and Changes (RICs) are Captured at Investment Level
All the investment objects in Clarity (Projects, Ideas, Custom Investments) now support Risk, Issues, and Changes. To help drive this change, Clarity now includes a new calculated attribute Risk Score in this release. The Risk attribute is still available and continues to be a Formula attribute. However, when customers update the RICs, Clarity will now use the Risk Score attribute when it saves the information in the Data warehouse.
The Risk Attribute has been replaced with the Risk Score attribute in all existing project management reports. Clarity also has a new view to help existing customers adopt the Risk Score attribute.
The following new reports have been created to help report developers capture RICs for all investments:
  • Investment Risk Register
  • Investment Issue Register
  • Investment Change Request Register
  • Investment Risk, Issue, and Change Summary
Upgrade Impact
: The Risk attribute is still available in the PMO accelerator. Customers using in attribute in Classic PPM can continue to do so in this release. If customers want to start using the Risk Score attribute, they can upgrade the PMO accelerator. New customers will use the Risk Score attribute.
Tables to Store To Dos Updated in the Data Warehouse
In previous releases, Clarity used the dwh_inv_todo table to store all the information about To-Dos. In Clarity 15.9.2 and higher releases the dwh_cmn_todo table stores all the To-Dos. The assoc_object_key is used to link to the parent. When you run the Data warehouse and if you have any To-Do items that need to be translated, Clarity will create the dwh_cmn_todo_In table.
Customers can use the dwh_inv_task_v view for tasks.
Upgrade Impact
: When you upgrade to this release of Clarity, all the information in the dwh_inv_todo table would be copied to the dwh_cmn_todo table. The dwh_inv_todo table will not be deprecated but will not store any information.
Enhancements to Hierarchies

The BETA tag is no longer applicable to Hierarchies. The following features have been added to this release:
OBS Security Added to Hierarchies
Hierarchies now support OBS security. You can associate a hierarchy with an OBS to ensure you take advantage of the existing OBS framework when assigning rights for the hierarchy. To learn more about hierarchies, see Clarity: Create and Edit Hierarchies.
Upgrade Impact
: When you upgrade to this release, Clarity will automatically
delete all existing saved views for hierarchies
Configure Blueprints with Channels for Hierarchies
As an application administrator or PMO content designer, you can use blueprints to configure layouts for hierarchies. You can copy and configure blueprints that reflect the goals of each business unit in your organization. Let's consider an example where multiple product management teams in the organization are using hierarchies to achieve different business outcomes. They have created multiple custom attributes. Some attributes are relevant to the New Banking Application Product Management team while others are relevant to the Next-Gen AI team. The administrator can create different blueprints for these teams so each team would only see information relevant to them.
In this release, the Hierarchies blueprint includes the Investments and the Properties modules. Both modules will automatically be included in your blueprint. You can also create channels to embed content from another source, such as an external site, application, or Classic PPM context-sensitive investment reports into hierarchies.
To learn more about blueprints, see Clarity: Hierarchy Blueprints.
Upgrade Impact
: When you upgrade to this release, Clarity will automatically
delete all existing saved views for hierarchies
Assign Different Colors to Various Investment Types
In previous releases of Clarity, you could select a single custom or stock lookup attribute to select the color of all investment cards in the hierarchy. In this release of Clarity, you can select different attributes for different investment types that are available in your hierarchy. You can select fields from both the abstract investment object and the concrete objects (projects, ideas, and custom investments). To learn more about setting colors for investment cards, see Clarity: Create and Edit Hierarchies.
Upgrade Impact
: You can now color investment cards based on different attributes for different investments. In previous releases, you could select a single custom or stock lookup attribute to select the color of all investment cards in the hierarchy. When you upgrade to this release, Clarity will automatically
delete all existing saved views for hierarchies
Import Child Cards Directly from Parent Card
You can select an investment card, right-click, and use the Import Children option to import multiple investments as children. To learn more about importing investments in hierarchies, see Clarity: Create and Edit Hierarchies.
Upgrade Impact
: When you upgrade to this release, Clarity will automatically
delete all existing saved views for hierarchies
Configure Hierarchy Cards and Metrics Using Project, Idea, and Custom Investment Fields
In the previous release, fields that were a part of the abstract investment object were available for selection in hierarchies. In this release, you can select fields associated with the concrete investment object (project, ideas, custom investments) to displayed on investment cards. You can also use the various metrics available with concrete investment objects to create custom metrics for Hierarchies. To learn more about setting metrics for investment cards, see Clarity: Create and Edit Hierarchies.
Upgrade Impact
: When you upgrade to this release, Clarity will automatically
delete all existing saved views for hierarchies
Enhancements to Custom Metrics
There have been multiple updates made to custom metrics for Hierarchies.
  • In previous releases of Clarity, you could not view the calculations of custom metrics after you created them. In this release, you can click the Edit icon associated with a metric to view its definition.
  • You can only create or delete a custom metric only when you have the Hierarchy - Manage Metrics global right. If you don’t have this access right, you will see an error message when you try to access the MANAGE METRICS dialog.
  • The Aggregation and Calculation metrics are now available in two separate tabs to provide a better user experience.
  • The custom metrics are now available under the Hierarchical category in the filter on the cross-object grid. The metrics are also available in the Column picker under the Hierarchical category in the Cross-Object grid.
Upgrade Impact
: Hierarchy users will lose their ability to create hierarchy metrics that they previously had unless they have the "Hierarchy - Manage Metrics" access right. Also, when you upgrade to this release, Clarity will automatically
delete all existing saved views for hierarchies
To learn more about custom metrics, see Clarity: Create and Edit Hierarchies.
Analyze Hierarchies By Using the Cross-Object Investment Grid
The Cross-Object Investment Grid for hierarchies includes two key updates:
  • The Parent and Level columns are available in the Hierarchies gird. You can add these columns to the grid to see how the investments are related to each other.
  • You can view the custom metrics in the cross-object investment grid. In the previous release, custom metrics were only visible in the Manage Metrics window on the Hierarchy tab.
To learn about the Cross-Object Investment Grid, see Clarity: Create and Edit Hierarchies.
Upgrade Impact
: When you upgrade to this release, Clarity will automatically
delete all existing saved views for hierarchies
Applying Field-Level Security for Hierarchies
You now have the following capabilities for using field-level security with hierarchies.
  • Field-level security is now applicable in hierarchies.
  • You can now secure fields associated with the hierarchy object by using the Field Level Security grid
  • You can secure attributes associated with the abstract financial object. Consider a scenario where you want to secure the Planned Cost attribute. Since this attribute is available for the abstract financial object and concrete investment object (Project, Ideas, Custom Investments), you need to:
    • Secure it as the abstract investment object level (Investment Abstract object and Financial Abstract object)
    • Secure it for individual concrete investment objects (Projects, Ideas, Custom Investments)
      If you secure Planned Cost for the abstract financial object and projects but don't secure it for ideas, you will see the Planned Cost for ideas in the cross-object grid in hierarchies.
Field-level security does not apply to custom metrics. If you secure the planned cost field and then create an aggregation metric named Aggregated Planned Cost, the aggregation metric cannot be secured by using field-level security.
To learn about the Cross-Object Investment Grid, see Clarity: Create and Edit Hierarchies.
Upgrade Impact
: When you upgrade to this release, Clarity will automatically
delete all existing saved views for hierarchies
Display Messages When Users Log Into Clarity

Administrators can now display messages to users when they log into Clarity. Administrators can use the System Settings section on the Administration page to configure the message and associated settings.
To learn more see, Clarity: System Settings.
Upgrade Impact
: No impact. You can start using this feature after you upgrade to Clarity 15.9.2.
Key Points to Remember
  • The Login message will not appear if users are using SSO to log into Clarity.
  • Clarity does not support multiple languages for the login message.
Introducing Pages

Administrators can now define a collection of pages in Clarity. It provides a single place to access desired Clarity or external application pages without being inside an object instance. This allows customers to leverage the Channel functionality outside the object instance. Administrators can define blueprints for pages.
To learn more about pages, see Clarity: Working with Pages and Clarity: Pages Blueprints.
Key Points to Remember:
  • Classic PPM includes the new studio object called “Page”.
    • Includes Instance, Global, and OBS access rights
  • Attributes in Page can be secured using Field Level Security.
  • Pages cannot be seen in Classic PPM.
  • You cannot define sub-objects for the Page object
  • Channels within a blueprint are limited to the same governor limit of 15.
  • In Classic PPM the “Page” object has the event enable flag. This is standard object configuration, but processes will not be supported with the Page object.
  • When setting security you will see two “Page” objects listed. One refers to the Classic PPM portlet page, and the other to the Clarity page. The description for the Clarity page will list “new user experience”.
Upgrade Impact:
Administrators need to assign the Page – Navigate access right to users so that they can leverage this functionality.
Internet Explorer 11 Not Supported for
Classic PPM
still supports IE 11; however,
cannot extend backward compatibility with any old browser technology, including IE 11.
This is not a known issue with
. 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 following problems could occur:
  • Defective features or memory leaks (with no scheduled fixes from Microsoft)
  • Missing browser framework support for new REST API capabilities
  • Poor appearance or slow performance with HTML 5 and new Angular components
  • Links to other sites stop working or show messages indicating you need to update your browser
For example, using IE 11, you could cause your roadmap timeline to stop working, the staffing pages might not load all resources, and other problems could occur that appear to be
until users realize they are using old unsupported browser technology to access a completely new drag-and-drop feature-rich web application interface. For best results when viewing the modern user experience pages in
, switch to a new browser such as Edge, Firefox, or Chrome.
JAXEN Enhancements in Clarity
Clarity 15.9.2 and higher releases include the JAXEN 1.2.0 library. This has impacted the syntax for certain GEL scripts. Read the following Knowledge Base article for more information.
Telemetry Enhancements
Telemetry is a capability that is integrated into
to send product usage and system configuration data to Broadcom. This data helps Broadcom gain insights into customers' product usage, understand their software needs, and focus on the features and platforms that are most commonly used. Telemetry DOES NOT collect any personally identifiable information (PII).
The Opt-In capability is no longer available when you configure the Subscription Compliance Setup section in the General System Settings.
will send telemetry data to Broadcom for all your
production servers. To learn more about the Telemetry capability, see Configure General System Settings
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.
Microsoft Project Integration Upgrade Details
You should uninstall and upgrade your
Microsoft Project Integration software using the version available after upgrading
in Account Settings-> Software Downloads. Note that the Microsoft Project Interface bit level installed should match that of Microsoft Project. Microsoft Project Interface (x86) should be installed for 32 bit versions of Microsoft Project and Microsoft Project Interface (x64) version should be installed for 64 bit versions of Microsoft Project.
Updated Logout Behaviour for SAML Users
In previous releases,
would redirect users to the errorURL when it receives SAML request that it could not process. In
15.9 and higher releases,
redirects users to the logout URL when it receives a valid SAML request with the following issues:
  • Clarity
    cannot find the user in its user store or
  •   The user is inactive in
Users that use Spanish (Peru) locale will now have the period symbol as a decimal separator.
: Users that use the "Spanish (Peru)" locale will now have the period "." symbol as the decimal separator instead of the comma "," symbol.
: 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:
As a result, a user might see a raw text label or English text in the user interface instead of the translated text.
: Switch your
account settings to one of the supported languages listed in the Release Notes.
help will be available only in English for a couple of months after release. The Help link in
Classic PPM
will automatically redirect you to the English site. The help link in
currently defaults to the localized site and displays a blank page since the content is not localized. Broadcom will fix this issue in future releases.
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).
: 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=
[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
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:
Classic PPM
  • Data Warehouse Configured
  • Load Data Warehouse Job Completed
  • PMO Accelerator Add-in Installed
Install PMO or APM add-ins
  • Data Warehouse Configured
Supported Upgrade Paths for Clarity
Please review the table to identify the minimum supported release from which you can upgrade to the latest version of
Clarity Version
Minimum Supported Version for Direct Upgrade
  • If you have Release 14.3 or older, your release is no longer supported. Upgrade to Release 15.4 first, and then upgrade to
  • You cannot upgrade to Release
    from Release 14.2 with Jaspersoft 5.6.1 or from Release 14.3 with Jaspersoft 6.1.0. The Jaspersoft 6.4.2 or 7.1 upgrade does not support those configurations. Your
    upgrade is still supported. For example, upgrade to 14.3 and Jaspersoft 6.4.2 first. Then upgrade to 15.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, from 15.7 to 15.7.1, from 15.7.1 to 15.8, from 15.8 to 15.8.1, and from 15.8.1 to
If you have installed any patches on the base version, verify that you applied the latest supported cumulative patch before and after you upgrade. Patch maintenance before and after upgrades is important for troubleshooting, security fixes, and general system health.
Follow these steps
  1. Select your current release from the
    menu at the top right of that help page.
    For example, select 15.1 and verify you installed the patch or select 15.3 and verify that you installed the patch before starting your upgrade to 15.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
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
    installer to the
    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:
    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
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
, 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
Upgrade Action
: Retrieve the
file from the installation media. Place the file in a location in your file system so that it is accessible to the installer.
: 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
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
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
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
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 a 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
  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,
provided the functionality with no net loss to end-users. We recommend that you perform an analysis comparing the value of
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
directory using ant-based scripting. Use ant scripts to automate preserving and restoring customization in
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:
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 = ${}</echo> <if fileexists="${}" not="true"> <fail>Install dir not specified = ${}</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="${}"> <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
  • For systems using Oracle 12c R1 (, no further action is required.
  • For systems using Oracle 12c R2 (, you can optimize performance by setting the optimizer to 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:
  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='' *.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='' *.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'