Skip to content
CA PPM - 14.2
Documentation powered by DocOps

Release 14.1 Updates (On Premise)

Last update December 22, 2017

Supported Upgrade Paths for Release 14.1

Before you start the upgrade, we recommend that you read the information in Change Impact and Upgrade (On Premise).

If you have any of the following releases installed on the base level with no patches, you can directly upgrade to CA PPM Release 14.1:

  • CA PPM Release 8.1 or Service Pack or Fix Pack 8.1.x
  • CA PPM Version 12.0 or Service Pack 12.0.x
  • CA PPM Release 12.1 or Service Packs
  • CA PPM Version 13.0 or Service Packs
  • CA PPM Release 13.1
  • CA PPM Release 13.2
  • CA PPM Release 13.3

Follow the upgrade path included in the following table, only if you have installed any patches on the base versions:

Patch Levels Upgrade Path
If any patch level is installed on the base version 12.1.0 (i.e. 12.1.0.1 - 12.1.0.8) Installation of 12.1.0.8 is required before the upgrade to Release 14.1.
If any patch level is installed on the base version 12.1.1
(that is, 12.1.1.1 - 12.1.1.10)
Installation of 12.1.1.10 is recommended before the upgrade to Release 14.1.
If any patch level is installed on the base version 12.1.2
(that is, 12.1.2.1 - 12.1.2.3)
Installation of 12.1.2.3 is recommended before the upgrade to Release 14.1.
If any patch level is installed on the base version 12.1.3
(that is, 12.1.3.1 - 12.1.3.6)
Installation of 12.1.3.6 is recommended before the upgrade to Release 14.1.
If any patch level is installed on the base version 13.0.1
(that is, 13.0.1.1 - 13.0.1.7)
Installation of 13.0.1.7 is required before the upgrade to Release 14.1.
If any patch level is installed on the base version 13.1.0
(that is, 13.1.0.1 - 13.1.0.5)
Installation of 13.1.0.9 is recommended before the upgrade to Release 14.1.
If any patch level is installed on the base version 13.2.0
(that is, 13.2.0.1 - 13.2.0.4)
Installation of 13.2.0.8 is recommended before the upgrade to Release 14.1.
If any patch level is installed on the base version 13.3.0
(that is, 13.3.0.1 - 13.3.0.7)
Installation of 13.3.0.7 is recommended before the upgrade to Release 14.1.

For example:

  • If you have CA PPM SP 12.1.3, you can directly upgrade to Release 14.1.
  • If you have CA PPM 12.1.0.2, then you have to apply CA PPM 12.1.0.8 first to upgrade to Release 14.1.
  • If you have CA PPM 12.1.3.4, then it is recommended that you apply CA PPM 12.1.3.6 first to upgrade to Release 14.1.
  • If you have CA PPM 12.1.3.6, you can directly upgrade to Release 14.1.

Important! If you are on a CA PPM patch level that is not included in the preceding list, take care when attempting an upgrade to Release 14.1. Issues could result if you try to upgrade to Release 14.1 from a patch level that is not supported. For best results, wait for a supported upgrade path to a later release or patch. To find out more, contact CA Support or your CA Services representative. You can also find more information by visiting the CA PPM User Communities.

The Release 14.1 installer can upgrade your data set from a variety of older releases. The installer detects how many incremental upgrade paths are required to bring your current installation up to Release 14.1.

Note: If you are running a version earlier than Release 12.1.1, consider upgrading to 12.1.1, 12.1.2, or 12.1.3 before you upgrade to Release 14.1. Although the interim upgrade is not a requirement, it simplifies the troubleshooting and restart process if an upgrade step fails.

The Release 14.1 installer runs the upgrade processes included in the following table.

Version, Release, or Service Pack Currently Installed Upgrade Processes
Earlier than Service Pack 12.1.1

Service Pack 12.1.1

Version 13.0

Release 13.1

Release 13.2

Release 13.3

Release 14.1

Service Pack 12.1.1, 12.1.2, or 12.1.3

Version 13.0

Release 13.1

Release 13.2

Release 13.3

Release 14.1

Version 13.0 or Service Pack 13.0.x

Release 13.1

Release 13.2

Release 13.3

Release 14.1

Release 13.1

Release 13.2

Release 13.3

Release 14.1

Release 13.2

Release 13.3

Release 14.1

Release 13.3 Release 14.1

Upgrade Considerations for Release 14.1

Here are the installation and upgrade changes for Release 14.1.

Add-ins Compatibilities

The following section describes important information about upgrading installed add-ins, accelerators, and connectors.

  • If you are upgrading from Version 13.0 through Release 14.1 to Release 14.2, the following add-ins are upgraded:
    • PMO Accelerator
    • Clarity Solution Pack (CSP)

      Note: The CSP add-in is supported only for existing customers. This add-in is not supported for new CA PPM installations.
    • CA Clarity Agile
  • If you are upgrading from any version before Version 13.0 to Release 14.2, upgrade all installed add-ins.
  • Starting with Version 13.3, a new installation process is required for add-ins, accelerators, and connectors.

    Note: For more information, see Installing and Upgrading.

The following table includes the add-in, accelerator, and connector releases that are compatible with Release 14.2.

Add-in, Accelerator, or Connector New Installation
14.2
Upgrade from 12.x to 14.2 Upgrade from 13.x or 14.1 to 14.2
PMO Accelerator 14.2.0 14.2.0 14.2.0
Clarity Solution Pack (CSP) 14.2.0 14.2.0 14.2.0
Earned Value Manager 2.0.2 2.0.2 2.0.2
Accelerator for PRINCE2 2.0.2 2.0.2 2.0.2
Accelerator for the PMBOK 2.0.2 2.0.2 2.0.2
Accelerator for New Product Development 2.0.3 2.0.3 2.0.3
PPM Essentials Accelerator 2.0.2 2.0.2 2.0.2
BRM Accelerator 3.0.2 3.0.2 3.0.2
Connector for CA Unicenter Service Desk 12.7 & CA Software Change Managerâ„¢ 12.1.0.3 2.0.1 2.0.1 2.0.1
Connector for CA Unicenter Asset Portfolio Management 11.3.4 2.0.2 2.0.2 2.0.2
Connector for Microsoft SharePoint 2013 3.0.0 3.0.0 3.0.0
Service Connect 2.0.0 2.0.0 2.0.0
Catalyst Connector 2.5.0 2.5.0 2.5.0
CA Clarity Agile 14.1.0 14.1.0 14.1.0
VersionOne Connector 14.1.0 14.1.0 14.1.0

Add-in Installation

Add-ins, accelerators, and connectors are now included with the CA PPM installation. You do not have to download the add-in separately and extract the .jar file.

Note: For more information about the new add-in installation process, see Installing and Upgrading.

Upgrade Action: See the Add-in Compatibilities section if you are required to install a new version of your existing add-ins, accelerators, or connectors.

Clarity Solution Pack Compatibility

The Clarity Solution Pack (CSP) is supported only for existing customers. This add-in is not supported for new CA PPM installations.

Before you install the CSP add-in, verify that the compatible versions of CA PPM and the PMO Accelerator are installed. The CSP installation fails if you do not install the compatible version of the PMO Accelerator add-in before installing the CSP.

Important! Review the certified and supported versions chart in the CSP Release Notes to determine if an upgrade of CA PPM and the PMO Accelerator is required or optional. For complete information, see the Clarity Solution Pack Index page on CA Support Online.

Java 7

This release uses Java 7. In addition to the CA PPM server, the following software clients also require Java 7:

  • XML Open Gateway (XOG) client
  • Service Connect

CA PPM provides a specific Java Runtime Environment (JRE) for the following clients.

  • Open Workbench
  • Connector for Microsoft SharePoint

The JRE is copied to the hard drive in the installation directory on the end-user workstation. The JRE is used specifically for the clients and is independent of the JRE used for the Windows workstation.

Note: For an upgrade from a 13.x version, the server installer prompts for the path of JDK 1.7.
Important! The Java Runtime Environment (JRE) is updated frequently with fixes for security issues, including issues that are unknown at the time CA PPM is released. To ensure that you have the latest fixes, we recommend that you download the most recent version 7 JDK from the Oracle website.

Upgrade Action: Install Java 7 on workstations that have the software clients for which CA PPM does not provide the JRE.

J2EE Installations

For an upgrade on an installation that uses generic as the vendor type, update the DataDirect JDBC driver .jar files in your third-party application server environment. The version for these files has changed in this release.

Upgrade Action: Update your DataDirect JDBC driver .jar files. For more information, see Installing and Upgrading.

Internet Explorer 11

If you are using Internet Explorer 11 with CA PPM, the browser is automatically set to run in the Internet Explorer 10 compatibility mode for the CA PPM session. The setting is for the CA PPM session only and does not affect any other Internet Explorer 11 browser activity.

Known Issues for Release 14.1

Here are the known issues for Release 14.1.

Duplicate Cost Plan Code Error

This issue applies only to upgrades from a 12.x release to the current release.

The duplication of a plan code within a financial plan can cause the upgrade process to fail. The plan code for each plan type within the investment must be unique. For example, you can have a cost plan with the code MasterPlan2011 and a budget plan with the same code. However, you cannot have two cost plans with code MasterPlan2011 for the same investment. The unique database constraint for this rule was added in Version 13.0.

Due to concurrency issues, there can be a data issue in previous versions. When a duplicate plan type code exists within a single financial plan, the upgrade process fails with an appropriate error message. You are required to correct the data issue before resuming the upgrade process. An upgrade check script runs and alerts you that this problem exists.

To identify possible data issues before you start the upgrade, run the following query:

SELECT p1.id, p1.code, p1.name 
FROM fin_plans p1, fin_plans p2 
WHERE p1.id != p2.id 
AND p1.object_id = p2.object_id 
AND p1.code = p2.code 
AND p1.plan_type_code = p2.plan_type_code

If this query returns any rows, it indicates issues with fin_plans table data.

We recommend that you rename the codes for duplicate records. Do not change the other data. A sample query is available to fix the data issues. Because this known issue deals with financial information, review the query carefully before deciding to use it. The following query appends _<internalId> to the duplicate plan code.

<!-- Oracle --> 
UPDATE fin_plans 
SET code = code || '_' || to_Char(id) 
WHERE id IN 
    ( SELECT p1.id 
                              FROM fin_plans p1, fin_plans p2 
                              WHERE p1.id != p2.id 
                AND p1.object_id = p2.object_id 
                AND p1.code = p2.code 
                AND p1.plan_type_code = p2.plan_type_code 
                ) 


<!-- Mssql --> 
UPDATE fin_plans 
SET code = code + '_' + CAST(id AS VARCHAR) 
WHERE id IN ( SELECT p1.id 
                                FROM fin_plans p1, fin_plans p2 
                                WHERE p1.id != p2.id 
                AND p1.object_id = p2.object_id 
                AND p1.code = p2.code 
                AND p1.plan_type_code = p2.plan_type_code 
) 

Missing Data for Resource Financials

This issue applies only to upgrades from a 12.x release to the current release.

If the Resource Class or Transaction Class fields are null for Resource financials, the upgrade process fails. The data must be corrected before you resume the upgrade process. An upgrade check script runs and alerts you that this problem exists.

The not null database constraint for the RESOURCE_CLASS and TRANSCLASS columns in the PAC_MNT_RESOURCES table was added in Version 13.0. If you are upgrading from a previous version of CA PPM, it is possible that the information is missing.

We recommend running the following query to identify records with this data issue before starting the upgrade.

Select * from pac_mnt_resources where RESOURCE_CLASS is null OR transclass is null

If this query returns any rows, it indicates that there are issues with the PAC_MNT_RESOURCES table data. We recommend reviewing all returned records and updating the records with valid transaction class and resource class values.

Upgrade Fails if the Default Language for the Admin User Is Not English

A portion of the upgrade relies on the English locale when it is importing content using the XML Open Gateway (XOG). This import fails if the default language of the admin user is not set to English. The workaround is to set the admin user language to English.

Resume Capability During the Upgrade

CA PPM does not support the ability to resume during an upgrade. We recommend that you run the Checkinstall utility and review the reports that it generates before starting. To reduce the possibility of a failure, correct any errors that the Checkinstall reports indicate.

If your upgrade fails, review the logs and the Checkinstall post-installation reports to determine the reason for the failure. Then, restore the working preupgrade version and database, correct the failure, and restart the upgrade.

Export Icons in Resource Planning Tabs Not Functioning

Export to Excel and Export to PowerPoint icons on a Resource Planning tab give an error when you click them.

Note: This issue applies only to WebSphere application servers.

As a workaround, use the Export to Excel and Export to PowerPoint links available from the Options icon in the individual portlets on the tabs.

Missing General Action Menu After Upgrade

In some cases, the General Action menu does not appear after an upgrade. This issue occurs on the Project object when the following conditions exist:

  • In the edit properties view (Layout:Edit), a display condition is defined on the General subpage.
  • The General object actions menu for the view is not customized.

You can correct the issue before the upgrade, or you can upgrade and then correct the issue in the new upgraded product.

To correct the issue before the upgrade:

Remove the display conditions on the General subpage before the upgrade and redefine the display conditions after the upgrade.

Note: If the preupgrade server is on Version 13.0 or a later service pack, you can handle the issue in a different manner. Before you start the upgrade, edit the General Action menu. Move any action that is listed there from the Available Actions list to the Selected Actions list and save. After the upgrade is complete, you can remove any unwanted actions.

To correct the issue after the upgrade:

  1. Create an action menu with the following details:
    • Menu Name: General
    • Menu Code: general
    • Description: General
  2. Move the following out-of-the-box actions from the Available Actions to the Selected Actions list:
    • Add to My Projects
    • Copy Project from Template
    • Remove from My Projects
    • Go to Links Page
    • Go to Notes Page
Note: For more information about creating an action menu, see CA PPM Studio Development.

Automatic Update to Curly Brackets in OBS Names During Upgrade

If an OBS name contains a left curly bracket ({) or a right curly bracket (}), left or right parentheses replace the characters during the upgrade.

Example: The OBS name External{Department} becomes External(Department) after the upgrade.

Report Instance Export from the Report Library

You cannot export report instances from the report library when the BusinessObjects server is configured with CA PPM installed on a Windows 2012 server. BusinessObjects Enterprise 3.1 SP5 is not supported for Windows 2012.

Note: Installing the BusinessObjects server on a supported configuration does not avoid this issue. The .jar files that are used for the CA PPM integration are not compatible with Windows 2012.

Orphan Records in Table CMN_SEC_ASSGND_OBJ_PERM for MSSQL Users

A recent change prevents the creation of orphan records in the table CMN_SEC_ASSGND_OBJ_PERM. However, for MSSQL users, pre-existing orphan records can sometimes remain. You can search for orphan records and can remove them from the table after the upgrade is complete.

To verify that orphan records exist in the table, run the following query:

select COUNT(*)  from (select object_instance_id from cmn_sec_assgnd_obj_perm p
    where p.object_ID = 50680 and object_instance_id not in 
(select ID from BPM_RUN_PROCESSES)) q

The number value that the query returns indicates the number of orphan records.

To clean up orphan records, invoke the following upgrade script from <clarity_install_dir>/bin using dbpatch:

POSTUPGRADE_57954_MSSQL_DEL_PROC_INST_ASSGND_OBJ_PERM.xml

Use the following command:

dbpatch -install -file <CLARITY_INSTALL_DIR>\upgrade\13.3.0\component\postupgrade\POSTUPGRADE_57954_MSSQL_DEL_PROC_INST_ASSGND_OBJ_PERM.xml -apply

Note: The length of time the query runs is dependent on the number of orphan records to be deleted.

CA PPM Upgrade and Oracle Enterprise Table Compression

If you are using the Oracle Enterprise Edition compression feature, disable the compression feature before starting the CA PPM upgrade. If the compression feature is enabled, the upgrade fails with the following Oracle database error:

[CA Clarity][Oracle JDBC Driver][Oracle]ORA-39726: unsupported add/drop column operation on compressed tables

The following procedure explains how to prepare for the upgrade by disabling compression. Once the procedure is complete, you can proceed with the upgrade. When the upgrade has successfully completed, you can compress the tables again.

To prepare for the upgrade, complete the following steps:

  1. Identify compressed tables by executing the following query:

    SELECT TABLE_NAME, COMPRESSION FROM USER_TABLES WHERE COMPRESSION='ENABLED';
    
  2. Disable compression. Run the output of this query. Keep this list handy, so that these tables can be compressed again after the upgrade.

    SELECT 'ALTER TABLE ' || TABLE_NAME || ' MOVE NOCOMPRESS;'  FROM USER_TABLES WHERE COMPRESSION='ENABLED';
    
  3. Rebuild the unusable indexes. Run the output of this query:

    SELECT 'ALTER INDEX ' || INDEX_NAME || ' REBUILD;' FROM USER_INDEXES WHERE STATUS='UNUSABLE';
    

Update Operation For Some Project Object Attributes Does Not Appear in the Audit Trail

In some instances, when auditing is enabled for specific attributes on the Project object, only the insert operation is reported in the audit trail. The update operation does not show for the attributes. The affected attributes include:

  • Budgeted Capital Cost
  • Planned Capital Cost
  • Budgeted Operating Cost
  • Planned Operating Cost

WebSphere Deployment Does Not Show Database Information in CA Clarity System Administration

During a generic J2EE installation, the nsa.ear file installs CA Clarity System Administration. Once you start CA Clarity System Administration, you can see the database information after you specify your database credentials. However, if you are installing on WebSphere, the database information is not available. Neither the Install History page nor the Installation Overview page in CA Clarity System Administration shows the database as installed, even though it is.

This behavior does not affect your ability to complete the installation and use the application.

Upgrade Action: To get details of the database, run the query CMN_INSTALL_HISTORY.

Generic J2EE Upgrade Produces an Error If the J2EE.home Property Is Not Set

An error is received during an upgrade for a generic J2EE application server (IBM WebSphere). Because the vendor is generic, the prompt for the J2EE home directory does not appear and the j2ee.home property is not set. Without a j2ee.home setting, an error occurs in the installation process.

Upgrade Action:

Set the following values in the <installer>/install.properties file:

  • j2ee.home=<any value>
  • j2ee.vendor=generic

An Upgrade With a Non-RAC Database Results in a Disconnect Between the Application Server and the Database

If you are upgrading to Release 13.2, 13.3, or 14.1 with a non-RAC database, the network between the application server and the database disconnects during the upgrade. You see the following error:

FATAL 2013-07-17 13:14:46,376 [main] union.persistence Failed to initialize Context properties
7/17/13 1:14 PM (admin)                 java.sql.SQLNonTransientConnectionException: [CA Clarity][Oracle JDBC Driver]Connection reset
7/17/13 1:14 PM (admin)        at com.ca.clarity.jdbc.oraclebase.ddcg.b(Unknown Source)
7/17/13 1:14 PM (admin)        at com.ca.clarity.jdbc.oraclebase.ddcg.a(Unknown Source)
7/17/13 1:14 PM (admin)        at com.ca.clarity.jdbc.oraclebase.ddcf.b(Unknown Source)
7/17/13 1:14 PM (admin)        at com.ca.clarity.jdbc.oraclebase.ddcf.a(Unknown Source)
7/17/13 1:14 PM (admin)        at com.ca.clarity.jdbc.oraclebase.ddcf.a(Unknown Source)
7/17/13 1:14 PM (admin)        at com.ca.clarity.jdbc.oracle.net8.dd g.b(Unknown Source)

Upgrade Action:

Before you start the upgrade, complete the following steps:

  1. Open CA Clarity System Administration, and click Servers in the left pane.
  2. Click the name of the application server.
  3. Click the Database subtab.
  4. In the Internal Connection: Niku section, select the Specify URL check box.
    The JDBC text box appears.
  5. Add the following tags to the JDBC URL:

    ConnectionRetryCount=400;ConnectionRetryDelay=3
    
  6. Click Save.

Google Chrome Version 30.0.1599.66 m Issues

The following CA PPM issues occur for users who are using this particular version of Chrome (Version 30.0.1599.66 m):

  • The Recent Pages (History) drop-down that lets you navigate back to previously viewed pages does not work.
  • Export to Excel and Export to PowerPoint do not work at the portlet level.
  • Export to Excel does not work on a list page.

These issues do not appear in other browsers and have been found only in this version of Chrome.

Gantt Printing Issue with Chrome

If you use Chrome, the following issues can occur when you print a Gantt chart:

  • Some rows have extra space after the row.
  • Some lines break across pages, presenting part of the line on two pages.
  • The Gantt schedule lines do not appear correctly.

This issue does not occur in Internet Explorer or Firefox.

Using the Value -1 to Disable the New XOG Governor Limit Does Not Work Correctly for XOG Write

Setting the Maximum XML Node Limit value to -1 in CA Clarity System Administration disables the XOG Governor limit. Currently, entering this value causes XOG write operations to throw the following error:

XOG-9060: The system cannot import this instance with the current configuration. Increase the 'Maximum XML Nodes' value in the CSA and try again. 

Workaround: Set the Maximum XML Node Limit to 10^15.puttin

Rate Matrix Extraction Job's Scheduled Instances and Job Logs Deleted

During an upgrade from a 12.x release to a 13.0 or higher release, the Rate Matrix Extraction job’s scheduled instances and job logs are deleted.

Upgrade action: Reschedule the Rate Matrix Extraction job.

Microsoft Project 2013 Do Not Install Service Pack 1

The CA PPM Legacy MSP Interface option does not support the Microsoft Project Service Pack 1.

Service Pack 1 for Microsoft Project 2013 has a known issue that affects how it works with CA PPM. The following behavior results when the service pack is installed:

  • Baselined projects cannot be opened with Microsoft Project 2013. The Visual Basics run-time error '91' is received.
  • All the actuals are zeroed out when you launch a project from CA PPM to Microsoft Project 2013.

For more information, see the following Knowledge Base articles on CA Support Online: TEC610737, TEC615024.

Note: Microsoft Project 2013 Service Pack 1 is supported for integration with the new CA PPM Release 14.2 MSP Interface option.

Upgrade Action: Do not apply Service Pack 1 to Microsoft Project 2013 if you are using the CA PPM Legacy MSP Interface.

Add-in Enhancements for Release 14.1

Here are the add-in enhancements for Release 14.1.

VersionOne Connector

The CA PPM VersionOne Connector provides project managers visibility into agile projects and eliminates dual-time entry. Managers can track CA PPM projects effectively, along with the allocated cost, resources, and time. Portfolio managers can do top-down planning with increased project transparency.

Note: For information about installing this connector, see Installation.

Upgrade Action: None

Administration Changes for Release 14.1

Here are the Administration updates for Release 14.1.

Added Security for Webroot Folder Data

Before this release, storing an HTML page in the webroot folder could make the contents of that folder vulnerable to someone without proper credentials. For example, if you store index.html in the webroot folder, an unauthorized person could gain access to CAPA information without logging in. All the user needs is the server and port number: http://<servername>:<portnumber>/niku/index.html.

To resolve this issue, a new servlet filter (ClarityContentFilter) was introduced. The filter is registered in the following file: <installfolder>/tomcat-app-deploy/conf/web.xml. This servlet prevents users from accessing a page, image, script, or any other file without logging in to the product.

Note the following points about ClarityContentFilter:

  • You can exclude webroot files from the filter using a ClarityContentFilter parameter named allowedList. This parameter allows some items to be excluded from the filter. If you want the webroot folder to be excluded, you can append it to the allowedList parameter separated from other items by a comma. Redeploy the app service when you change the allowedList parameter.
  • You can disable the filter by adding the following value to the Java VM parameters of the app server:
    -DdisableContentFilter=true.

Upgrade Action: None

Apache Tomcat Log Analysis

The following jobs have been added to create and manage data that you can use to analyze performance in an Apache Tomcat environment. You can add custom portlets, queries, or externally available content to provide details regarding system performance. Although the job runs for application servers other than Tomcat, no data is created.

  • Tomcat Access Log Import/Analyze Job
    This job imports and analyzes Tomcat access log files from the local CA PPM environment (all app services). The job stores and summarizes the data in the following designated tables:
    • LOG_DETAILS
    • LOG_SUMMARY
    • LOG_FILES
    • LOG_REPORTDEFS
  • Delete Log Analysis Data Job
    This job removes the analysis-related data that is stored in CA PPM. The criteria for removing the data is the LOG_DATE on each of the log analysis tables.
    The job is scheduled to run automatically at 1:00 A.M. each day.

Upgrade Action: None

Character Limit for Audited Multi-Valued Lookups Increased

Before Release 13.2.0.1, ODF_AUD_VALUE_FCT returned a value of type Varchar2. With the release of 13.2.0.1, the returned value type was changed to CLOB. This change increases the number of characters that are allowed for auditing multivalued lookups from 4,000 to an unlimited number of characters.

Upgrade Action: Update any reports or portlets that use ODF_AUD_VALUE_FCT.

Limit the Number of Rows for Export to Excel

System administrators can limit the maximum number of rows that can be exported to Excel. A new field in Clarity System Administration provides a safeguard against the export of unlimited or large amounts of data which can affect system performance.

An individual user with the appropriate access rights can control the number of rows that are exported to Excel using a setting in CA PPM. However, the setting in CA PPM does not override the setting in Clarity System Administration. From CA PPM, the number of rows that are exported is managed by entering a value in the Maximum rows for Export to Excel field. The field is available from Administration, General Settings, System Options. Previously, if no value was entered in the field, an unlimited number of rows could be exported to Excel.

Note: If you are a new customer, the default setting for the number of rows that can be exported is 25,000.

Upgrade Action: Place a practical limit on the number of rows of Excel data that can be exported.

  1. Log in to Clarity System Administration.
  2. Click Servers in the left pane, and click the name of the server.
  3. On the Properties tab, click the Application subtab.
  4. Enter a value in the Maximum rows for Export to Excel field and click Save.
  5. To place the changes in effect, restart the services.

Remove Session IDs from Log Files

As a security measure, you can configure CA PPM to prevent session ID values from appearing in your log files. To prevent these values from appearing, edit the logger.xml file. Replace the log pattern (%u:%s:%a) with the pattern (%U:%a).

The following examples show the results of using both log patterns in the logger.xml file.

Example: (%u:%s:%a)

This line of code shows how the pattern to display the session ID value appears in the logger.xml file.

<param name="ConversionPattern" value="%-5p %d{ISO8601} [%t] %c{2} (%u:%s:%a) %m\r\n"/>

This pattern produces records in a log file with the session ID value. The following record from the app-ca.log that shows the session ID value (bolded):

DEBUG 2014-08-18 19:52:02,949 [http-bio-80-exec-3] odf.view (clarity:admin:5077018__8DF3B2A0-F398-4A4B-BC35-E9A012065CE0:npt.overview) Adding view FILTER_VIEW_LOADER::USER:NIKU.ROOT to transient cache

Example: (%U:%a)

This line of code shows how the pattern to prevent the session ID value appears in the logger.xml file.

<param name="ConversionPattern" value="%-5p %d{ISO8601} [%t] %c{2} (%U:%a) %m\r\n"/>

This pattern produces a record in a log file without the session ID value. The following example is a record from the app-ca-service.log that shows no session ID value.

DEBUG 2014-08-18 19:52:02,494 [http-bio-80-exec-3] in.service (admin:npt.overview)

CA PPM supports additional logging patterns included in the following table if the layout is set to NikuLayout in the logger.xml for an appender.

Pattern Option Purpose
u

Creates the user ID with the tenant ID in the log.

Example: (%u) creates the output (clarity:admin) in the log.

U

Creates the user ID in the log.

Example: (%U) creates the output (admin) in the log.

s

Creates the session ID in the log.

Example: (%s) creates the output (5077018__8DF3B2A0-F398-4A4B-BC35-E9A012065CE0) in the log.

a

Creates the action ID in the log.

Example: (%a) creates the output (npt.overview) in the log.

Note: For more information about log4j version 1.2 supported patterns, see the API documentation for Class PatternLayout at https://logging.apache.org.

Set Options for Cross-Site Scripting (XSS) Vulnerability

Cross-Site Scripting (XSS) attacks insert malicious scripts into otherwise trusted web sites. A cross-site scripting attacker uses a web application to send malicious code, generally in the form of a browser side script, to an end user. These attacks succeed when a web application uses input from a user in the output it generates without validating or encoding the input.

You can set options to validate user input. With input validation, CA PPM compares the user input to a set of commonly used XSS string patterns. If any part of the user input matches one of the common patterns, CA PPM restricts the XSS string in the user input. The product restricts the XSS string by placing escape characters before and after the string.

The escape characters are visible to the end user. The characters instruct the browser to ignore any script or HTML tag that is attached to the user input. This output encoding ensures that the user input is treated as text and not active content that can be executed. This action helps ensure user input that is returned to the browser is safe from XSS.

Set Up User Input Validation

The XSS options let you manage the escaping of user input values in the application, URL attributes, and site links. You can also add extra patterns to be escaped.

Important! The XSS detection is turned on by default; however, site links and URL attributes are exempted from this detection. To turn on XSS detection for site links and URL attributes, modify the options that are described in the following section.

To change the setting for any option, you execute database SQL statements.

Follow these steps:

  1. Access the CMN_OPTION_VALUES database table.
  2. Update the table entry for the particular option. For information about each option, see the option descriptions.
  3. Flush the cache.

Cross-Site Scripting Options

The following options apply to user input validation.

  • RESTRICT.APP.XSS (XSS Restriction Option)
    Restricts the XSS string in the user input when the string matches a pattern in the CMN.XSS.PATTERNS option. This system option applies to the entire application, except the URL attributes and site links. You can set restrictions for URL attributes and site links through separate options.
    Values: True (restrictions are on), False (restrictions are off)
    Default: True

    Note: The HtmlPortlet content is not restricted (escaped). The HTML portlets execute any script in HTML content, which is the expected behavior.

    To change the RESTRICT.APP.XSS option, update the CMN_OPTION_VALUES database table using the following SQL statement:

    update cmn_option_values set value='false|true' where option_id = (select id from cmn_options where option_code=' RESTRICT.APP.XSS') 
    
  • RESTRICT.URL.ATTR.XSS (URL Attribute Value Option)
    Restricts the URL attribute value (that you created with Studio) when the value matches a pattern in the CMN.XSS.PATTERNS option.
    Values: True (restrictions are on), False (restrictions are off)
    Default: False
    To change the RESTRICT.URL.ATTR.XSS option, update the CMN_OPTION_VALUES database table using the following SQL statement:

    update cmn_option_values set value='false|true' where option_id = (select id from cmn_options where option_code=' RESTRICT.URL.ATTR.XSS') 
    
  • RESTRICT.SITE.LINKS.XSS (Site Links Option)
    Restricts the site links entry value when the value matches a pattern in the CMN.XSS.PATTERNS option.
    Values: True (restrictions are on), False (restrictions are off)
    Default: False
    To change the RESTRICT.SITE.LINKS.XSS option, update the CMN_OPTION_VALUES database table using the following SQL statement:

    update cmn_option_values set value='false|true' where option_id = (select id from cmn_options where option_code=' RESTRICT.SITE.LINKS.XSS')
    
  • CMN.XSS.PATTERNS (Common XSS Patterns Option)
    Defines the string patterns that are commonly used for XSS. You can modify this option to add more string patterns.
    To add patterns, access the CMN_OPTION_VALUES database table and include the new patterns in the CMN.XSS.PATTERNS option.
    String patterns =
    </script>
    <script(.*?)>
    <script>(.*?)</script>
    alert(.*?)
    eval\\((.*?)\\)
    expression\\((.*?)\\)
    javascript:
    onerror(.*?)=
    onload(.*?)=
    src[\r\n]*=[\r\n]*\\\"(.*?)\\\"
    src[\r\n]*=[\r\n]*\\\'(.*?)\\\'

Example: Adding a new pattern

The following example statements add the new pattern onfocus to the CMN.XSS.PATTERNS option:

Oracle:

CMN_OPTION_VALUES_INS_SP('CMN.XSS.PATTERNS','true','true','onfocus(.*?)=',1); 

MSSQL:

EXEC CMN_OPTION_VALUES_INS_SP 'CMN.XSS.PATTERNS','true','true','onfocus(.*?)=',1

Upgrade Action: None

Action Item Localization

You can translate action item names and descriptions that are associated with processes. The advantage is that recipients see the action item in the language set for them.

For example, as the process creator, you translate an action item into all CA PPM supported languages. When the process is executed, the user working in CA PPM in French sees the action item in French. The user working in CA PPM in Turkish sees the action item in that language. This change improves the user experience because the action item is seen in the appropriate language.

You can translate an action item by using the translation icon that appears next to the Action Item Name field. The icon appears after the page for the action item is saved. Clicking the icon opens a dialog that lets you specify different language translations for the Action Item Name and Description fields.

Note: The Action Item translation icon is intended as an administrative tool and appears only for action items that are related to processes. The icon is not available to action item operations that end users perform from the Home menu.

Upgrade Action: None

Financial Management Changes for Release 14.1

Here are the Financial Management updates for Release 14.1.

Ignore Non-Labor Resources and Roles on Auto Population

A new option provides a way manually to forecast and preserve planned units, cost, and revenue for non-labor resources. The new option, Ignore Non-Labor Resources/Roles in Cost Plan Population, is available on the System Options page.

When this option is selected, team allocation or assignment ETC from non-labor resources and roles is skipped during the autopopulation of a cost plan. For example, Populate from Investment Team. When the option is unselected, cost plan population functions as it has in previous releases. In this case, all data for an investment is included in the cost plan. The option is unselected by default.

Note: This option setting affects any autopopulation action that is run against a new or existing cost plan. Ensure that you understand whether your business needs require non-labor resources and roles for autopopulation.

To navigate to the option, open the Administration menu, and from General Settings, click System Options. The option is located in the section named Other.

Here are some facts and tips on using this enhancement:

  • We recommend setting the option once and setting up a business procedure for your users to follow. Do not reset this option frequently. Changing the setting can lead to data discrepancy.
  • An unplanned row from a non-labor resource is included in a cost plan because the process is actual-driven. An unplanned row is one that shows actuals but no planned units or cost. This situation occurs when actuals are posted before a planned row has been added to the cost plan either manually or through cost plan population. The application has worked this way in the past, and selecting the option does not change this behavior.
  • No existing cost plan row for a non-labor resource added manually is deleted on cost plan repopulation. However, if cost plan population added a row previously, the row is deleted during cost plan repopulation. The application has worked this way in the past, and selecting the option does not change this behavior.

Best Practice: We recommend creating new cost plans to start manually forecasting non-labor resources once the option is selected. This course is more prudent than repopulating existing plans because you cannot determine how a row was originally inserted into a cost plan.

Upgrade Action: None

Length of Money Fields

The value entered in any money field (including custom money fields) is limited to 18 digits. Any value you enter after the 18th digit changes to a zero.

Upgrade Action: None

Change in the Resource Browse Field for Rate Matrix

Before this release, you could select a role or a resource as a value for the Resource field in a rate matrix. The Resource field browse incorrectly showed both resources and roles as selection options. The browse has been corrected to show only resources for the Resource field.

To add financially enabled roles to a rate matrix, use the Resource Role field.

You cannot import a role in the resource code field through the XML Open Gateway (XOG). If the XOG input XML file contains roles in the resource code field, the following error is thrown: REVMGR-20299: Role in Resource code.

Correct any matrix rows with a role in the Resource field. Incorrect matrix rows cause an error when you try to create a cost plan in an investment using roles and resources. In this case, the following error is thrown: REVMGR-20728:Rates and Costs are both missing for one or more roles/resources.

Upgrade Action: Manually update incorrect rate matrix rows.

  1. To discover any roles that have been assigned to a rate matrix incorrectly, run the checkinstall script.
    The checkinstall script logs any rate matrix rows that have an incorrect role assignment in the Resource field. The following format for the error is given in the log file: Rate Matrix Name, From Date, To Date, and Role.
  2. Open the rate matrix in CA PPM and manually update the Resource field with the correct resource value.

Open Workbench Changes for Release 14.1

Here are the Open Workbench updates for Release 14.1.

Cell Text Wrapping

If you enter text in Open Workbench table cells and the text is larger than the cell width, the text now wraps. This enhancement ensures that the text that you enter from Open Workbench is always visible completely.

Note: This feature is not available when a project is opened from CA PPM into Open Workbench.

Upgrade Action: None

Estimate to Complete (ETC) Auto-Calculation

In previous releases, when you assigned a resource to a task in Open Workbench, the ETC was not automatically calculated. With this release, you can configure Open Workbench to calculate ETC automatically. A new field named Auto Calculate ETC has been added to Open Workbench. The automatic calculation applies to all resource assignments that you perform in Open Workbench. You can view and manage these automatically calculated ETC values in both CA PPM and Open Workbench.

By default, the Auto Calculate ETC check box is not selected. To make this option available, you are required to select it.

Note: For more information about the Auto Calculate ETC option, see Open Workbench.

Upgrade Action: None

Project Management Changes for Release 14.1

Here are the Project Management updates for Release 14.1.

New Microsoft Project Driver

A new Microsoft Project Interface driver (XML-based) is available for you to select during the installation of the Microsoft Project Interface. You can also select the existing legacy driver, which is COM-based. The two driver versions are available for both 32-bit and 64-bit environments.

If you install Microsoft Project Interface from the CA PPM user interface, a wizard guides you through the installation for both driver versions.

Upgrade Action: None

Studio Changes for Release 14.1

Here are the Studio updates for Release 14.1.

Studio Content Management

You can collect specific CA PPM content in a content package. Content packages help you identify, assemble, export, and deploy content between development, test, and production systems. A content package also lets you distribute to external third parties. Recipients can import the content as an add-in in their environments and can use the content. For example, you can develop a series of pages, portlets, and queries and can offer them to internal users and external customers.

When you export a content package, the application creates .jar files. The XML Open Gateway (XOG) allows you to migrate these package files to other environments. As a developer, you can design content items, package them for export, and then import them in to another environment.

You can also import Studio content packages that were developed internally or by third parties. Studio content packages extend the functionality of the application.

Note: For more information about Studio content management and the required access rights, see Studio Development.

Upgrade Action: None

User Interface Changes for Release 14.1

Here are the user interface updates for Release 14.1.

Smart Sections

If you have multiple sections on a page with numerous fields on some sections, you can now manage sections easier. In this release, the section header bar acts as a switch to expand or collapse the section. The section header bar also helps you identify the sections with required fields or errors that occur upon saving.

The following changes improve the way page sections operate:

  • To open or close all sections on a page, double-click any section header bar.
  • To open or close a single section, click the section header bar for the section.
  • The header bars for any sections that contain errors when you save are highlighted with a red border.
    If all sections are collapsed, the first highlighted section is expanded for you to make corrections. To make corrections in any remaining highlighted sections, click the section header bar to open the section.
  • Any sections that contain required fields display the Required icon on the header bar. If the section contains empty required fields, the icon displays brightly. If all required fields are completed, the icon displays in a dimmed format. This display lets you scan the sections even in the collapsed state to identify which ones contain required fields that need completing.

When you close a page, the status of the sections is saved. The next time that you open the page in the same browser, it appears as you left it. If you change browsers, the status of the sections is not saved and the standard presentation of sections (all open) appears.

The following pages or page components do not have to smart sections:

  • The properties page for a report or job.
  • The System Options page. To see this page, open the Administration menu, and from General Settings, click System Options.
  • Time-scaled value sections. Although time-scaled values resemble sections, they are not true sections and are not included in these changes.

Upgrade Action: None

Change to Page Menu Behavior

The following changes improve the way menus on pages operate:

  • A tab menu now displays when you mouse over the tab. Previously, you clicked the down arrow to see a tab menu. The menu closes automatically when the cursor moves off the menu.
  • Other menus (for example, Actions, Scenario, or Open in Scheduler) open when you mouse over the menu name. In this case, the menu stays open until you click in an area outside the menu.

Upgrade Action: None

Data Model Changes for Release 14.1

Here are the data model changes for Release 14.1.

Added Tables

The following tables were added for this release:

  • CMS_CONTENT_ADDIN_ITEMS
  • CMS_CONTENT_ADDINS
  • CMS_CONTENT_ITEMS
  • CMS_CONTENT_PACKAGES
  • CMS_CONTENT_TYPES
  • LOG_DETAILS
  • LOG_FILES
  • LOG_REPORTDEFS
  • LOG_SESSIONS
  • LOG_SUMMARY

Updated Tables

The following tables were updated for this release.

CAL_ACTION_ITEM_ASSIGNEES

Added columns:

AI_DESCRIPTION

AI_SUBJECT

CMN_INSTALL_HISTORY

Updated column:

INSTALL_ID

CMN_NOTES

Updated column:

SUBJECT

CMN_NOTIFICATIONS

Added column:

IS_ADMIN_VISIBLE

PRASSIGNMENT

Added column:

ODF_SS_ACTCOST_CURVE

Added index:

PRASSIGNMENT_GN1

PRDEPENDENCY

Added column:

PRLAGFORMAT

RPT_CALENDAR

Added columns:

CREATED_DATE

LAST_UPDATED_DATE

RPT_INV_HIERARCHY

Added columns:

CREATED_DATE

INV_HIERARCHIES_ID

RSM_SKILLS

Updated column:

SKILL_NAME

Dropped Tables

No tables were dropped in this release.

XML Open Gateway (XOG) Changes for Release 14.1

Here are the XOG updates for Release 14.1.

Changes to the writeFile GEL tag

The behavior of the GEL tag writeFile has been changed when the tag is used with the line tag. With this release, each call to the line tag writes the line to the specified output file. This change prevents potential out of memory issues when you run the GEL script. You can override the new behavior by specifying bulkWrite="true" on the writeFile tag.

Note: For writeFile examples, see XML Open Gateway (XOG) Development.

The following example shows the writeFile GEL tag.

 <f:writeFile 
    fileName="projectData.txt" <!-- filename is required -->
    delimiter="&#x9;" <!-- If not specified this is set to a comma (',')
    writeBulk="false" <!-- write one line at a time to the output file. This is the default behavior. If it is desired to have the result written at the end of the request set       writeBulk="true" -->
    maxFileSize="1g"  <!-- the maximum file size allowed when bulkWrite="false". 1G is the default; valid examples are 1024k, 250 m, 2g. -->
    >
  <gel:forEach select="myQuery" var="row">
        <f:line>
          <f:column value="${row.ID}"/>
          <f:column value="${row.NAME}"/>
        </f:line>
  </gel:forEach>
  </f:writeFile>

Upgrade Action: None

XML Open Gateway Output File is Not Indented

Starting with Release 13.3, the XOG client output is unformatted without line breaks or indentation. You can use third-party software to convert the output to a more readable, user-friendly format.

Upgrade Action: None

Was this helpful?

Please log in to post comments.