This section provides known issues for CA Clarity PPM Release 14.2.
The Advanced Reporting repository folder structure and its items (such as domains, reports, input controls, and templates) are not localized. The Public, Shared, Temp, Themes, and Users folders are also not localized. The out-of-the-box items that are available in these folders are not localized. The item names and their descriptions display in English for all languages. Input Controls (that are used as filters in reports) display the $R expression that is used by Jaspersoft for localization. This expression is only converted when running the reports. However, the report output is fully localized.
The names of custom subobjects that are dynamically updated in Advanced Reporting domains are not localized. As a result, the names are not localized in ad hoc views either. The names appear in the language selected when the subobjects were created. However, the custom master object names are localized.
If you change languages while you are in your current product session (that is, you do not log out), the data in Advanced Reporting is not completely localized. To resolve this issue, log out of CA Clarity PPM after changing the language setting and log in again. The data then appears in the new language.
If you set up multiple email addresses for Advanced Reporting Notifications and one of the email addresses uses an incorrect format, none of the email addresses receives the notification. Also, if you have addresses in both the "To" and the "CC" fields and one of the addresses has an incorrect format, no email is sent to any address in the two fields. This issue applies to the "Send report when scheduler runs" and the "Send job status notifications" sections of the Advanced Reporting report schedule Notifications tab.
If you export a report to PDF and then view the report in your browser, the report output data does not display charts, maps, and other widgets. However, if you download the exported PDF and open it in Adobe Reader, the charts and other widgets are shown.
To see the charts and widgets in the browser PDF, enable the Adobe Reader plug-in for your browser. Also, make sure you disable any other PDF reader plug-in.
When you schedule an Advanced Reporting report using Create Schedule and you select a date using the date selection calendar for On Specific Date, you can receive an error when you save the schedule. However, you are able to select a specific date for your schedule for the following languages: English, Japanese, Italian, Polish, Brazilian Portuguese, Swedish, Traditional Chinese, and Simplified Chinese. For all other supported languages, you cannot set a specific schedule date.
Advanced Reporting allows you to schedule a report PDF, save the output to the repository, and send notifications about the report. If you select "Include reports as repository links in email body" when you set up the Notifications, the PDF appears collapsed (in small size) on the browser after the user clicks the email link. This issue occurs with Internet Explorer and Mozilla Firefox.
When you are creating or editing an Advanced Reporting ad hoc view, you can use the filter fields to limit the selection options. However, the filter lists are not auto-populated with selection results based on your search criteria. No results appear. This issue occurs in Oracle database environments.
The following output options, which are available for selection when you create or edit a report schedule, have issues regarding their format or content:
When you run a report using Advanced Reporting, you can select report options, which display as drop-down lists on the left of the report page. These options let you filter the data in your report. At times, these options do not display all of the selections available in the database. This issue occurs when the data displayed by the report options has been updated after you logged in to your current session. To resolve this issue, log out of CA Clarity PPM and log back in again. The data displays correctly then.
The sender email address is the address that appears when JasperSoft sends an email notification for a scheduled report. JasperSoft lets you set the sender email address at the JasperSoft Reporting Server (JRS) level, but not at the tenant (organization) level.
The following address is the default sender email address value for the JasperSoft reporting server for On Premise implementations:
do-not-reply@your_domain.com
For information about changing this default value during installation, see the Installation Guide.
To change the default value after installation, perform the following steps:
After Jaspersoft installation, the administrator configures Jaspersoft using CA Clarity System Administration (CSA). During this configuration, generate a key store using the following command:
admin jasper keystore
However, if the Organization Name field (in the CSA, Reporting tab, Jaspersoft section) is blank, the resulting key store is also blank.
You can resolve this issue by updating the Organization Name field in CSA and running the command again.
The reports for the EVMS and the PMBOK add-in are not available as Jaspersoft reports.
When you baseline your project in Microsoft Project and then import it back to CA Clarity PPM again, the baseline costs are ignored when saved to CA Clarity PPM. The baseline costs include project, assignment task, and team. This situation occurs with the Microsoft Project Interface (newer version). To resolve this issue and as a best practice, update your baseline in CA Clarity PPM only.
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
)
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 Clarity 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.
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.
CA Clarity 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 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.
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:
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:
Note: For more information about creating an action menu, see the Studio Developer Guide.
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.
You cannot export report instances from the report library when the BusinessObjects server is configured with CA Clarity 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 Clarity PPM integration are not compatible with Windows 2012.
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.
If you are using the Oracle Enterprise Edition compression feature, disable the compression feature before starting the CA Clarity 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:
SELECT TABLE_NAME, COMPRESSION FROM USER_TABLES WHERE COMPRESSION='ENABLED';
SELECT 'ALTER TABLE ' || TABLE_NAME || ' MOVE NOCOMPRESS;' FROM USER_TABLES WHERE COMPRESSION='ENABLED';
SELECT 'ALTER INDEX ' || INDEX_NAME || ' REBUILD;' FROM USER_INDEXES WHERE STATUS='UNUSABLE';
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:
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.
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:
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:
The JDBC text box appears.
ConnectionRetryCount=400;ConnectionRetryDelay=3
The following CA Clarity PPM issues occur for users who are using this particular version of Chrome (Version 30.0.1599.66 m):
These issues do not appear in other browsers and have been found only in this version of Chrome.
If you use Chrome, the following issues can occur when you print a Gantt chart:
This issue does not occur in Internet Explorer or Firefox.
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
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.
The CA Clarity 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 Clarity PPM. The following behavior results when the service pack is installed:
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 Clarity 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 Clarity PPM Legacy MSP Interface.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|