Release 13.0 Updates › Upgrade Considerations for Version 13.0

Upgrade Considerations for Version 13.0

This section provides information about installation and upgrade changes for Version 13.0.

New Log File Names

Log file names have changed. Previously, log files had the name format *-niku.log (for example, bg-niku.log). This format has been changed to *-ca.log (for example, bg-ca.log).

Dropped Languages

The following languages are not available for CA Clarity PPM v13:

• Korean
• Simplified Chinese
• Traditional Chinese

During an upgrade, existing users of these languages are reset to use English.

Upgrade Action: None

About Add-ins and Upgrades

Note the following actions to be taken after you have add-ins or connectors upgraded:

• Apply the Upgrade Ready content for those items that you are actively using.
• Best Practice: If you modified stock CA Clarity PPM content, copy the modified content before upgrading, apply the new incoming stock CA Clarity PPM content, and then retrofit the modifications to the new content.
• Read the PMO Accelerator Release Notes for important information about what has changed for PMO Accelerator v3.0.
• Review the System: Clarity Content add-in for upgrade ready content (for example, Role Capacity portlet). Apply the changes to accept the new v13.0 upgraded content.
• Review the Studio views and system content and manually upgrade as needed.

  The upgrade preserves all pre-existing Studio view configurations. If an existing view has configurations or if the object for the view is partitioned, the system does not automatically upgrade the view and/or the partition.

  Use the Studio Views list page to determine which views were not automatically upgraded.

  Some tips on reviewing the views:

  • The Last Version column identifies changes to stock views in CA Clarity PPM v13.
  • If a view was automatically upgraded as part of the upgrade process, a check mark appears in the view's Upgraded column. No further action is required.
  • If a view was changed in CA Clarity PPM v13 but was not upgraded due to pre-existing configurations, decide if you want to apply the changed view.

    Look for views with the following:

    Last Version column=13.0 and the Upgraded column= unchecked.

• Verify your NSQL queries.

  During the upgrade, the NSQL validator script automatically checks NSQL queries. Results are written to the admin.log. This log contains:

  • Query name
  • Query ID
  • Content Source
  • Query ID from CMN_NSQL_QUERIES of the query that failed validation

  There are database schema changes in this release. You must correct invalid NSQL queries for portlets to work. See the chapter in this document named "Data Model Changes."

  Upgrade action:

  If the query can be changed in Studio:

  1. Go to the NSQL tab for each failing query.
  2. Click the Preview button.
  3. Review the errors.
  4. Repair the broken query constructs or fields.
  5. Click the Preview button.
  6. Confirm the NSQL query is valid.

If the query is in use by active portlets and cannot be edited in Studio:

1. User the XML Open Gateway (XOG) to export the failing query.
2. Correct the broken query constructs or fields.
3. Use XOG to import the corrected query.
4. Click the Preview button.
5. Confirm the NSQL query is valid.

Changes to Existing CA PPM Universes

The following changes were made to the existing CA PPM Investment Financials universe to support the v13.0 database schema:

• Added derived tables to the universe to mirror the Group By and Sub-Group By in the Financial Plans for Cost and Budget.

  SELECT l.pk_id cost_plan_id,
         MAX(CASE WHEN l.seq = 0 THEN
                  CASE WHEN value = 'charge_code_id' THEN 'LOOKUP_CHARGE_CODES'
                       WHEN value = 'role_id' THEN 'SCH_BROWSE_ROLE'
                       WHEN value = 'transaction_class_id' THEN 'FIN_TRANSCLASSES'
                       WHEN value = 'lov1_id' THEN 'FIN_BROWSE_USER_LOV1'
                       WHEN value = 'lov2_id' THEN 'FIN_BROWSE_USER_LOV2'
                       ELSE NULL END
                  ELSE NULL END) AS plan_by_1_code,
         MAX(CASE WHEN l.seq = 0 THEN ln.name ELSE NULL END) AS plan_by_1_name,
         MAX(CASE WHEN l.seq = 1 THEN
                  CASE WHEN value = 'charge_code_id' THEN 'LOOKUP_CHARGE_CODES'
                       WHEN value = 'role_id' THEN 'SCH_BROWSE_ROLE'
                       WHEN value = 'transaction_class_id' THEN 'FIN_TRANSCLASSES'
                       WHEN value = 'lov1_id' THEN 'FIN_BROWSE_USER_LOV1'
                       WHEN value = 'lov2_id' THEN 'FIN_BROWSE_USER_LOV2'
                       ELSE NULL END
                  ELSE NULL END) AS plan_by_2_code,
         MAX(CASE WHEN l.seq = 1 THEN ln.name ELSE NULL END) AS plan_by_2_name
  FROM   odf_multi_valued_lookups l
         LEFT OUTER JOIN cmn_lookups_v ln ON l.value = ln.lookup_code
                                         AND ln.lookup_type = 'LOOKUP_FIN_GROUPING_ATTRIBUTES_CAPTIONS'
                                         AND ln.language_code = @Prompt('param_language','A',,mono,free,,{'en'}
  WHERE  l.attribute = 'grouping_attributes'
  AND    l.seq IN (0,1)
  GROUP BY l.pk_id
  

• Changed the links in the Investment Financials Universe for budget plan details and cost plan details. The previous fields were different from the new v13 fields:

The Legacy Universe has been updated to remove references to fields that have been changed or are no longer in the Clarity data schema.

Note: See Data Model Changes for Version 13.0 for a list of changed and deprecated fields.