Change Impact and Upgrade (On Demand)

HID_release_info_change_impact_od
ccppmod142
HID_release_info_change_impact_od
Plan the 
Clarity Project and Portfolio Management (PPM)
upgrade and determine the upgrade options for your business needs. As the administrator and implementer, use this information to plan your training and rollout efforts. Complete information for the current release and summary information for previous releases is provided here. The complete 
Change Impact and Upgrade 
content
 
for a specific 14.x release is available by selecting a release in the Versions drop-down on this page. Content before 14.x is available on the Documentation page of CA Support Online.
This article covers the following topics:
  • Pre and post-upgrade steps
  • Features and enhancements for the current and previous releases and the upgrade actions that they require
  • Known issues
If you are upgrading from an earlier release, review the information for the updates in Release 14.2, Release 14.1 and the 13.x releases.
Contents
2
 
Add-ins Compatibilities
Review this important information about upgrading installed add-ins, accelerators, and connectors.
  • If you are upgrading from a 13.x release to this release, the following add-ins are upgraded, if deployed:
    • PMO Accelerator
    • Clarity Project and Portfolio Management (PPM)
       Solution Pack (CSP)
    • CA Agile Planning
    • Connector for Microsoft SharePoint
  • If you are upgrading from any version before Version 13.0 to this release, all installed add-ins are upgraded.
The following table includes the accelerator and connector releases that are installed with Release 14.2.
Accelerator or Connector
Upgraded Version
PMO Accelerator
14.2.0
Clarity Project and Portfolio Management (PPM)
Solution Pack (CSP)
14.2.0
Earned Value Manager
2.0.2
Accelerator for PRINCE2
2.0.2
Accelerator for the PMBOK
2.0.2
Accelerator for New Product Development
2.0.3
BRM Accelerator
3.0.2
Connector for CA Unicenter Service Desk & CA Software Change Manager™ for Distributed
2.0.1
Connector for Microsoft SharePoint
3.0.0
Service Connect
2.0.0
Catalyst Connector
2.5.0
CA Agile Planning
14.1.0
Integration Adaptor
14.1.0
VersionOne Connector
14.1.0
Java 7
This release uses Java 7. The following software client requires Java 7:
  • XML Open Gateway (XOG) client
Clarity Project and Portfolio Management (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.
The Java Runtime Environment (JRE) is updated frequently with fixes for security issues, including issues that are unknown at the time 
Clarity Project and Portfolio Management (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 Actions
: Install Java 7 on workstations that have the software clients for which 
Clarity Project and Portfolio Management (PPM)
 does not provide the JRE.
See also End of Service Announcement for 
Clarity Project and Portfolio Management (PPM)
 and Oracle Java 7.
Clarity Project and Portfolio Management (PPM)
 is not affected by the January 2013 Java vulnerability (CVE-2013-0422: Oracle Java 7 Security Manager Bypass Vulnerability). For more information please contact your administrator.
Automatic Update to Special Characters in OBS Unit Names during Upgrade
While you are upgrading, the preinstallation log can show a warning message about the special characters that are not allowed in the OBS Unit Names. This warning message is displayed in the precheck-results.xml file. The following characters are the special characters for which the warning is shown:
  • Slash (/)
  • Colon (:)
  • Double quote (")
  • Less than (<)
  • Greater than (>)
If the administrator does not replace the special characters with the valid character (hyphen "-") before upgrading, the upgrade automatically replaces the characters with the hyphen.
If you do not want hyphens placed in names with special characters, update the names during the preinstallation check before you begin the upgrade process.
If you have an existing installation, you have two options for how to proceed before upgrading to 
Clarity Project and Portfolio Management (PPM)
 Release 14.2.
CA Productivity Accelerator (CA PA) Version 11.1
If you have CA PA Version 11.1, install a patch to make the player package compatible with 
Clarity Project and Portfolio Management (PPM)
 Release 14.2. A different file is now used to launch the player package. After you install the patch, republish and upload the content to the On Demand team. For more information, see the CA PA Support website.
CA Productivity Accelerator (CA PA) Version 12.1
You can upgrade to the latest version CA PA 12.1. Open a Support ticket, obtain a new license key, and download the software from the Download Center. The content from CA PA 11.1 can be exported and is fully compatible with CA PA 12.1. An additional patch is required for the player package to function properly with 
Clarity Project and Portfolio Management (PPM)
. For more information, see the CA PA Support website.
Internet Explorer 11
If you are using Internet Explorer 11 with 
Clarity Project and Portfolio Management (PPM)
, the browser is automatically set to run in the Internet Explorer 10 compatibility mode for the 
Clarity Project and Portfolio Management (PPM)
 session. The setting is for the 
Clarity Project and Portfolio Management (PPM)
 session only and does not affect any other Internet Explorer 11 browser activity.
Support Ended for Microsoft Excel 2007 and Microsoft PowerPoint 2007
Clarity Project and Portfolio Management (PPM)
 support for Microsoft Excel 2007 and Microsoft PowerPoint 2007 stopped at Release 14.1.
Upgrade Action
: To use these Microsoft products with this release, you must upgrade them to later a version.
Discontinued Internet Explorer Browser Version Support
Microsoft recently made a significant change in its Internet Explorer support policy. Effective January 12, 2016, only the most current version of Internet Explorer available for a supported operating system will receive technical support and security updates. Support for Internet Explorer versions 8, 9, and 10 is being retired. This change results in potential impacts to customers who are running 
Clarity Project and Portfolio Management (PPM)
 Releases 13.3 or 14.2 and to customers who plan to upgrade to 
Clarity Project and Portfolio Management (PPM)
 Release 14.3.
Administration Changes for Release 14.2
Here are the Administration updates for Release 14.2.
Change in Link Actions for the Project Object
The following obsolete actions were removed as options from the Action drop-down list that is available when a new link is created for the Project object:
  • Project Budget - Latest Revision
  • Project Budget - Specific Revision
  • Project Forecast - Latest Revision
  • Project Forecast - Specific Revision
Upgrade Action
: None
Resource Lookups for Action Items
Clarity Project and Portfolio Management (PPM)
 provides the following stock lookups for use with the Action Item Assignees functionality:
  • Resource Browse (SCH_BROWSE_RESOURCE)
  • All Resources Browse (LOOKUP_RESOURCES_ALL)
The lookup definitions contain the following general properties:
  • Object = Resource and the Parent Window
  • Hidden Key = ID value from SRM_RESOURCES table
The 
Clarity Project and Portfolio Management (PPM)
 process Action Item Assignees functionality expects the internal record ID for a Resource record, which is stored on the SRM_RESOURCES table. The functionality does not expect a user record ID. You can create a custom attribute that uses a stock 
Resource Browse
 lookup type, or you can create your own dynamic query lookup definition.
The most commonly used system-supplied lookup that meets this criteria is the Lookup ID = "SCH_BROWSE_RESOURCE". Using this lookup, you can create your own dynamic lookup that returns the SRM_RESOURCE.ID value as the hidden key value in the lookup.
Do not confuse the Resource Browse lookups with similarly named resource or user lookups.
Upgrade Action
: None
Advanced Reporting
The Advanced Reporting feature lets you build views and reports against project and other investment data to drive organizational intelligence. All customers upgrading to Release 14.2 that have no custom reports receive Advanced Reporting automatically. Advance Reporting has the following benefits for your users:
  • Easy to use, interactive reports that run within 
    Clarity Project and Portfolio Management (PPM)
     are available.
  • Filter options and report results appear in the same window, with support for cascading filters.
  • More scheduling options are available.
  • You can email reports, export reports, and save the report in the Jaspersoft repository.
    • You can specify email addresses, using up to a maximum of 200 characters. Separate email addresses with commas. You can also enter email aliases, which we recommend if you are sending the report to a large number of users.
    • You can export reports to a maximum of two formats (for example, Powerpoint and Word or PDF and Excel).
  • You can create report and style templates.
  • You can develop reports in 
    Clarity Project and Portfolio Management (PPM)
     against the Data Warehouse or the 
    Clarity Project and Portfolio Management (PPM)
     transactional database.
Data Warehouse
The Data Warehouse provides a schema that is optimized specifically for analytics. A set of 
Clarity Project and Portfolio Management (PPM)
 jobs extract, transform, and load the data from 
Clarity Project and Portfolio Management (PPM)
 to the Data Warehouse. The advantages of the Data Warehouse include:
Simplification of the data model that makes end user reporting easier. This feature reduces the demand for custom report development.
  • Reducing the stress and traffic on the 
    Clarity Project and Portfolio Management (PPM)
     transactional database. This reduction is possible because the Data Warehouse resides on a separate database server.
  • Any reporting solution can access the information in the Data Warehouse.
 
The Data Warehouse addresses several data and reporting challenges, described in the following table, that users experienced when working directly with the 
Clarity Project and Portfolio Management (PPM)
 transactional database.
Challenge
Response
Reports run against transactional data
The Data Warehouse has its own database which takes stress off the transactional 
Clarity Project and Portfolio Management (PPM)
database.
Complex relational database queries
The data warehouse carries keys and descriptive values in the dimension tables so that fewer joins are required. Facts are combined into summary and period tables.
Finding data with 1000+ tables
Data Warehouse tables are user friendly for reporting (with the exception of configuration and meta tables).
Table name inconsistencies
Similar tables are grouped together by the table prefix, and the names are descriptive.
Difficult time slice setup
Specific time slices are set up to populate the data warehouse. Defaults are set but can be adjusted.
Inconsistent column naming
Columns are named consistently across tables.
Resource ID versus
User ID confusion
Resource columns (manager_key, resource_key, and so on) are always the resource_key. In
Clarity Project and Portfolio Management (PPM)
, manager points to the user ID and the resource points to the resource ID or code, which is inconsistent.
Date and time storage correctness
The finish/end dates seen on the screen are dates in the data warehouse database. In
Clarity Project and Portfolio Management (PPM)
, a user must use a function to determine the date. For example: 12/31/2012 on the screen could be stored as 1/1/2013 00:00:00 in the 
Clarity Project and Portfolio Management (PPM)
table.
Use of Code versus ID
The 
Clarity Project and Portfolio Management (PPM)
financial tables use codes instead of IDs. The Data Warehouse always uses the numeric key of the dynamic lookups.
Database tuning
Because the Data Warehouse database is separate from the
Clarity Project and Portfolio Management (PPM)
database, it can be tuned differently for optimal performance.
Studio attributes not available in a Universe without customization
The data warehouse is extendable without customization. A flag was added to Studio objects and attributes that tells the load job to add new objects and attributes automatically.
Jaspersoft Reports
Advanced Reporting uses the Jaspersoft Studio application to manage views, reports, and dashboards. This third-party reporting option is integrated with 
Clarity Project and Portfolio Management (PPM)
 to provide easy reporting for users. Each report can be customized by selecting the domains and fields needed.
The Jaspersoft domains are a business representation of the Data Warehouse that lets you interact with data without having to understand database complexities. The Jaspersoft domains parallel and serve the same general purpose as the Business Objects Universes. The following figure shows how the Jaspersoft domains can be used to create reports in 
Clarity Project and Portfolio Management (PPM)
.
image2018-3-5 12:36:39.png
 
User Interface Adjustments for Advanced Reporting
New or upgrading customers who are moving to Advanced Reporting (Jaspersoft) must adjust the 
Clarity Project and Portfolio Management (PPM)
 user interface and user access rights. Because the Business Objects reporting solution is still available for existing customers, the user interface reflects that option.
Upgrade Actions
: Adjust the user interface and access rights to reflect that Jaspersoft and not Business Objects is the reporting option.
Actions for new and upgrading customers:
  1. Rename the 
    Reports and Jobs
     link that appears in the Home menu to 
    Jobs.
     This menu link appears for basic users.
    1. Open the Administration menu and from Studio, click Menu Manager.
    2. In the menu list, click Application Menu.
    3. Click Reports and Jobs in the list that appears.
    4. Change the link name to Jobs.
    5. Change the link description to Jobs.
    6. Click Save and Return.
    7. To see the updated menu option, refresh the menu.
  2. Rename the 
    Reports and Jobs
     link that appears in the Administration menu to 
    Jobs. 
    This menu link appears for administrators.
    1. Open the Administration menu and from Studio, click Menu Manager.
    2. In the menu list, click Administration Tool Menu.
    3. Click Reports and Jobs in the list that appears.
    4. Change the link name to Jobs.
    5. Change the link description to Jobs.
    6. Click Save and Return.
    7. To see the updated menu option, refresh the menu.
  3. Ensure that no users have the 
    Reports - Access
     right assigned.
    This access right makes the Reports tab under the Reports and Jobs link accessible to users. Because the reports listed there are Business Objects reports, the tab should not be visible to Jaspersoft users.
    If you are a new customer, do not assign this access right to users. 
    If you are an upgrading customer, remove the access right from assigned resources or groups. An out-of-the-box Jaspersoft report that is named 
    User Access Rights
     can provide the resources and groups with the right granted.
  4. Remove the My Reports portlet from the Overview page.
    1. Open the Administration menu and from Studio, click Portlet Pages.
    2. In the Pages list, click Overview, and then click Tabs.
    3. In the list of tabs, click General, and then click Content.
    4. Select the check box next to My Reports and click Remove.
    5. Save your changes.
General 
Clarity Project and Portfolio Management (PPM)
 Differences between Jaspersoft and Business Objects Implementations
The following cases describe the way that 
Clarity Project and Portfolio Management (PPM)
 report-related fields set for Business Objects can affect a Jaspersoft user:
  • If 
    Report 
    is selected for the Executable Type field in the Job Definitions filter, no result is given. Previously, this selection resulted in the list of Business Objects out-of-the-box reports.
  • All Jaspersoft reports are created and executed directly from the Jaspersoft user interface available in 
    Clarity Project and Portfolio Management (PPM)
    . Do not create a job with an Executable Type of 
    Report 
    if you are a Jaspersoft user.
  • Report-based object actions do not allow you to select a report from a drop-down list. No out-of-the-box reports appear in the Report drop-down list.
  • Query (NSQL) link creation does not provide out-of-the-box reports in the list of actions that can be selected.
  • Customers who are using Advanced Reporting cannot currently add an Action Link in Favorites for a report.
  • If you email repository links in the email body, the user must have repository access within Advanced Reporting, which requires at least a restricted user license. If the user needs to view the report output and does not have a minimum of a restricted user license, schedule a report to email the report output to the user.
Time Slices for the Data Warehouse
The following points apply to time slice requests that support the Data Warehouse:
  • A total of 40 time slice requests (25 new and 15 existing) support the Data Warehouse.
    To view the list of Data Warehouse time slice requests, navigate to the Time Slices list page and sort on the Data Warehouse column.
  • 25 new time slice requests were created.
  • 15 existing time slices can be affected during the Release 14.2 upgrade.
  • Because of new time slice requests and changes to existing requests, the first run of the 
    Time Slicing
     job can take substantially longer than usual.
  • Data Warehouse time slice requests are system requests and cannot be deleted.
  • The Data Warehouse time slice requests default to the following time periods, based on the database server system date:
    • For daily: 1 year back, 1 year forward. The From Date of the slice request is one year prior to the system date.
    • For weekly: 1 year back, 1 year forward. The From Date is one year prior to the system date and is the same day as the 
      First Day of Work Week
      . To locate the 
      First Day of Work Week 
      field, open the Administration menu and from Project Management, click Settings.
    • For monthly: 3 years back, 3 years forward. The From Date is three years prior to the system date and is always the first day of the month.
    • For fiscal: 3 years back, 3 years forward. The From Date is three years prior to the system date and corresponds to the start date of a Monthly (or 13 Period) fiscal period type that is based on the 
      Entity for Fiscal Periods
       value in Data Warehouse Options. To locate the 
      Entity for Fiscal Periods 
      field, open the Administration menu and from General Settings, click System Options.
      The entity must have Monthly (or 13 Period) fiscal time periods set up to cover the range of the time slice requests. Otherwise, the time slice requests are ignored when the
      Time Slicing
      job is run.
      If the From Date and Number of Periods for the 15 existing time slice requests are set to cover a time range greater than the default time ranges, the upgrade does not update the time slices. The time slices are left as they were before the upgrade.
  • The Data Warehouse time slice requests can be edited on the Time Slices page available from the Administration menu.
  • By default, the Data Warehouse time slice requests are set consistently for each slice period (Daily, Weekly, Monthly, Fiscal).
    If you edit these slice requests, set the From Date and Number of Periods to be the same for each slice period type. If these values are not set correctly, the data in the Data Warehouse will be inconsistent.
    Specifically, follow these rules when setting the From Date and Number of Periods for the Data Warehouse time slice requests:
    • All daily time slice requests, must have the same From Date and Number of Periods.
      This release contains only one daily time slice request.
    • All weekly time slice requests must have the same From Date and Number of Periods. The From Date must also be the same day of the week as the 
      First Day of the Work Week
      . For example: If the 
      First Day of the Work Week
       is a Monday, all weekly time slice requests must be set with a From Date that is the same, and the date must be a Monday.
    • All monthly time slice requests must have the same From Date and Number of Periods. The From Date must be the first of a month; it cannot be a day within the month.
    • All fiscal time slice requests must have the same From Date and Number of Periods. The From Date must correspond to the start date of a Monthly (or 13 Period) fiscal period type that is based on the 
      Entity for Fiscal Periods
       value in Data Warehouse Options. To locate the 
      Entity for Fiscal Periods 
      field, open the Administration menu and from General Settings, click System Options. The entity must have Monthly (or 13 Period) fiscal time periods set up to cover the range of the time slice requests. Otherwise, the time slice requests are ignored when the 
      Time Slicing
       job is run.
  • If you change the slice request default time periods, we recommend setting the time slice range to cover the start/finish dates of the investments on which you regularly report. For example, for two-year investments on which you regularly report, set the time slices to cover two years back and two years forward so that all relevant data is included in the Data Warehouse.
  • Fiscal time slice requests and a new table (PRJ_FISCAL_BLB_SLICES) were added to the 
    Clarity Project and Portfolio Management (PPM)
     schema to support fiscal period data in the Data Warehouse. These slice requests are not populated and do not have supporting data in the PRJ_FISCAL_BLB_SLICES table until a series of steps are completed.
    Although we ship fiscal time slice requests, this release contains no option to create new time slice requests with a slice period of fiscal. The only available fiscal time slice request functionality resides in the new slice requests shipped for the Data Warehouse.
    To use the new fiscal slices and populate the PRJ_FISCAL_BLB_SLICES table after the upgrade or installation, follow these steps:
    1. Log in as an Administrator user.
    2. Open the Administration menu and from General Settings, click System Options.
    3. Select the 
      Entity for Fiscal Periods 
      value and verify the Languages setting, and save your changes.
      Specifies the entity that is used to determine fiscal periods. The fiscal periods that are associated with the selected entity are used for all Data Warehouse fiscal period data calculations. Setting the entity for the first time creates new Data Warehouse time slice requests. Therefore, the initial run of the Time Slicing job takes significantly longer than normal. 
      Initially setting an entity or updating it also updates the fiscal entity and fiscal period type for the Data Warehouse fiscal time slice requests. Do not set or change the entity when a time slice rollover is in progress. If you do, an error message appears. Wait until the rollover completes and then set the entity. To determine which slice requests are in the rollover, check the expiration date on the time slices. A slice request with an expiration date that is blank, earlier than the current date, or the same as the current date is in the rollover. Allow the slice request to complete processing before setting the entity.
      The entity must have Monthly (or 13 Period) fiscal time periods set up to cover the range of the time slice requests. Otherwise, the time slice requests are ignored when the
      Time Slicing
      job is run.
    4. Run the 
      Time Slicing
       job.
    5. To populate the Data Warehouse schema, run the Load Data Warehouse job.
    6. To populate the security tables in the Data Warehouse schema, run the Load Data Warehouse Access Rights job.
     
  • The following table contains the Data Warehouse time slice requests. Note that the new time slices have 
    dwh 
    in the name, and the fiscal time slices have 
    fiscal 
    in the name.
Time Slice ID
Time Slice Name
55555
DAILYRESOURCETIMECURVE
55556
WEEKLYRESOURCEACTCURVE
55557
WEEKLYRESOURCEESTCURVE
300
WEEKLYRESOURCEBASECURVE
307
WEEKLYBASEASSIGNCOSTS
55559
WEEKLYRESOURCEAVAILCURVE
55558
WEEKLYRESOURCEALLOCCURVE
306
WEEKLYRESOURCEHARDALLOC
4
MONTHLYRESOURCEACTCURVE
5
MONTHLYRESOURCEESTCURVE
312
MONTHLYRESOURCEBASECURVE
305
MONTHLYBASEASSIGNCOSTS
7
MONTHLYRESOURCEAVAILCURVE
6
MONTHLYRESOURCEALLOCCURVE
55566
MONTHLYRESOURCEHARDALLOC
55577
assignment::practcurve::dwh_fiscal
55578
assignment::prestcurve::dwh_fiscal
5004026
assignment::actcost_curve::dwh_week
5004027
assignment::actcost_curve::dwh_month
55584
assignment::actcost_curve::dwh_fiscal
55576
assignment::etccost_curve::dwh_week
55567
assignment::etccost_curve::dwh_month
55589
assignment::etccost_curve::dwh_fiscal
55588
baseline::current_assignment_usage::dwh_fiscal
55587
baseline::current_assignment_cost::dwh_fiscal
5004016
baseline::current_team_usage::dwh_week
5004017
baseline::current_team_usage::dwh_month
55582
baseline::current_team_usage::dwh_fiscal
5004020
baseline::current_team_cost::dwh_week
5004021
baseline::current_team_cost::dwh_month
55581
baseline::current_team_cost::dwh_fiscal
55579
resource::pravailcurve::dwh_fiscal
55580
team::pralloccurve::dwh_fiscal
55583
team::hard_curve::dwh_fiscal
5004022
team::alloccost_curve::dwh_week
5004023
team::alloccost_curve::dwh_month
55585
team::alloccost_curve::dwh_fiscal
5004024
team::hardallccost_curve::dwh_week
5004025
team::hardallccost_curve::dwh_month
55586
team::hardallccost_curve::dwh_fiscal
Financial Management Changes for Release 14.2
Here are the Financial Management updates for Release 14.2.
Updates to Non Project Investment Objects (NPIOs)
The following updates were made to NPIOs (Programs, Applications, Assets, Products, and Other Work):
  • Enhanced functionality of the 
    Update Earned Value Totals 
    job
    The 
    Earned Value Totals
     job was renamed to 
    Update Earned Value and Cost Totals 
    to reflect new functionality. This job calculates the earned value and costs for projects and costs for NPIOs. The project or the NPIO can be selected using the Investment Browse field on the job properties page. The job contains parameters that let you select the OBS unit, filter mode for the OBS unit, and the investment manager. The functionality of this job can also be invoked using the object action Update Cost Totals on the Team page of an investment.
  • New Object Action on the Investment Staff pages
    The new object action Update Cost Totals is available on all project and NPIO Staff list and detail pages. This object action calculates the allocation and hard allocation costs. Three new fields (Allocation Cost, Hard Allocation Cost, and ETC Cost) were added to represent these values. The fields were added to capture the cost values in the data warehouse and cannot be broken across the time periods.
    These costs can also be selected on custom portlets that are based on the Team data provider. The Staff list and details pages also display the allocation cost and hard allocation cost.
  • Time Slice Changes
    The following time slices were added or renamed to reflect the new functionality:
    • Added:
      Assignment::ETC Cost
      Team::Allocation Cost
      Team::Hard Allocation Cost
    • Renamed:
      Assignment::Actual Cost (previously Assignment::Actual Cost Curve)
Upgrade Action
: None
Resource Average Allocation Percentage
The business logic behind the calculation for the default resource allocation percentage has been improved. When calculating the average allocation percentage and total availability hours, the application uses the start and finish dates for the team member instead of the investment.
This change can affect your own custom metrics and other calculations.
To illustrate the enhancements, create a project with a six-week duration from August 5 to September 13 and staff it with a team of three resources.
  1. On the Team list for the first resource, change the finish date to August 17 (two weeks, 80 hours) and the Default Allocation to 50 percent. The allocation is 40/80 or 50 percent as expected.
  2. For a second resource, change the finish date to August 17 (two weeks, 80 hours) and the Default Allocation to 50 percent. Add a segment from August 18 to 30 (two weeks, 80 hours) at an allocation of 100 percent.
    • Before this release, the application would calculate an allocation of 120 (40 + 80) and suggest an average allocation percentage for a resource that spans the complete project duration. In other words, the allocation percentage would apply 50 percent to 240, the total hours in the duration of the project (6 weeks x 40 hours = 240).
    • New in this release, the application calculates the allocation of 120 hours but yields a more accurate average allocation of 75 percent. The duration is just four weeks for the resource, not six. Their 120 hours divided by 160 total hours results in an average allocation of 75 percent.
  3. For a third resource, change the finish date to August 17 (two weeks, 80 hours) and the Default Allocation to 50 percent. Adjust this segment by specifying an allocation of 100 percent from August 5 to 17.
    • Before this release, the application would calculate an allocation of 40 hours for the two weeks, but an average allocation of 16.7 percent (40/240).
    • New in this release, the application calculates the same allocation of 40 hours but yields an average allocation of 50 percent (40/80).
Upgrade Action
: None
Portfolio Management Changes for Release 14.2
Here are the Portfolio Management updates for Release 14.2.
Limit on Portfolio Investments Removed
Release 14.2 has no limit on the number of investments that can be included in a portfolio. In previous releases, the limit for investments was 150.
The limits for roles (25) and attributes (700) remain the same.
Upgrade Action
: None
Usability Improvements for the Waterlines View
The following changes were made to the Waterlines view:
  • Pending Edits for Waterlines
    The changes that you make to the Waterlines view are saved as pending edits. The edits are saved temporarily until you save them permanently or discard them. If you navigate away from the view or close the session, the pending edits are saved. When you return to the view, you can still save or discard your pending edits.
  • Discard Changes 
    This button on the Waterlines view lets you discard pending edits. The button is activated when pending edits appear on the view.
  • Improved Waterline View Navigation
    You can scroll in both directions on the Waterlines view to see the complete list of investments. The Waterlines view contains no pagination; the list of investments is refreshed continuously. You can view 150 investments on the view at a time.
    Setting the Aggregate Constraint on the waterline for the first time, running the Portfolio Synchronization job, or changing the ranking rules with a constraint reprocesses the aggregated values in the Waterlines view. Depending on the number of investments in the portfolio, you can experience a slight delay while the calculations are refreshed.
  • Enhanced Waterline Drag and Drop
    A drag-and-drop operation on Waterlines view investments causes a tool tip to appear that shows the drop target and the number of selected rows. The tool tip is a green checkmark. When you reach the top or bottom of the list, the icon changes to a red circle with a line.
Change to the Synchronize Portfolio Investments Job
When the number of portfolio investments added between runs of the 
Synchronize Portfolio Investments
 job is equal to or greater than 1,000, an alert appears. The alert breaks down the number of investments by type and asks if you want to continue with the synchronization.
The alert appears only when the threshold of 1,000 added portfolio investments is reached. The alert can be triggered when the Sync Now button initiates the job.
Upgrade Action
: None
Synchronization Required after Adding Roles
When you add roles to a portfolio on the Targets page, you must click Sync Now to see the latest aggregated and individual role values on the Waterlines view. If you do not synchronize the portfolio after adding roles, an alert appears on the Waterlines view.
Upgrade Action
: None
Project Management Changes for Release 14.2
Here are the Project Management updates for Release 14.2.
Microsoft Project 2013 Service Pack 1
Microsoft Project 2013 Service Pack 1 is supported for integration with the new 
Clarity Project and Portfolio Management (PPM)
 Release 14.2 MSP Interface option. The 
Clarity Project and Portfolio Management (PPM)
 Legacy MSP Interface option does not support the Microsoft Project Service Pack 1.
Upgrade Action
: Alert your project managers to this incompatibility if they plan to use the Legacy Interface option.
Auto-Numbering and Project IDs
If auto-numbering is defined on the project object, the auto-numbering is enforced when you create and save a project to 
Clarity Project and Portfolio Management (PPM)
. The project ID field will be read-only in Microsoft Project.
Upgrade Action
: None
Assignment Max Percent Load is Respected for Fixed Unit Tasks
A flag has been added under Project Management Administration called “MSP Assignment Units Mapping with PPM Assignment Max % Load" to allow customers to turn on or off the mapping of Max % Load when opening/exporting the project from Microsoft Project.
  • If the flag is checked, the MSP unit is mapped based on the Max % Load value in 
    Clarity Project and Portfolio Management (PPM)
    .
  • If the flag is unchecked, the MSP unit is mapped based on the staff allocation rate base on the date that you opened the project in Microsoft Project.
When saving or importing to 
Clarity Project and Portfolio Management (PPM)
, the MSP assignment units value is always written to Max % Load, regardless of the flag setting under Project Management Administration.
Upgrade Action:
 Set this flag based on your requirement for the Max % Load information when opening the project in Microsoft Project.
New UI for Mapping 
Clarity Project and Portfolio Management (PPM)
 Attributes to Microsoft Project Fields
You can create or update the field mapping for 
Clarity Project and Portfolio Management (PPM)
 custom attributes and Microsoft Project fields to synchronize the values when importing and exporting data. Only the custom attributes of the Project, Resource, Task, Assignment, and Team objects can be mapped. The custom attributes must be of following data types:
  • Date
  • Number
  • String
  • Boolean
 
For more information about mapping fields, see
Project Management
.
 
Upgrade Action
: None
Data Model Changes for Release 14.2
To identify the Oracle and Microsoft SQL database and data warehouse schema changes, see Oracle and MS SQL Database Schema Changes.
Known Issues for Release 14.2
Fiscal Time Slices Are Reset after Saving the System Options Page
Fiscal Time slices are reset if you save the System Options page (Administration, General Settings, System Options). This resetting occurs even if you do not change any of the fields on the page.
Advanced Reporting Repository Items Are not Localized
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.
Advanced Reporting Custom Subobjects Are not 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.
Advanced Reporting Requires Logout to Change Language
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 
Clarity Project and Portfolio Management (PPM)
 after changing the language setting and log in again. The data then appears in the new language.
Advanced Reporting Notifications Do Not Work with Incorrect Email Format
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.
Advanced Reporting Charts and Widgets Do not Appear in Browser PDF
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.
Advanced Reporting Schedule Date Does not Work for Some Languages
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 Scheduled PDF Appears in Collapsed Format
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.
Advanced Reporting Ad Hoc View Filters Do not Auto-Populate
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.
Advanced Reporting Report Output with Email Notifications
The following output options, which are available for selection when you create or edit a report schedule, have issues regarding their format or content:
  • PDF – Contains one blank page.
  • ODT – Contains one page only.
  • PPTX – Contains one slide only, with extra content on that slide.
  • RTF – Requires a long time for a large report.
Advanced Reporting Report Options Do not Display Data
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 
Clarity Project and Portfolio Management (PPM)
 and log back in again. The data displays correctly then.
Jaspersoft Sender Email Address
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. This issue occurs when more than one tenant (organization) is present on the same server.
The following address is the default sender email address value for the JasperSoft reporting server for On Demand implementations:
Reports for Earned Value Management (EVMS) and PMBOK Add-Ins
The reports for the EVMS and the PMBOK add-in are not available as Jaspersoft reports.
Microsoft Project Interface - Baseline Costs are Ignored
When you baseline your project in Microsoft Project and then import it back to 
Clarity Project and Portfolio Management (PPM)
 again, the baseline costs are ignored when saved to 
Clarity Project and Portfolio Management (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 
Clarity Project and Portfolio Management (PPM)
 only.
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.
Google Chrome Version 30.0.1599.66 m Issues
The following 
Clarity Project and Portfolio Management (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.
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
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 
Clarity Project and Portfolio Management (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 
Clarity Project and Portfolio Management (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 
    Clarity Project and Portfolio Management (PPM)
     to Microsoft Project 2013.
For more information, see the following Knowledge Base articles on CA Support Online: TEC610737, TEC615024.
Microsoft Project 2013 Service Pack 1 is supported for integration with the new 
Clarity Project and Portfolio Management (PPM)
Release 14.2 MSP Interface option.
Upgrade Action
: Do not apply Service Pack 1 to Microsoft Project 2013 if you are using the 
Clarity Project and Portfolio Management (PPM)
 Legacy MSP Interface.
Pre-Upgrade Steps
  1. You must have the standard base calendar available in your 
    Clarity Project and Portfolio Management (PPM)
    application before you upgrade. If you deleted the shipped calendar that is named 
    Standard
    , create it before upgrading. Contact CA Support if your instance is missing the Standard base calendar.
  2. Process all
    In progress
    transactions into WIP.
    1. Verify the following conditions: 
      1. imp_transactionimport and ppa_transcontrol are clear.
      2. WIP adjustments are approved.
    2. Review and fix all invalid transactions.
  3. Review Time Slices. 
    Verify that the table is slicing out only the data that is required. If extra data is getting sliced, the database size increases and affects system performance.
  4. Complete and put all processes on hold.
  5. Remove or delete process history, notifications, jobs, or logs. Look for items that you do not need to keep.
  6. Pause all scheduled jobs. Take special note of the 
    Time Slicing
     job. Pause it before stopping the CA PPM services before upgrading.
Post Upgrade Steps
Complete the following post upgrade steps after a release upgrade:
  1. If you have custom Xcelsius dashboards, see
    Correcting the CA Clarity PPM URL for HTML and Xcelsius Portlets
    in the Release 13.0 Updates.
  2. For CABI Release 3.3 SP2 (BusinessObjects), manually restart the scheduled reports.
    Any scheduled reports that were configured before the upgrade to this release do not automatically run after the upgrade.
  3. Apply your upgraded add-ins and connectors.
    • Request a backup of your 
      Clarity Project and Portfolio Management (PPM)
      installation before installing each add-in so that you can restore the application if necessary. You can also use the previous night's regular backup as a restore point. Backups are retained for seven days unless a longer period is requested. A 30, 60, or 90 day retention is available on request.
    • Apply the Upgrade Ready content for those items that you are actively using.
      Consider the configurations that you have made to items before applying them. Applying modified items overwrites your configurations.
      Best Practice
      : If you modified stock 
      Clarity Project and Portfolio Management (PPM)
      content, copy the modified content before upgrading. Then, apply the new incoming stock 
      Clarity Project and Portfolio Management (PPM)
      content, and retrofit the modifications to the new content.
    • Read the
      PMO Accelerator Release Notes
      for important information about what has changed for the PMO Accelerator.
    • Review the
      System: Clarity Content
      add-in for upgrade ready content (for example, the Role Capacity portlet). To accept the new Release 14.2 upgraded content, apply the changes.
  4. Review the Studio views and system content and manually upgrade as needed.
    The upgrade preserves all preexisting 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.
    To determine which views were not automatically upgraded, use the Studio Views list page.
    Here are some tips on reviewing the views:
    • The Last Version column identifies changes to stock views in Release 14.2.
    • If a view was automatically upgraded as part of the upgrade process, a checkmark appears in the Upgraded column. No further action is required.
    • If a view that changed in Release 13.3 was not upgraded due to pre-existing configurations, decide whether to apply the changed view.
      Look for views with the following column information:
      Last Version column=14.2 and the Upgraded column= unchecked.
  5. Verify your custom NSQL queries if any exist.
    During the upgrade, the NSQL validator script automatically verifies NSQL queries. Results are written to the admin.log.
    The log contains the following information:
    • Query name
    • Query ID
    • Content Source
    • Query ID from CMN_NSQL_QUERIES of the query that failed validation
    This release contains database schema changes. To ensure that portlets work, correct any invalid NSQL queries.
    For information about the database schema changes, see
    Data Model Changes for Release 14.2
    .
    If the query can be changed in Studio, complete these steps:
    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 that the NSQL query is valid.
    If the query is in use by active portlets and cannot be edited in Studio, complete these steps:
      • Use the XML Open Gateway (XOG) to export the failing query.
      • Correct the broken query constructs or fields.
      • Use XOG to import the corrected query.
      • Click the Preview button.
      • Confirm that the NSQL query is valid.
  6. The XML Open Gateway (XOG) client requires the Java Runtime Environment (JRE). If you use the XOG, note that the JRE is no longer available from the Clarity Software Downloads link. Review the supporting documentation and training materials you provide to your users. Wherever these materials direct users to download the JRE from within
    Clarity Project and Portfolio Management (PPM)
    , update the reference. Direct your users to download the JRE (Version 7) from www.java.com.
  7. Register any Portfolio Investment attributes that you want to display in portfolio pages. Although the required attributes display by default, you must register any other attributes (stock or custom) that you want to display.
  8. This product supports Microsoft Project 2010 and 2013. If you upgrade and use one of these versions, update your Microsoft Project Desktop to ensure that data populates appropriately in the Microsoft Project Interface. Set the scheduling option to Automatic when you want to open the schedule in the Microsoft Project Interface.
  9. If you use a custom statistics job, refer to the updated Oracle Table Analyze Job procedure in the
    Clarity Project and Portfolio Management (PPM)
    schema (CMN_JOB_ANALYZE_SP) and make necessary corrections in the custom statistics job.