CA PPM 15.4.1 Change Impact and Upgrade

This page highlights significant changes, required actions, and recommended options for upgrades to Release 15.4.1. Plan your cappm upgrade and determine the options that fit your business needs. As an administrator, use this information to plan your training and roll-out efforts. 
ccppmod1541
This page highlights significant changes, required actions, and recommended options for upgrades to Release 15.4.1. Plan your 
Clarity PPM
 upgrade and determine the options that fit your business needs. As an administrator, use this information to plan your training and roll-out efforts. 
 Before upgrading from an earlier release, review this page for all subsequent releases. For example, you are upgrading from Release 14.4 to 15.4.1. Review the changes in releases 15.1, 15.2, 15.3, 15.4, and 15.4.1. To switch to the 
Change Impact and Upgrade
 page for another release, click the 
Versions
 menu at the top of this page. The English edition of this documentation is periodically updated with new information.
 
2
 
 
HID_HID_release_info_change_impact_od
 
HID_release_info_change_impact_op
To prepare for an upgrade to 
Clarity PPM
 Release 15.4.1, review the supported upgrade paths, features, enhancements, and required upgrade actions. The following information summarizes how the new changes introduced in this release impact your upgrade experience to 
Clarity PPM
 Release 15.4.1.
 
Release 15.4.1 Enhancements
: In addition to all the new features and enhancements introduced in the CA PPM 15.4.0.0 base version, the 15.4.1 service pack includes the following updates:
Roadmap Enhancements
  • Roadmaps now support the dynamic selection of multiple targets.
  • You can compare scenarios in the timeline to decide the best course of action for a roadmap.
  • You can import projects as roadmap items. You can also link roadmap items to projects in the roadmap grid.
  • You can also link roadmap items to projects in the roadmap grid with new Linked To and Linked To ID fields. Users with rights can click the project name in the Linked To field to open the linked project from the roadmap grid. A link from a roadmap item to its linked project is also available on the roadmap timeline and board views.
  • The following new attributes are now available for configuration in the roadmap grid. The attributes show dependencies between roadmap items and are read-only in the grid. You can edit the attributes in the timeline.
    • Predecessors
    • Successors
New Project Staff Page
As a resource manager or administrator, you can define project staff by adding resources as team members in the 
New User Experience
. This new resource management staffing feature includes a new Staff module in the project blueprint that includes a new Staff page for an open project. You can use the new Staff page to define project teams and staff teams with resources and roles.
As a result of this staffing enhancement, you can now perform the following activities:
  • Configure a blueprint visual for % Complete to show this standard metric as a new ring chart on project tiles.
  • Define default allocation and allocation dates on the new project Staff page.
  • Change General Settings to display staff data in FTE or hours.
 
Upgrade Action 1
: After upgrade, administrators can see the new Staff module in the Standard Project blueprint. Any existing user-defined blueprints are not affected by the upgrade. Administrators can edit their blueprints to add the new Staff module. See New User Experience: Configure Project Blueprints.
 
Upgrade Action 2: 
Staffing features include the Staffing (formerly Resource Management) page and the new project-specific Staff page.
 
Before using the new Staffing features, run the following two jobs: 
  •  
    Convert Mixed Booking Status
    : The 
    mixed
     booking status available in classic PPM is not supported in the 
    New User Experience
     Staffing features. This job converts project team allocations with 
    mixed
     booking status to 
    hard
     or 
    soft
    . After all mixed booking allocations are converted, the Allow Mixed Booking option in the Project Management administration settings is disabled. 
  •  
    Populate Resource Management Curves
    : This job populates the time-scaled value fields on the resource management views on the Staffing page. 
    By default, these jobs are inactive. After the upgrade, activate and then run these two jobs. One time is sufficient. If you do not run the Populate Resource Management Curves job after completing an upgrade, no data appears in the resource management views on the Staffing page or on the new project Staff page.
Enhanced Tasks Page
The MyTasks feature introduced in 15.4.0 has been enhanced in 15.4.1. The new Tasks menu item and Tasks page also support the needs of project managers. A team member sees their own assigned tasks (
my tasks
) from one or more assigned investments. A project manager or other authorized user sees all tasks from all their authorized investments, including the tasks of their team members.
 
Upgrade Action
: Grant the 
Tasks - Navigate
 access right to users who want to navigate to this new page. The access right is included in the following PMO Accelerator access groups:
  • PMO Executive Viewer
  • PMO Executive Viewer Extended
  • PMO Financial Administrator
  • PMO Idea Creator
  • PMO Idea Reviewer
  • PMO Investment Creator
  • PMO Investment Viewer Extended
  • PMO Portfolio Manager
  • PMO Program Manager
  • PMO Project Creator
  • PMO Project Manager
  • PMO Project Manager Extended
  • PMO Project Viewer
  • PMO Resource Manager
  • PMO Resource Manager Extended
  • PMO Team Member
  • PMO Vendor Management
  • PMO System Administrator
Mention Teams in Conversations About Risks, Issues, or Changes 
On the project Risks, Issues, and Changes tabs, you can now use @mention for teams in conversations.
Attribute Label Change from Business Owner to Sponsor
For consistency between Classic CA PPM and the New User Experience, the 
Business Owner
 label has been renamed to 
Sponsor
. The attribute label change was made to the Project and Idea objects and everywhere instances of this attribute appear. Updates were made in the PMO Accelerator and APM add-in. Impacted views, blueprints, queries, lookups, portlets, processes, and PMO and Jaspersoft reports have all been updated.
New Filters for Timesheets and Approvals
  • On the Review & Approve page, you can now filter timesheets by Resource, Resource Manager, and Resource OBS.
  • On the Timesheets page, the filter columns are now column headings. Also, filters are available for Resource, Resource Manager, Resource OBS, and Status.
  • A new filter option, OPEN FOR TIME ENTRY is available on the Add Work page. You can filter the tasks that are open for time entry. The default value for the filter is 
    ALL
    .
Notifications and Direct Links to Specific Timesheets
Notification email generated in Classic CA PPM now includes direct links to timesheets in the New User Experience. The new links open the timesheet for a specific named resource and for a specific time period. This feature applies to the following scenarios:
  • When a resource submits a timesheet, the notification email to the approver contains a direct link to the submitted timesheet. The approver can open the resource timesheet directly from the email and then approve, return, or edit the timesheet.
  • If the approver returns a timesheet, the notification email to the submitter contains a direct link to the submitted and returned timesheet. The resource can open the timesheet directly from the email and then edit and resubmit the timesheet.
  • The reminder email to submit a timesheet contains a direct link to the timesheet that is due for approval. The resource can open the delayed timesheet directly from the email and submit it for approval.
Administrators and Studio developers can create their own portlets in Classic PPM with these new links to offer their teams more precision and time-savings.
In previous releases, the timesheet notifications for the 
New User Experience
 linked resource managers and users to the parent timesheet or review page. The user had to specify the time period and managers had to specify both the time period and resource.
 
Upgrade Action
: To use the new links in your classic PPM portlets, apply the following structure to your links:
http://<server:port>/pm/#/timesheets/timesheet?timesheetId=<timesheet_ID>&resourceId=<resource_ID>&timeperiodId=<period_ID>
For example:
http://ourPPMserver:8080/pm/#timesheets/timesheet?timesheetId=5000200&resourceId=5003004&timeperiodId=5000101
Users can click these links inside portlets, in email notifications, or copy and paste them in a browser. With sufficient access rights, they can view the target timesheet directly.
  • A project team member typically can view only their own timesheet on the My Timesheets page.
  • For resource managers with approval rights, or for delegates who can enter time for others, the same page appears as the Timesheets page.
New Timesheet Options
The following timesheet options are available in classic PPM under 
Administration
Timesheet Options 
to support time entry in the 
New User Experience
:
  •  
    Allow Entry of Line Item Totals
     allows users to enter one total time value at the task level. The total value is distributed evenly across the work days of the time period.
Advanced Reporting and Data Warehouse Enhancements
Jaspersoft reports with date filters now support relative date filters when you run or schedule reports from the Options pane on the Advanced Reporting page in classic PPM. For example, if you want a report to show data from the most recent complete calendar month, enter 
MONTH−1
. To plan ahead and specify a report Start Date two weeks into the future, enter 
WEEK+2
.
The following image shows valid absolute and relative Start Date filter values:
 image2018-7-7 12:36:31.png 
Supported relative date parameters include DAY, WEEK, MONTH, QUARTER, SEMI, and YEAR.
This enhancement applies to the following default reports:
 
Financial Management:
- Investment Transaction Inquiry
 
Investment Management
:
- Investment Allocations and Assignments
- Investment Assignments by Task
- Investment Baseline vs. Plan by Task
- Product or Application Roadmap
 
Program Management
:
- Program Milestone Dependencies
 
Project Management
:
- Project Portfolio Summary
- Project Planning Schedule
- Project Schedule
- Project Status Summary
- Project Storyboard
- Project Task Dependencies
- Project or Program Roadmap
 
Resource Management
:
- Capacity vs. Allocation by OBS
- Capacity vs. Booking Status by OBS
- Capacity vs. Demand by Resource
- Capacity vs. Demand by Role
- Over/Under Allocation by Resource
- Over/Under Allocation by Role
- Resource Allocations and Assignments
- Resource Assignments by Task
- Resource Availability
- Resource Baseline vs. Plan by Employment Type
- Resource Forecasted Utilization
- Resource Forecasted Utilization Detail
- Resource Skills and Remaining Capacity
- Resource Skills and Remaining Capacity Detail
Enhanced Trending Data Synchronization
The 15.4.1 service pack resolves a specific type of migration troubleshooting issue where the PPM database is restored and the data warehouse schema is blank. A dependency on the existence of trending data has been removed. This enhancement applies to both Oracle and MS SQL databases.
  • The PPM trending metadata is always in sync with the data warehouse metadata.
  • Trending job failures no longer occur due to an out-of-sync condition.
  • This enhancement preserves data accuracy for PPM trending and the data warehouse.
 
Upgrade Action
: No action is required. However, make a backup of any trending data that you want to preserve and restore later. In troubleshooting situations with CA Support, the following optional new stored procedure is available to run from the data warehouse:
DWH_TRD_CLEANUP_TRENDS_SP (DBLINK)
DBLINK is the only parameter. This stored procedure performs the following actions:
  • Drops all trending tables that were dynamically created.
  • Resets the PPM and data warehouse trending metadata tables (sets the processing flag to 0 as though trending has never been processed).
  • Truncates the core trending tables and removes only their data.
As a reminder, make a backup of any trending data that you want to preserve and restore later. 
Enhanced MVL Storage and Improved Performance of the Load Data Warehouse Job
Full and incremental Load Data Warehouse jobs perform faster in this release due to improvements in multi-value lookup (MVL) processing and storage. General performance improvements apply to Oracle and SQL data warehouses entries with a large number of MVL values (such as cost plans).
This release also includes specific improvements on Oracle data warehouse MVL values with long strings over 4,000 characters. These long strings were often the result of concatenation with the 
listagg
 function and have been redesigned for better performance in Oracle data warehouse databases. No changes were necessary on SQL datasets because MVL data overflow issues were not observed on Microsoft SQL.
 
Upgrade Action
: No action is required.
Data Warehouse Performance Improvements
  •  
    Financial Transaction Facts
    : A new internal processing table DWH_X_PLAN_ACT_PER_FACTS in the data warehouse improves performance. The new table, available in both Oracle and Microsoft SQL databases, improves incremental and full loads of the data warehouse.
    Upgrade Action
    : No action is required.
  •  
    Oracle Merge Capability
    : Incremental data warehouse load performance is improved by leveraging Oracle database merge capabilities in the following tables:
    DWH_FIN_PLAN_PERIOD_FACTS DWH_FIN_PLAN_SUMMARY_FACTS DWH_FIN_TRANSACTION_FACTS DWH_INV_ASSIGN_PERIOD_FACTS DWH_INV_TEAM_PERIOD_FACTS DWH_RES_PERIOD_FACTS DWH_X_PLAN_ACT_PER_FACTS DWH_X_RES_AVAIL_PER_FACTS
    While not guaranteed, tentative product plans target the expansion of this capability to more tables in future releases.
    Upgrade Action
    : No action is required.
Administrative Enhancements
Unsupported Browser Messages for Internet Explorer 11
The new features in the 
New User Experience
 no longer support the legacy Microsoft Internet Explorer 11 browser. In 15.4.0, a message appeared to remind users to switch to another browser. In 15.4.1, administrators can disable those messages; however, Microsoft Internet Explorer 11 remains unsupported for the newest features in 
Clarity PPM
.
 
Upgrade Action
: To determine whether any action is required, follow these steps:
  1. Determine if you have users who continue to use Internet Explorer 11 with the 
    New User Experience
  2. Decide if these users can switch to a compatible browser as listed in the Release Notes.
  3. Determine if the application should show them the unsupported browser message or suppress these messages. For example, if Internet Explorer 11 is required for other applications, you can turn the reminder messages off. If Internet Explorer 11 is no longer supported at your organization, you can allow users to see the reminder messages.
Access Rights and License Types
In previous releases, the application included users with the 
Report - Run (Auto)
 access right in the count of 
restricted
 licenses. In this service pack, users with 
Report - Run (Auto)
 are considered to possess a 
view - only
 license. See 
Access Rights Reference
 and View User Counts by License Type.
Classic PPM Investment Hierarchy Multi-Currency Enhancement
Program and investment hierarchies in the classic user interface now include currency exchange rates in exports to Excel or comma-separated values (CSV). When multiple currencies are active, the aggregation of child values requires currency conversions before calculating correct totals. Exported data has been updated to match.
For example, you use the project or program portfolio hierarchy pages in classic PPM and run the Synchronize Portfolio Investments job. You regularly view the following fields:
Planned Cost Planned Capital Cost Planned Operating Cost Planned NPV Planned Benefit Budgeted Cost Budgeted Capital Cost Budgeted Operating Cost Budgeted Benefit Budgeted NPV
In multi-currency environments in previous releases, some list views were not currency-aware and did not perform currency conversions in summed totals. This release supports the ability to plan subproject costs in a local currency and then roll these costs into the main project in the target converted currency. The converted values apply exchange rates before calculating their totals. Exports to CSV or Excel (data only) match the values that appear in classic PPM.
To illustrate the enhanced behavior, configure multiple currencies and setup currency exchange conversion rates. In a hierarchy of three projects, assign three different currencies. When viewing the parent project or program, the child project values, including cost plans, are converted and then aggregated. Exports to Excel or CSV match the on-screen values.
 
Upgrade Action
: No action is required. 
End-of-Support for SharePoint Integration
The End-of-Life (EOL) milestone for the Microsoft SharePoint Connector Add-in for CA PPM and CA PPM SaaS was announced May 22, 2018. The documentation will remain available in doc sets for older versions (switch your docops.ca.com view to a previous release such as 15.3). However, this feature will no longer appear in the 15.4.x documentation or in newer editions to make room for new features and enhancements. In the future, REST API support for SharePoint integrations might become available.
The SharePoint Add-in will no longer be enhanced or maintained as of May 22, 2018. This feature will no longer qualify for support beyond May 31, 2019. After May 2019, in accordance with our End-of-Life Support Policy, CA Technologies will continue to provide self-service support until the expiration of your current contractual support period.
 
Upgrade Action
: If you are upgrading from a previous release that supported this integration, evaluate your replacement workflow and document repository options. Begin by reviewing the new features in the 
New User Experience
 including project documents, links, and attachments in conversations.
FedRAMP Environments
Add-in Compatibilities
The Release Notes provides the supported add-in versions that are compatible with new installations or upgrades to this release.
  • If you are upgrading from Releases 13.3 or 14.x to the current release, the following add-ins are upgraded automatically:
    • PMO Accelerator
    • Accelerator for the PMBOK
    • CA Agile Planning (deprecated)
  • If you are upgrading from Release 13.2 or earlier to the current release, you must upgrade all installed add-ins.
The following change might be perceived by users upgrading from 14.3 or earlier releases; however, it is not new. Starting with Release 14.4, the default 
Status Report Status
 lookup values changed from 
Minor Variance
 to 
Needs Help
 and from 
Significant Variance
 to 
At Risk
. The 
On Track
 value remained the same. See the English language edition of the PMO Accelerator Release Notes for Release 14.4.
Oracle Table Analyze Job Improvements
For CA PPM on-premise customers with Oracle databases, the Oracle Table Analyze job gathers statistics, traditionally by Estimate Percent, and runs basic database optimization commands. By optimizing database statistics, queries can be opened more quickly resulting in general performance improvement. However, in previous releases, running this job by Estimate Percent was inefficient compared to running it by auto-sampling. 
In CA PPM 15.4.1, the Oracle Table Analyze job no longer includes the following parameters:
  • Schema Name
  • Estimate Percent
The new stored procedure uses the following default values:
  •  
    USER
     for Schema Name
  •  
    AUTO_SAMPLE_SIZE
     for Estimate Percent 
The CMN_GATHER_TABLE_STATS procedure now uses AUTO_SAMPLE_SIZE and all references were updated.
 
Upgrade Action
: No action is required; however, determine whether you need to run this job and how often. See CA PPM Jobs Reference.
Running 
Oracle Stats 
includes histogram stats that increase input-output consumption and paging memory. Because the CA PPM Oracle Table Analyze job does not gather histogram stats, it does not cause these performance issues. CA recommends using the CA PPM Oracle Table Analyze job. 
Internal Rate of Return (IRR) Adjustment
The 15.4.1.4 patch improves the calculation behavior of the Planned IRR field. In previous releases, the Planned IRR for ideas was not calculating a value and was blank in certain scenarios where costs preceeded benefits by about one year. The behavior was limited to detailed plans for ideas; simple plans did successfully calculate IRR.
 IRR_fix.png 
 
Upgrade Action
: This update is available with the 15.4.1.4 patch. No action is required after installation; however, we recommend that you examine your ideas in Classic PPM. Previously blank values for Planned IRR might now calculate a value as a result of this adjustment.
: If no positive (or negative) cash flow exists, IRR is left blank. To learn more, see the following links:
IPv6 Network Compatibility Restrictions
The following information applies to on-premise environments.
CA PPM 15.4 and 15.4.1 are certified to operate in an IPv6 networking environment with restrictions. Other configurations of CA PPM using IPv6 are likely to work but have not been certified. For mixed environments with IPv6 and IPv4, the server instance uses two network interface cards, one configured for IPv6 and the other for IPv4. We performed our certification testing on an isolated private IPv6 environment that is not accessible to other networks.
During PPM installation in IPv6 environments, you are prompted for the correct multicast and bind address. The following entries provide examples:
 
IPv6 Mulitcast
: ff0e::75:75
 
bindAddress
=fe80::cb8b:3483:cddd:bca3
Red Hat Enterprise Linux Configurations with Oracle
We support mixed mode IPv6 installations of CA PPM, mail server, and Jaspersoft in Red Hat Enterprise Linux (RHEL) configurations with Oracle.
  •  
    RHEL OS Version
    : 7u4
  •  
    App Server
    : Apache Tomcat 8.5.23 (64-bit)
  •  
    Database
    : Oracle Enterprise Edition 12.2.0.1.0
  •  
    JasperReports Server
    : 6.4.2
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, resuling 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.4 on RHEL
We do not recommend attempts to integrate any IPv6 components into earlier releases and then upgrade to 15.4. IPv6 was not supported in earlier releases. Upgrade to 15.4 using IPv4 and then switch to IPv6. If your requirements mandate an attempt to force an upgrade from 15.3 to 15.4 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"/>
Installation and Upgrade Enhancements
 
Compatible Database Check
: If the upgrade script detects an Oracle 11.2.x or MS SQL Server 2008/2012 database, the upgrade stops.
 
Upgrade Action
: Upgrade your database to a supported release as listed in the Release Notes.
: You might also need to upgrade to a temporary intermediate release before you can upgrade your database. See the following sample scenarios for guidance.
  •  
    Upgrade Example 1
    : You have CA PPM 14.3 on Oracle 11.2.x and want to upgrade to 15.4.1.
    Upgrade Action
    : Upgrade to Oracle 12.1.0.2 before upgrading to PPM 15.4.1.
  •  
    Upgrade Example 2
    : You have CA PPM 15.2 on Oracle 11.2.x and want to upgrade to 15.4.1.
    Upgrade Action
    : Upgrade to Oracle 12.1.0.2 before upgrading to PPM 15.4.1.
  •  
    Upgrade Example 3
    : You have CA PPM 13.x or 14.2 on Oracle 11.2.x and want to upgrade to 15.4.1.
    Upgrade Action
    : Upgrade to CA PPM 14.3, 14.4, 15.1, or 15.2. before attempting to update the Oracle database. Oracle 12.x is not supported until 14.3. Upgrade CA PPM to a supported temporary release and then upgrade the database to Oracle 12.1.0.2 before upgrading to PPM 15.4.1.
  •  
    Upgrade Example 4
    : You have CA PPM 13.x or 14.2 on SQL Server 2008 or 2012 and want to upgrade to 15.4.1.
    Upgrade Action
    : Upgrade to CA PPM 14.3, 14.4, 15.1, or 15.2 before attempting to update the SQL Server database. SQL Server 2014 is not supported until 14.3. Upgrade CA PPM to a supported temporary release and then upgrade the database to SQL Server 2014 or 2016 before upgrading to PPM 15.4.1.
 
Backups During Upgrades:
 When you attempt an upgrade from Release 15.3 or a previous release to this release, the upgrade offers to save database backups for you. This behavior does not occur if you upgrade from 15.4. A gap of two or more releases is required (in this case, 15.3 to 15.4 and then 15.4 to 15.4.1). One backup is stored at a time for each release-level step. For example, you create a backup of your 14.4 database and then start an upgrade to 15.4.1. The upgrade attempts to save a backup of your temporary 15.1 database. The upgrade continues, purges that backup, and then attempts to backup your temporary 15.2 database. If you encounter a problem before the final 15.4.1 upgrade finishes, you have a more recent backup. In previous releases, rollback to an earlier release was in many cases the only option.
 
Upgrade Action
: Before starting the upgrade, to allow backups, grant the required permissions to the database schema user.
Depending on the size of your database, each step-level backup can potentially take several hours for each release in the upgrade path. We recommend that you attempt the upgrade with database backups in a sandbox environment. When you have resolved any upgrade issues, perform the production upgrade and skip the backups.
 
Delete Process Instance Job
: After an upgrade, this release defines a recurrent quarterly schedule for the Delete Process Instance job. This job cleans up obsolete BPM_ERRORS table entries as far back as 90 days (one quarter). This default behavior helps control the size of the BPM_ERRORS table. 
 
Upgrade Action
: No action is required; however, you have options. The upgrade process truncates the records in the BPM_ERRORS table and moves them into BPM_ERRORS_BKP. At this point, the upgrade has successfully reduced the size of this table. No further action is required. However, as an option, you can retrieve the data if you need it for auditing or troubleshooting purposes.
As an on-premise administrator, to restore the last 90 days of data from the backup table to the BPM_ERRORS table, run the following query:
INSERT INTO BPM_ERRORS
SELECT * FROM BPM_ERRORS_BKP WHERE LAST_UPDATED_DATE >= (SELECT (MAX(LAST_UPDATED_DATE)-91) CUTOFF_DATE FROM BPM_ERRORS_BKP) AND NOT EXISTS (SELECT 1 FROM BPM_ERRORS WHERE BPM_ERRORS_BKP.ID = BPM_ERRORS.ID);
 
New CSA Setting for Error Logging
: A new CSA setting introduced in 15.3 allows you to configure the level of logging that you want to see for process GEL scripts using <gel:log>. As a default, only errors or fatal logs are persisted in the BPM_ERRORS table. Accordingly, only error messages appear on the user interface. Messages that are not logged in BPM_ERRORS are not visible. You can change the default setting to allow logs for warnings and other informational messages so they also appear.
 
Upgrade Action
: No action is required; however, you have options. After an upgrade, the default logging level for process GEL scripts is set to 
Error
. Unless an error occurs, nothing gets logged in the BPM_ERRORS table. As an on-premise administrator, you can change the default security log setting in 
Clarity PPM
 System Administration (CSA). For example, change the value of the Process Engine Persistence Log Level field. For better performance, we recommend that you the keep the logging level at 
Error
.
Data Warehouse Changes
 
Installation of the Data Warehouse is Required
: As a reminder, starting with the previous release (15.3), you must deploy the 
Clarity PPM
 data warehouse. It is an integrated component of the product.
 
Upgrade Action
: You can configure it for reporting, lookup queries, and trending or decide not to use it. However, it must be installed and configured in all environments, on-premise and SaaS.
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 in Release 15.4.1
The following section lists the known issues at the time this release was delivered. Based on feedback and priority, additional known issues after the GA release date are sometimes added.
 
 
4
 
4
 
 
Oracle 12c Release 2 Performance
Some performance degradation could be the result of a possible ORDERED hint regression issue in Oracle 12c Release 2 SQL statements.
  • For Oracle 12c R1 (12.1.0.2), no action is required. 
  • For Oracle 12c R2 (12.2.0.1), enable the following parameter and set the optimizer to 12.1.0.2.
To improve performance, database administrators can run the following commands:
sqlplus / as sysdba ALTER SYSTEM SET "_fix_control" = '17800514:0'; ALTER SYSTEM SET OPTIMIZER_FEATURES_ENABLE= '12.1.0.2' SCOPE=BOTH; Exit;
This issue and workaround are subject to change pending further third-party developments.
Setting the Locale to Chinese (Taiwan) Disables Roadmaps, Financials, and Risks, Issues, Changes
In classic 
Clarity PPM
, you can change the locale under 
Home
Personal
Account Settings
. If you set the 
Locale
 to 
Chinese (Taiwan)
, the following capabilities are no longer available in the 
New User Experience
:
  • Roadmaps
  • Project Financials
  • Project Risks, Issues, and Changes
Project Role Lookup Field Displays both Labor and Non-labor Roles
If a user has 
Resource – View
 access to non-labor roles, these roles also appear in the Project Role lookup field on the new project staff page. If you are using the 
New User Experience
 only for managing project staff and you are 
not
 using non-labor roles and resources, grant the 
Resource – View
 (OBS or instance) access right for labor roles only. Granting the view access right for labor roles and resources only ensures that non-labor roles do not appear in the Project Role lookup field.
Visual and Module Labels in a Blueprint are Only Available in English
The labels for visuals and modules that you can configure in a project blueprint are visible only in the English language.
Numbers Not Displayed Correctly if Color-Mapping is Defined for Numbers with Fractional Values
The numbers are not displayed correctly if color-mapping is defined for numbers with fractional values such as FTE. See KB000097845 for details and workaround.
Amounts from Different Currencies are Not Aggregated on the Timeline
If your roadmap contains roadmap items associated with different currencies, the amounts are not aggregated in the timeline.
Email Notifications for New UX Project Team Members Include a Link to Classic PPM
When a resource is added as a participant on a project in the new UX, the email notification provides a link to the project in classic PPM. With access rights to the new UX, the user can navigate to the appropriate project in the new user interface.
JasperReports Server 6.4.2 Missing Input Values and Data When Drilling Back to Original Report
When attempting to drill into a second report from an initial report, some reports might not display your input values. The following message appears:
 
 You must apply input values before the report can be displayed.
 
For example, you might encounter this known issue when drilling into a second report from one of the following original reports:
  • Over/Under Allocation by Resource drilling down to Capacity Vs. Demand by Resource
  • Top 50 Project Watchlist drilling down to Project Status
  • User License and Activity drilling down to User License and Activity Detail
TIBCO is tracking this issue as JS-33944.
DE41635: Cost Plan Data in the User Interface Does Not Match the Slice Table
If you have a cost plan populated from Investment Team and you edit a value for one of the periods and then repopulate the plan from Investment Team, the corresponding slice in table ODF_SSL_CST_DTL_COST does not get resliced. Instead, it retains the value that was manually updated. This known issue can occur for labor and non-labor resources and roles. In prior versions, when the cost plan was repopulated, all the records in 
fin_cost_plan_details
 got recreated. In 15.4, it does not appear that the records are created again after the cost plan repopulates. You might see differences in cost values between the ODF_SSL_CST_DTL_COST slice table and the Cost Plan Details page. The slice table is not updating the values if any of the plan values are manually edited and then the plan is repopulated.
A fix for DE41635 was delivered in the 15.4.1.1 patch and 15.5.0.0 base release. 
DE42973, DE42977: Load Data Warehouse Job 'Encountered Exception'
Incremental Load Data Warehouse job instances could fail with the following error:
ORA-20100: ENCOUNTERED EXCEPTION WHILE INSERTING INTO DWH_INV_PER_FACTS_LOAD. SQLERRM : ORA-30926: unable to get a stable set of rows in the source tables
 
Steps to Reproduce
:
  1. Run a Full Load of the DWH
  2. Create a Financial Plan on a project that didn't have a financial plan
  3. Run an Incremental Load of the DWH
  4. While the Incremental is running, add a risk
    The job aborts due to dwh_x_inv_plan_per_facts_mv looking at the plan_exists flag in dwh_x_inv_sum_facts.
A fix was delivered in the CA PPM 15.4.1.2 patch. As a workaround, do not schedule the Load Data Warehouse job during business hours.
DE43623: Updates to Roadmap Items Can Cause the Load Data Warehouse Job to Fail
The Load Data Warehouse job could fail if users create or edit roadmap items after the job has been scheduled to run. Foreign key constraint errors can also result if users create roadmaps or adjust the position of roadmap items in the timeline before the job has finished. 
 
Error Example 1:
 
Execute SQL script - org.pentaho.di.core.exception.KettleStepException: Error while running this step Couldn't execute SQL: ALTER TABLE DWH_RDM_ITEM_POSITION ENABLE VALIDATE CONSTRAINT DWH_RDM_ITEM_POSITION_FK2 [CA Clarity][Oracle JDBC Driver][Oracle]ORA-02298: cannot validate (US5NP2096DDWH.DWH_RDM_ITEM_POSITION_FK2) - parent keys not found at org.pentaho.di.trans.steps.sql.ExecSQL.processRow(ExecSQL.java:251) at org.pentaho.di.trans.step.RunThread.run(RunThread.java:60) Caused by: org.pentaho.di.core.exception.KettleDatabaseException: Couldn't execute SQL: ALTER TABLE DWH_RDM_ITEM_POSITION ENABLE VALIDATE CONSTRAINT DWH_RDM_ITEM_POSITION_FK2 [CA Clarity][Oracle JDBC Driver][Oracle]ORA-02298: cannot validate (US5NP2096DDWH.DWH_RDM_ITEM_POSITION_FK2) - parent keys not found
 
Error Example 2:
 
Execute SQL script - org.pentaho.di.core.exception.KettleStepException: Error while running this step Couldn't execute SQL: ALTER TABLE DWH_RDM_ROADMAP_ITEM ENABLE VALIDATE CONSTRAINT DWH_RDM_ROADMAP_ITEM_FK1 [CA Clarity][Oracle JDBC Driver][Oracle]ORA-02298: cannot validate (US5NP2096DDWH.DWH_RDM_ROADMAP_ITEM_FK1) - parent keys not found at org.pentaho.di.trans.steps.sql.ExecSQL.processRow(ExecSQL.java:251) at org.pentaho.di.trans.step.RunThread.run(RunThread.java:60) Caused by: org.pentaho.di.core.exception.KettleDatabaseException: Couldn't execute SQL: ALTER TABLE DWH_RDM_ROADMAP_ITEM ENABLE VALIDATE CONSTRAINT DWH_RDM_ROADMAP_ITEM_FK1 [CA Clarity][Oracle JDBC Driver][Oracle]ORA-02298: cannot validate (US5NP2096DDWH.DWH_RDM_ROADMAP_ITEM_FK1) - parent keys not found
A fix for this issue was delivered with the CA PPM 15.4.1.3 patch and CA PPM 15.5.1 service pack in early December 2018. As a workaround, do not schedule the Load Data Warehouse job during business hours.
DE42925: Cannot XOG-Out Data For a Single User By Resource ID
You might experience the following issue if you export (XOG-out) a project with multiple task assignees. To encounter this issue, you would have to modify your XOG script to filter on the project ID and just one resource ID from the project. After you export the project, instead of getting filtered allocations for a particular resource, your XOG output contains the allocations for every resource in the project.
 
Workaround
: Apply post-processing on the output to filter the content or extract the single record.
This issue has been resolved in recent development activity for the next release of CA PPM. Contact CA Support to request the possibility of inclusion in a future 15.4.1 or 15.5.1 patch.
After resolving this issue, either of the following filters for 
resourceId
 or 
resourceID
 will work as expected to filter for only one resource:
<Filter name="resourceId" criteria="EQUALS">csk.testEngineer</Filter>
<Filter name="resourceID" criteria="EQUALS">csk.testEngineer</Filter>
Until you upgrade to 15.5.1, avoid creating GEL scripts that attempt to read, run, or append records in very large CSV files. Out-of-memory errors and application outages can occur. 
DE42180: Agile Sync Job cannot process more than 50 resources at a time
When creating or syncing an existing project in CA PPM and marking it to sync with Rally the following error is received after running the PPM Synchronize Agile Central scheduled job.
There was a problem while syncing the project team for project: 400 api.maxRecordsProcessError API-1002: Can only process 50 records at a time.
 
Workaround
: Upgrade to 15.5 or higher. This known issue in 15.4.1 was resolved in 15.5 or higher.
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
Install PMO or APM add-ins
Data Warehouse Configured
 
New User Experience
 
PMO Accelerator Add-in
Supported Upgrade Paths for Release 15.4.1
To upgrade 
directly
 to 15.4.1, your current release must be 14.2 or higher. The 15.4.1 installer can backup and upgrade your data from supported older releases. The installer detects how many incremental upgrade paths are required to update your installation to the latest release. If two or more, you are prompted to decide if you would like the automated backups to occur.
  • If you have Release 13.3 or 14.1, you can upgrade to Release 15.4 and then apply the 15.4.1 service pack.
  • You cannot upgrade to Release 15.4 
    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 upgrade does not support those configurations. Your indirect upgrade is still supported. For example, upgrade to 14.3 and Jaspersoft 6.2.1 first. Then upgrade to 15.4 and then apply the 15.4.1 service pack.
  • You can upgrade from 14.2 to 14.4 if you have no Jaspersoft reports environment configured. You can also elect to upgrade from those releases and perform a fresh installation of your reports environment.
  • To upgrade from 13.2 and earlier releases, upgrade to 14.2 or 14.3 first. This middle step simplifies the troubleshooting and restart process if an upgrade step fails. Then upgrade to 15.4 and then apply the 15.4.1 service pack.
If you have installed any patches on the base version, verify that you applied the latest supported cumulative patch before you upgrade. Patch maintenance before and after upgrades is important for troubleshooting, security fixes, and general system health.
 
Follow these steps
:
  1. Select your current release from the 
    Versions
     menu at the top right of that docops page.
    For example, select 15.1 and verify you installed the 15.1.0.9 patch or select 15.3 and verify that you installed the 15.3.0.3 patch before starting your upgrade to 15.4.1.
 You might experience issues if you attempt to upgrade directly from an unsupported patch level. For best results, follow a supported upgrade path. To learn more, contact CA Support or CA Services. You can also visit the CA PPM Community to collaborate with other community members about your specific questions.
After the June 2018 release of 15.4.1, you can upgrade to 15.4 and apply the 15.4.1 service pack, or, if supported, upgrade directly to 15.4.1. You can upgrade from 15.4.0.0 base release to 15.4.1.0 service pack without applying the 15.4.0.1 patch first.
MS SQL Server Database Compatibility Level
If you are using SQL Server 2014 for this release, set the compatibility level to 120 from SQL Server Management Studio or use the following command:
EXEC SP_DBCMPTLEVEL <database>, 120
Oracle Database Only PRJ_BLB_SLICES Table
The ID, UNIT, LAST_UPDATED_DATE and LAST_UPDATED_BY columns in the PRJ_BLB_SLICES table have been dropped. If you are using Oracle, the table is replicated before the columns are dropped. The replication requires you to verify that the tablespace that PRJ_BLB_SLICES occupies is large enough to accommodate the temporary size increase.
 
Upgrade Action
:
To determine if the tablespace can deal with this condition, have your database administrator (as sysdba) run the following query. Change the schema owner to the owner of the 
Clarity PPM
 schema:
select SLC.owner, SLC.table_name, SLC.TABLESPACE_NAME, SLC.MB MB_NEEDED, TBSPC.MB_FREE MB_FREE, SIZING.MAX_MB, SIZING.MB_USED, EXT.AUTOEXTENSIBLE FROM (select owner, table_name, NVL(round((num_rows*avg_row_len)/(1024*1024)),0) MB, TABLESPACE_NAME from all_tables where owner = 'CLARITY' and table_name = 'PRJ_BLB_SLICES') SLC INNER JOIN (select df.tablespace_name, (df.totalspace - tu.totalusedspace) "MB_FREE" from (select tablespace_name, round(sum(bytes) / 1048576) TotalSpace from dba_data_files group by tablespace_name) df, (select round(sum(bytes)/(1024*1024)) totalusedspace, tablespace_name from dba_segments group by tablespace_name) tu where df.tablespace_name = tu.tablespace_name) TBSPC ON (SLC.TABLESPACE_NAME = TBSPC.TABLESPACE_NAME) INNER JOIN (select distinct(autoextensible), tablespace_name from dba_data_files) EXT on (slc.tablespace_name = ext.tablespace_name) INNER JOIN (select tablespace_name , count(*) as no_of_data_files , sum(MAXBYTES)/(1024*1024)*count(*) as MAX_MB , sum(user_bytes)/(1024*1024) MB_USED , round((sum(user_bytes)/(1024*1024))/(sum(MAXBYTES)/(1024*1024))*100,2) PERCENT_USED from dba_data_files group by tablespace_name) SIZING ON (SLC.TABLESPACE_NAME = SIZING.TABLESPACE_NAME)
The following example shows the kind of results that the query returns:
OWNER TABLE_NAME TABLESPACE_NAME MB_NEEDED MB_FREE MAX_MB MB_USED AUTO-EXTENSIBLE CLARITY PRJ_BLB_SLICES USERS_LARGE 1306 5020 90000 15997 YES
 
If AUTOEXTENSIBLE is YES:
 
The tablespace for PRJ_BLB_SLICES can grow automatically up to the MAX_MB value. Ensure that the MAX_MB value is higher than the MB_NEEDED + MB_USED.
 
If AUTOEXTENSIBLE is NO:
 
Ensure that the MB_NEEDED value is less than MB_FREE. If the MB_NEEDED value is not lower, the database administrator can allocate or extend extra data files to the tablespace under the TABLESPACE_NAME column.
We recommend increasing the tablespace at least 20 percent more than is needed. The increase helps to ensure that the tablespace can accommodate standard data growth and the temporary replication.
Custom Processes, Scripts, and Other Customizations
CA PPM cannot upgrade any unsupported customized content. Customizations must be disabled and may need to be redesigned and re-implemented to work with changing product functionality.
! After an upgrade, unless you disable them, your customizations might result in errors or fail to work as expected.
 
Follow these steps
:
  1. Identify your custom content. For example, you have one or more custom processes with custom GEL scripts that modified timesheet status attributes in a previous release.
  2. Acknowledge the customizations and recognize that the upgrade scripts might not support the custom content. Even if the custom content is upgraded, it may no longer work as expected. For example, your custom process references an object or attribute that has changed in the new release.
  3. As an on-premise administrator, the checkinstall script provides a warning for customizations that it detects pre-upgrade. You can see these warnings or the referenced logs for insight into the types of customizations that can negatively impact your upgrade experience. For example:
    WARNING: Possible schema customizations have been found. Any customizations to the system are the responsibility of the customer to maintain and are not supported. To upgrade, all customizations must be reviewed, changed, or removed as needed before the upgrade. After a successful upgrade, the customizations may be added back to the system. The possible customizations found are listed in the following log files:
    check‐logs/database_customization_triggers.txt check‐logs/database_customization_indexes.txt check‐logs/database_customization_tables.txt checklogs/database_customization_constraints.txt
  4. As an on-demand (SaaS) administrator, you do not see these warnings or the referenced logs. These example messages provide insight into the types of customizations that can negatively impact your upgrade experience.
  5. In on-premise or SaaS environments, turn off your customizations before the upgrade. After the upgrade, reintroduce the customizations and test them in the Classic PPM interface. Optionally, verify the impact of the customization behavior on the 
    New User Experience
  6. In addition to database objects, also evaluate attribute values. Review the Oracle and Microsoft SQL database and data warehouse changes (see the Reference section in the English documentation). Validate if any of your customizations depend on any dropped, changed, or new attributes.
Some customers have experienced errors with legacy custom content. After disabling the custom process, script, or other legacy custom content, the 
New User Experience
 provided the functionality with no net loss to end users. We recommend that you perform an analysis comparing the value of CA PPM features in a complete COTS/SaaS solution against the value of developing your own unsupported customizations.
 
More Information
: