Clarity PPM 15.5.1.4 and Jaspersoft Cumulative Patch README Files

Cumulative patches for cappm 15.5.1 and Jaspersoft for PPM are periodically available. Before applying a patch, see the README for important information.
HID_clarity_readme
Cumulative patches for 
Clarity PPM
 15.5.1 and Jaspersoft for PPM are periodically available. Before applying a patch, see the README for important information.
How Do I Know If I Have CA PPM On-Premise or SaaS Edition?
 
Launch your CA PPM application, log in, and click 
Help
 (remember to allow browser pop-ups). The application opens the matching online help documentation for your edition of CA PPM on-premise or CA PPM SaaS.
To find the latest patch information, select your CA PPM release under the 
Versions
 menu and then open the patch README page. 
SaaS Customers: 
Contact CA Support to request and schedule patch installation on specific 
Clarity PPM
 hosted instances in the On Demand Portal. Any fixes for reports are automatically deployed in your SaaS environment. Notifications for scheduled mandatory Jaspersoft patches are provided by email to the customer support contacts on file. 
On-premise Customers:
 To install a patch or update reporting content, download the patch from CA Support and follow the README instructions on this page.
Although they are technically not patches, we list the Jaspersoft installers for CA PPM on this page because they behave like patches for existing 
Clarity PPM
 customers with Advanced Reporting environments.
 
3
 
2
 
 
Clarity PPM 15.5.1.x Cumulative Patch Details
Because patches are cumulative, when you install a single patch, it includes all the fixes from all previous patches.
GA Date
Patch
Aug 29, 2019
15.5.1.4
June 3, 2019*
15.5.1.3*
April 10, 2019
15.5.1.2
Feb 14, 2019
15.5.1.1
*An updated edition of this patch with a minor correction in its README text file is expected to be available for download on or around June 14, 2019.
CA PPM 15.5.0.0 base release customers have the following options:
  • OPTION A
    : Apply the 15.5.0.1. patch and remain at that level. No future patches are available with this option; however, you can upgrade to a future release.
  • OPTION B
    : Apply the 15.5.0.1 patch, and then apply the 15.5.1 service pack and the latest cumulative patch.
  • OPTION C
    : Skip the 15.5.0.1 patch and apply the 15.5.1 service pack on top of 15.5.0.0. Then apply the latest cumulative patch.
In addition to providing the same fixes delivered in the 15.5.0.1 patch, the 15.5.1 service pack includes new features and enhancements that extend your 15.5 product. Product release schedules do not include a 15.5.0.2 patch target; however, 15.5.0.1 remains a supported option (see 
OPTION A
 above).
To switch your documentation, select a release such as 15.5 or 15.5.1 from the 
Versions
 menu at the top of this page.
Patches are intended to be timely fixes and are not fully regression or integration tested, and are only tested against the issues listed below. CA feels confident that this patch will resolve the addressed problems, but customers should be aware that a patch could have adverse side effects to the function of their CA PPM application. Customers should not apply patches directly to production systems without first verifying in a test environment. If any issues arise in the installation or use of this patch, contact CA Support. 
Files Included
  • README.txt -> This file
  • install.sh -> Unix installer
  • install.bat -> Windows installer 
  • install.xml -> Ant install script
Prerequisites
Install only on systems running the version stated above.
Issues Fixed in 15.5.1.4
Clarity PPM 15.5.1.4 Patch README
Version #: 15.5.1
Patch #: 4
DE49842:
 XOG remove Association did NOT remove subobject
Steps to Reproduce:
  1. Login to Clarity PPM. 
  2. Find a Investment to associate a project with. 
  3. Associate the Project with an investment using the below XOG structure.
    <NikuDataBus xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="../xsd/nikuxog_project.xsd"> <Header action="write" externalSource="NIKU" objectType="project" version="15.5.1.240"/> <Projects> <Project name="Test Sub Project" projectID="PR2066"> <Tasks/> <Allocations/> <scenarioDependencies/> <InvestmentAssociations> <Allocations> <ParentInvestment defaultAllocationPercent="1.0" InvestmentType="project" InvestmentID="PR1037"/> </Allocations> <Hierarchies> </Hierarchies> </InvestmentAssociations> <General addedBy="admin" addedDate="2019-06-26"/> <OBSAssocs complete="false"/> </Project> </Projects> </NikuDataBus>
  4.  Navigate to investment PR1037 you will find PR2066 added as a Sub-Project and also in Heirarchy.
  5.  De-associate it using the below XOG structure.
    <NikuDataBus xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="../xsd/nikuxog_project.xsd"> <Header action="write" externalSource="NIKU" objectType="project" version="15.5.1.240"/> <Projects> <Project name="Test Sub Project" projectID="PR2066"> <Tasks/> <Allocations/> <scenarioDependencies/> <InvestmentAssociations complete="true"> <Allocations> </Allocations> <Hierarchies> </Hierarchies> </InvestmentAssociations> <General addedBy="admin" addedDate="2019-06-26"/> <OBSAssocs complete="false"/> </Project> </Projects> </NikuDataBus>
  6. Navigate to the Parent investment which is PR1037, You see that under Sub-Projects we find the project PR2066, but under hierarchies we don't have PR2066.
Expected Result: 
Project PR2066 should be removed from both hierarchies and subprojects, as what happens when you add/remove a child under Hierarchy tab using Clarity PPM UI. 
Actual Result : 
Project PR2066 is only removed from hierarchies tab and not subprojects.   
DE49702: New UX Project Navigation Performance Issue
Steps to Reproduce:
  1.  Login to Clarity PPM.
  2. Find a Project which has large number of team,tasks,assignments.
  3.  Navigate to New UX.
  4.  Search for the Project identified in Step 2.
  5. Click on the Project Tile.
Expected Result: Since the landing page of the Project is conversations, the Project should open quickly within 5 secs. 
Actual Result: Project opens after more than 2 minutes.
 DE47804: Anonymize Personally Identifiable Information (PII) job not working as expected 
Steps to Reproduce:
  1. Log in as an active user
  2. Set up an audit trail for fields that should be anonymized. Example: Project Manager, Change Request Assessor, etc
  3.  Find a resource to be anonymized
  4.  Update the fields with the audit trail (ex: Project Manager, Change Request Assessor) so some records contain the resource to be anonymized
  5.  Inactivate the resource to be anonymized and check the anonymize field
  6.  Run the PII Anonymization job
Expected Result: There should be no evidence that the resource exists. Manually look at cmn_audits table to make sure no evidence exists
Actual Result: The Audit table had references to the anonymized resource
DE44615: The incremental load data warehouse job long processing time
Steps to Reproduce:
  1.  Log in as an active user
  2. Set up some cost plans on projects
  3. Post actuals on the projects
  4. Run incremental load data warehouse
Expected Result: Data warehouse load should finish in a reasonable amount of time
Actual Result: Data warehouse load takes way too long to finish
DE45016: OBS When moving 2 levels LDWH job fails
Steps to Reproduce:
  1. Define OBS with more than 2 level
  2. XOG out the OBS
  3. Move 2 levels of the OBS (move to root)
  4.  Run DWH job
  5.  XOG in the OBS
  6. Run DWH job
Expected Result: DWH job should run fine
Actual Result: DWH job fails because of duplication of records
DE49471:Blank notifications being generated for Risks, Issues and Change Request when they are getting created
Pre-requisites:
  • Create custom attribute on the Issue object called "PMO Owner" with attribute ID = r4.
  • Data Type = Multi Valued Lookup - Number
  • Lookup = Resource Browse
  • Value Required is Checked
Steps to Reproduce:
  1. Create a Risk, Issue or Change Request by going to any existing project or create New one.
  2.  Assign the Risk, Issue or Change Request to Admin user. Click "Save".
  3. Check the notification tab under Organizer.
Expected Result: This issue has been assigned to you:
  • Issue Name: ASDFSADF
  •  ID: SDFSDFG
  • Investment: DDDD
  • Priority: Low
  • Assigned By: Administrator, CA PPM
  • Created On: 5/31/19 10:10 AM
To view the issue, Click Here
The same issue occurs with Risks and Change Requests.
Actual Result: 
  • This issue has been assigned to you:
  • Issue Name:
  • Issue ID:
  • Investment:
  • Priority:
  • Assigned By:
  • Created On:
To view the issue, Click Here
Issues Fixed in 15.5.1.3
Version #: 15.5.1
 Patch #: 3
DE42990: Adjusted Timesheet Not Showing in PPA WIP
Adjustment Timesheet does not post to WIP when financial status is closed when first adjustment posts.
Follow these steps:
 
1. Create and financially enable two (2) projects (Project 1 and Project 2). Select 
Open for Time Entry
 and set 
Track Mode
 to 
PPM
.
 
2. Add a financially enabled resource. Open for Time Entry. Make sure the resource is in the rate matrix so transactions will post.
 
Create one task on each project and assign the resource.
 
 
Timesheet steps:
 
 
3. Create a timesheet and add the two tasks from the two projects.
 
4. Make sure the Charge Code and Input Type code are populated.
 
5. Add hours for a few days on both projects/tasks.
 
6. Submit/Approve/Post Timesheet
 
7. Verify in Invalid Transactions
 
8. Post Transactions to Financials (Verify gone from Invalid Transactions)
 
9. Post to WIP - verify transactions are posted.
 
Adjust timesheet:
 
 
10. Adjust one line on the timesheet and remove the hours (zero or blank value) from Project 2.
 
11. Submit and Approve Do not post yet
 
12. Take off time entry and close financials for Project 2 (you already removed the hours). Not sure if Time Entry is relevant but financial status is.
 
13. Post Timesheets
 
14. Check Invalid Transactions - Entries should not be in there as Financial Status is closed.
 
 
Adjustment timesheet #2:
 
 
15. Open the project for time entry. DO NOT Change Financial Status - Remain Closed
 
16. Adjust the timesheet again and add hours back to Project 2.
 
17. Submit, Approve, Post again.
 
18. Check Invalid Transactions - Entries should not be in there as Financial Status is closed.
 
19. Open Financial Status on Project 2.
 
20. Post Timesheets again.
Expected Result: The two adjustments show in invalid transactions so the original timesheet gets credited.
 
Actual Result: Only Adjustment #2 is in Invalid Transactions. This causes WIP to have the Original Transactions and the #2 Adjustment transactions with no credits inflating WIP.
DE46904: Cannot Use Tab Key Navigation to Replace New UX Timesheet Cell Values (value is not pre-selected and cursor appears at end of value)
Steps to Reproduce:
 
1. Navigate to new UX
 
2. Go to timesheets > Edit an existing timesheet
 
3. Populate timesheet
 
4. Enter values for each one of the days (from Monday to Friday)
 
5. Go back to the Monday cell and using the tab move along the rest of the daysExpected results: The value in Tuesday is pre-selected. If a new value is entered, the pre-selected value is replaced.
 
Actual hours: The cursor is placed at the end of the value. You must delete the existing value before you can enter a new one.
DE44357: Cost Plan Issue - Non-standard fiscal periods do not follow expected editability rules
Steps to Reproduce:1. Make a non-standard calendar monthly period type (or 13 period type) fiscal periods so they do not start and end on the first/last day of month.
 
2. Create a manual MONTHLY cost plan using this entity.
 
3. Note that each period cell is editable.
 
4. Edit the cost plan properties to change End Period to prior period.
 
5. Go back to cost plan details.Expected Result: You cannot edit final period.
 
Actual Result: You can edit final period.
 
DE42701: Investment specific Charge Codes are not selectable in New UI Financial Plans
Steps to Reproduce:1. Navigate to Administration, Project Management, Settings, and make sure that "Enable Investment-specific Charge Codes" is marked as "Yes".
 
2. In Classic PPM, create a project.
 
3. Navigate to the Properties, Charge Code page.
 
4. Create a new charge code.
 
5. Navigate to the New UX. Open the project created in Step 2. Navigate to the "Financials" tab.
 
6. Create a financial plan. Group by "Charge Code"
 
7. Create a new row in the Financial plan. Try to choose the charge code created in step 4Expected Result: Charge Code created in Step 4 is selectable in the New UI
 
Actual Result: Charge Code created in Step 4 is not selectable in the New UI; however, it is selectable in Classic PPM.
 
DE46426: Forecasted Utilization Report does not display FTE under assignment column
1. Find someone who has no assignments but has actuals so they have EAC.2. Run the report for hours.
 
- Note the Assignment Hours - It shows EAC instead of ETC
 
- Note this does not have to be the only way to get ETC to be 0 but there has to be posted actuals to the task.
 
3. Run the report for FTE
 
-Note Assignments FTE shows 0 as there is 0 ETCExpected Result: The calculation should use EAC hours for both.Actual Result: FTE calculation for assignments is incorrect in the report query. When running the report with Unit Type as Hours,
 
the report uses EAC hours column whereas with Unit Type as FTE, the report uses the ETC hours column to calculate FTEs.
 
DE46361: Error 'NPT-0060: Mapping requires name to be supplied' when trying to set query attribute display mappings to icon type
Steps to Reproduce:1. Go to Administration > Studio > Queries
 
2. Create a new query called "My query"
 
3. Fill the NSQL tab with nsql query to create attributes (one of them is impact_enum attribute).
 
4. On the Attributes tab, edit the impact_enum attribute for example
 
5. Set the Display Mappings to icon
 
6. Select the Up Arrow - Red icon, or Red - Flag or any other. Add a description (Red) and provide any from to values (0 to 1)
 
7. Click Save.Expected result: The display mappings to be set to icon
 
Actual Result: Error received NPT-0060: Mapping requires name to be supplied / NPT-0063: From and To must be specified.
 
DE45555: Locale formatting is not correct in the denominator of the Timesheet Review & Approve Row and Flyout
Steps to Reproduce:1. Login to Classic PPM as an administrator.
 
2. Home Account Settings - Change the Locale: Italian (Italy) for the logged in administrator user.
 
3. Logout and login again as the administrator user so that the locale settings are updated.
 
4. Administration, Resources - Create a Resource.
 
5. Go to Home, Resources for this new resource and update the Calendar Shifts so that the Resource has 7,5 daily availability rate
 
6. Update the Resource settings for PPM Track Mode, Open for Time Entry
 
7. Navigate to the New UX,
 
8. Click on the Timesheets menu navigation,
 
9. Click on a 'Select Resource' button and select the newly created resource,
 
10. Populate the timesheet and enter in some time so that the total amount of time = 10,5,
 
11. Submit the Timesheet
 
Note the numbers appear correctly here as 10,50 / 37,50
 
12. Click on Review and Approve
 
13. Find the Resource with the submitted timesheet
 
14. See the card on the row for the resource with the submitted timesheet
 
Note the denominator number does not have a comma - it shows 10,50 / 37.50
 
The 2nd number has a decimal point, not a comma
 
15. Click on this card for the resource with the submitted timesheet to see the fly-out
 
Note the denominator number does not have a comma - it shows 10,50 / 37.50
 
The 2nd number has a decimal point, not a commaExpected Results: All numbers where a comma should be show have: ","
 
Actual Results: Numbers are showing with both comma and decimal points (ex. 10,50/37.5) 
DE40179: MS SQL Load Data Warehouse Full Load job performance problem on large datasets
Steps to Reproduce:
1. Use large MSSQL datasets - only reproducible on large datasets.
2. All jobs are Paused on this environment.
3. Run Load Data Warehouse - Full Load.
Expected results: Load Data Warehouse - Full to take a reasonable amount of time
Actual Results: Load Data Warehouse - Full takes large amount of time, big majority of which is on DWH_RES_PERIOD_FACTS
DE48698: Data Warehouse Table Constraint issue when running Load Data Warehouse job
The status attribute of the DWH_INV_SERVICE_LN_FK1 constraint on the DWH_INV_SERVICE_LN table has a 
disabled
 value after the full or incremental load data warehouse job is run to completed status. The Load Data Warehouse job disables all constraints before copying the data from the database to the data warehouse schema, and then re-enables all of them after the job is completed, so this behavior appears to be a bug.
Steps to Reproduce:
1. Run the full load data warehouse job.
2. Verify completed status.
Expected: The status attribute of the DWH_INV_SERVICE_LN_FK1 constraint has an "enabled" value after the job is completed.
Actual: The status attribute has the value "disabled" after the job is completed.
Issues Fixed in 15.5.1.2
DE42036: Timesheet hours for Incidents not showing in Capacity Overview Portlet
Steps to Reproduce:
1. Create an incident and assign it to a resource.
2. Open the timesheet for that resource for the current period.
3. Add the incident to the timesheet.
4. Log time to the incident and submit the timesheet.
5. Approve the timesheet and wait until it is posted.
6. Go to the Capacity Overview screen.
7. Configure the page to display Incident Actuals in the stacked Allocation time scaled value
8. Choose the OBS that contains the resource that tracked time to the incident.
Expected: The Incident Actuals shows the number of actuals posted by the resource on the incident.
Actual: The Incident Actuals is blank.
DE44896: New UX Staffing - Lag when typing data in cells
Steps to Reproduce:
Prerequisite: Create a project and add multiple resources to it.
1. Log in to the New UX.
2. In the main menu, click Staffing.
3. Switch to the 'Investments-to-Resources' view.
4. Expand a project.
5. Double-click in a cell next to the resource and type a new number (Example: 6).
6. Within a second or two, double click in the next cell and type in a new number (Example: 8).
7. Within a second or two, double click in another cell (example 10).
Expected Results: The updated values are reflected immediately (6.00 and 8.00 respectively).
Actual Results: There is a lag for the changed values to be reflected of at least a couple of seconds. The 6 entered in the cell may take a few seconds or more to reflect as 6.00. Sometimes, the numbers entered revert back to the old numbers entered instead of taking the new values.
DE46829: New UX Timesheet Displays ETC Hours Inconsistently from Task to Task
Steps to Reproduce:
1. Create a task assignment with Fixed Loading pattern.
2. Make the assignment be prior week and future a couple of weeks and make sure there is ETC.
3. Post a timesheet for the assignment for prior week. Enter 5 hours or so to get an actual thru date so ETC for prior to Actual Thru gets dropped.
4. Open the timesheet for the current week in the Classic and New UX. Add the Task.
Expected Results: ETC is the same in both.
Actual Results: In Classic PPM, ETC shows the sum of future weeks (after current week).
DE44708: Project Allocation Team Audit Trail Last Updated Date is updated, but not Last Updated By
After running time slicing job, the PRTEAM record looks like it was last updated by an inactive user in the audit trail.
Steps to Reproduce:
1. Log in to Classic Clarity PPM as an active user (User A).
2. Make a change to the team member allocation for User B through their calendar.
3. Inactivate User B.
4. Log in as another active user (User C) and run the Time Slicing job.
Expected Results: When the Time Slicing job re-slices the data it should NOT update the 'Last Updated Date' or 'Last Updated By' fields on the PRTEAM record because this is an indirect update to the allocation data.
Actual Results: When a resource calendar is updated, it causes the Time Slicing job to re-slice allocation data based on the new resource availability The 'Last Updated Date' field is updated on the PRTEAM record because the Time Slicing job last processed the allocation data. The Time Slicing job does not update the 'Last Updated By' field. Therefore, the user interprets the event as an inactive user changed the record recently.
DE46354: After time out of a new UX session that was connected via SSO cannot reconnect
Steps to Reproduce:
1. Configure SSO with CA PPM.
2. Navigate to New UX.
3. Allow the new UX session to time out
4. Attempt to log back in.
DE47568: NEW UX - SSO Status report, 'Undefined' error when clicking the 'Reports' Sub-Tab
Steps to Reproduce:
1. Login to CA PPM.
2. Navigate to New UX.
3. Open a Project.
4. Navigate to Status Tab.
5. Click on Reports sub-tab.
Expected Results: Report gets generated and displayed on screen
Actual Results: Server generates the report and user is seen and "undefined" error on top of the screen.
DE40836: MSSQL - Load Data Warehouse - Incremental has inconsistent times of execution
Steps to Reproduce:
1. Run Load Data Warehouse - Incremental multiple times throughout the day
Expected Results: Incremental to run in a certain amount of time
Actual Results: Sometimes, especially in the morning, the job runs for 100 min, some other times 15-20 min.
DE47625: Security Fix
This security defect was resolved in this patch. The steps to reproduce the defect are omitted for security reasons.
DE45179: Email for action items
Steps to Reproduce:
1. Set up a PPM system with email server information and a default sender address so that it can send emails
2. Perform any activity that will generate an out-of-the-box- notification. I tested adding and removing a participant on a project, sending a report completed notification, submitting a timesheet, and a process manual notification. All performed the same way.
Expected Results: The FROM field will be structured so that "LAST_NAME, FIRST_NAME" or "First_Name Last_Name" in the display portion of the FROM field like most emails.
Actual Result: The FROM field in the Email Header contains the user email address in the display name portion.
DE46688: Budget reports inconsistent
Steps to Reproduce:
1. Create two (2) projects with identical cost plans.
2. Add the same actual costs to both projects.
3. Run the Load Data Warehouse job with the Full Load parameter selected.
4. Add a risk to Project 1.
5. Add an actual cost to Project 2.
6. Run the Load Data Warehouse job in incremental mode (clear the Full Load parameter).
7. Look at the table dwh_x_inv_sum_facts, Project 1 will have 0 actual costs and Project 2 will be correct
Expected results: Project 1 plan cost and actual cost should be correct
Actual Results: The cost is being 0'd out
DE47810: Custom multi-valued field empty in data warehouse after incremental load
Steps to Reproduce:
1. Run a Data Warehouse Full Load so everything is sync'd up.
2. Go to a Project that has Status Reports
3. On a Status Report, delete 1 resource off the custom MVL.
Attribute we were using is based on an out of the box resource lookup.
4. Run an incremental DWH Load.
5. The display_value field in the dwh_cmn_mv_lookup table will
be null
Expected Results: It should not remove display_value after incremental run
Actual Result: It removes display_value after incremental run
DE48074: MSSQL - Load Data Warehouse Full Load job performance on large dataset (DWH_X_RES_AVAIL_PER_FACTS improvement)
Steps to Reproduce:
1. Use a large MSSQL customer database - only reproducible on large datasets
2. Run Load Data Warehouse - Full Load - note it runs for 250+ minutes
Expected results: Load Data Warehouse - Full to take a smaller amount of time
Actual Results: Load Data Warehouse - Full takes 280-300 minutes for the customer, much of it on DWH_X_RES_AVAIL_PER_FACTS
DE41718: Data Warehouse Incremental error ORA-01452: cannot CREATE UNIQUE INDEX; duplicate keys (after applying fix for DE37008)
Steps to Reproduce:
  1. In Classic PPM, open an existing cost plan line item and period that has a planned cost that has not been updated since the last data warehouse load.
  2. Add a financial transaction but do not post it.
    The application updates the cost plan line item for the same period in Step 1.
  3. Start the Load Data Warehouse job in incremental mode (clear the Full Load parameter).
  4. Post the financial transaction from Step 2.
  5. Verify the Load Data Warehouse job has finished running.
Expected Results: The job to be successful.
Actual Results: The job fails with ORA-01452: cannot CREATE UNIQUE INDEX; duplicate keys found.
Issues Fixed in 15.5.1.1
DE45213: "Could not load project" and Login Page Appear When Opening a Project in the New User Experience
An additional symptom that you might experience is an API-1018 error when attempting to replace a role with a resource in the New UX.
Steps to Reproduce:
1. In a web browser, navigate to http://<server>/niku/nu#action:npt.overview (enter your own values).
2. Log in as an administrative user.
3. Adjust the URL in your browser to http://<server>/pm (on your same server).
4. Log in as an administrative user.
5. Click a project.
Expected Results: The project opens.
Actual Results: "Could not load project" message appears and the Login page opens.
DE45370: New UX Performance Slow in Review & Approve if you have a filter applied and do not have 
Timesheet - Approve All
 rights
Steps to Reproduce:
1. Navigate to New UX Timesheets in PPM as a user with timesheet approve rights at the instance level for 5 resources, and not Timesheet Approve - All at the global level.
2. Click on the Review & Approve tab.
3. In the Showing section, select a Resource Manager and enter a Resource Manager to filter on.
Expected Results: The list of resources appears immediately.
Actual Results: It takes about 10-20 seconds to load just 5 resources.
DE44807: In the New User Experience, incorrectly able to edit tasks associated with inactive projects on adjusted timesheets
Steps to Reproduce:
1. Create a project that is active, open for time, and track mode PPM.
2. Add a resource to the project, also open for time, and track mode PPM.
3. Create a new task on the project (open for time) and assign the resource to the task.
4. Log in as the user and navigate to the New UX Timesheets page.
5. Add the task created in Step 3 to the current timesheet and submit for approval.
6. Approve the timesheet.
7. Run the Post Timesheets job.
8. After the timesheet is posted, go back to the project created in Step 1 and make the project 
inactive
.
9. Navigate back to the posted timesheet for the user.
10. Click the Adjust button.
Expected Results: Task associated with the inactive project is read-only; the hours cannot be changed.
Actual Results: The task is editable; you are able to change the hours on the task.
DE44318: MSP New Driver Task Start Dates are changed to Actuals Thru date even though no time has been submitted on the task
Steps to Reproduce:
1. Create a project in PPM (open for time with track mode PPM)
2. Add one resource to the project team (make sure they are open for time and track mode of PPM)
3. Create 2 tasks:
Task1 (Task Start Date is in the past):
Fixed Duration with start date 7/1/2018 and finish date 7/13/2018
Assign resource to task (with 10 hours ETC)
Task2 (Task Start Date is in the future):
Fixed Duration with start date 3/25/2019 and finish date 03/29/2019
Start No Earlier Constraint of 3/25/19
Assign resource to task with 5 hours of ETCs during the time frame of 3/25/19 - 3/29/19 (future time period)
4. For the user added to the team, submit 8 hours of ETC for task1 with the last hours entered on the time sheet
Go to the timesheet for 7/9/18 – 7/15/18 in the new UX (Past time period)
Ensure Assigned Tasks is selected then click Create Timesheet
Enter 2 hours of work for 7/10, 7/11, 7/12, and 7/13
Click Submit
Click Approve
Wait 5 minutes then run the Post Timesheets job (Note that the actuals thru date on the Team tab is now 7/15/18)
5. Export the project from PPM to MSP.
6. Observe the start date for task 2.
Expected Results: Since the task start date and ETCs are in the future, the task start days stays as 3/25/19
Actual Results: The task start date changes to 7/16/18, which is the first working day after the actual thru date for the resource on the project.
DE45317: Security Fix
This security defect was resolved in this patch. The steps to reproduce the defect are omitted for security reasons.
DE46559: Upgrade fails from 15.5 to 15.5.1
Steps to Reproduce:
1. Upgrade to any PPM that includes a change in job definition to introduce a job parameter for the first time (until now the job doesn't have any job parameters).
Expected Results: Upgrade is successful.
Actual Results: Upgrade fails with error on the XML file.
DE46395: Load Data Warehouse Job Fails If Using a Custom Lookup for 'Time Entry User Lookup Field 1'
Steps to Reproduce:
1. Log in to Classic Clarity PPM as an administrator. Click Administration, Data Administration, Lookups and click New. Create a dynamic query lookup using the following SELECT statement and WHERE clause:
SELECT @SELECT:TE.PRID:[email protected], @SELECT:SUBSTR(TSK.PRNAME,1,30):[email protected], @SELECT:SUBSTR(TSK.PRNAME,1,30):[email protected], @SELECT:LANG.LANGUAGE_CODE:[email protected], @SELECT:LANG.ID:[email protected] FROM PRTIMESHEET TS, PRTIMEENTRY TE, PRASSIGNMENT ASSG, PRTASK TSK, CMN_LANGUAGES LANG WHERE TS.PRID = @WHERE:PARAM:USER_DEF:INTEGER:[email protected] AND TS.PRID = TE.PRTIMESHEETID AND TE.PRASSIGNMENTID = ASSG.PRID AND TSK.PRID = ASSG.PRTASKID AND LANG.LANGUAGE_CODE = 'en' AND @[email protected]
     Query Reference: KB000022205 
2. Click 
Administration
Project Management
Timesheet Options
.
3. Modify the Value of "User Value 1 Lookup" from the default "Time Entry User Lookup Field 1" to the new lookup you created in Step 1.
4. Run the Load Data Warehouse job with the Full Load parameter selected.
Expected Results: Job completes without issues.
Actual Results: Load DWH job fails with error [CA Clarity][Oracle JDBC Driver][Oracle]ORA-30926: unable to get a stable set of rows in the source tables While merging DWH_META_COLUMNS
DE46372: Export to Excel (Data Only) Does Not Work when Results include Negative Numbers
Steps to Reproduce:
1. For simplicity, create a custom number attribute on the Team object (this issue is also reproducible with default system attributes).
2. Go to the Team tab of an existing project and add the custom number attribute to the Team list view.
3. Type in a negative amount for this custom field on the list view (for example -25).
4. Click Save.
5. Click Options, Export to Excel (Data Only).
6. Open the downloaded file.
Expected Results: The file opens in a spreadsheet application such as Microsoft Excel.
Actual Results: The file does not open and throws one of the following two errors:
  • "The file is corrupt and cannot be opened."
  • "Problems During Load, Problems came up in the following areas during the load: Table".
DE42922: LDAP - Synchronize Obsolete Users job taking longer than usual
Steps to Reproduce:
1. Enable LDAP integration with a large number of users (for example, 30,000 users).
2. Run the Synchronize Obsolete Users job.
3. Record the time for completion.
4. Use the new option of group membership based sync.
5. Run Synchronize Obsolete Users job.
6. Record the time for completion.
Expected Result: Complete it in minutes.
Actual Result: Took more than two hours to synchronize.
DE46043: Modern UX Project Tile Labels for Blueprint Visuals Are Not Translated
Steps to Reproduce:
1. Log in to the CA Clarity PPM New User Experience.
2. In the main menu, navigate to Classic PPM.
3. Set your Language account settings to a non-English language (for example, Spanish).
4. Switch back to the New User Experience.
5. In the main menu, click Projects.
The project tiles appear. 
Expected: Labels are translated.
Actual: Everything is translated into Spanish except for the labels below the visual gauges.
DE45714: Avatar Error in New User Experience
Additional symptoms that may be seen: Unable to view Status Reports or Attachments in the New UX
Steps to Reproduce:
Prerequisites: Have IIS Configured in the environment.
1. In the New UX, click on the application drop-down menu where your name appears at top right and select Settings.
2. On the Profile page, click UPLOAD.
4. Browse and select an image file to upload.
Expected Results: Avatar displays successfully and no error is generated.
Actual Results: A message states "Avatar Uploaded Successfully" but is followed by a "Could not load the avatar image" error and the image does not appear in the New UX.
DE45950: Existing custom sub-objects that are API enabled through the UI can not be found on Blueprint Modules
Steps to Reproduce:
1. In Classic PPM, click Administration, Studio, Objects.
2. Create a new object Sub1. This is a subobject of the master project object.
3. Select the API Enabled check box.
4. Save the object.
5. Create a new object Sub2. This is a subobject of the master project object
6. Do not check the API Enabled check box.
7. Save the object
8. Select the API Enabled check box.
9. Save the object.
10. Log in to the Modern UX.
11. In the main menu, click Administration, Blueprints.
12. Open a blueprint.
13. Click Modules.
Expected Result: Both Sub1 and Sub2 subobjects are available to be added as modules.
Actual Result: Only Sub1 is available. The existing subobject that has been API-enabled through the UI is not available for blueprint modules.
DE45859: SSO Logout URL value is not being applied when logging out on the Modern UX
Steps to Reproduce:
1. Configure SSO with CA PPM. (This issue was observed only when SSO was integrated with the on-premise edition of CA Clarity PPM.)
2. Navigate to New UX.
3. Click Logout.
Expected Results: Application logs out and the Logout URL specified in CSA is displayed.
Actual Results: Logout navigates to the Home page on New UX.
DE46001: Calendar Date Picker Widget does not show Japanese correctly
Steps to Reproduce:
1. Log in to the application where the user has their account settings for Language set to Japanese.
2. Go to any page that has a calendar date picker user interface control.
3. Click on the calendar icon and see the labels are not translated.
4. Click on the header pull down to see Months and Years and the labels are not translated.
Expected Results:  Calendar date picker labels show Japanese correctly.
Actual Results: Calendar date picker labels do not show Japanese correctly. Month, Week Day, and Today are shown as ? or ??.
DE44336: Copy Tasks from Previous Week adding Other Work
Steps to Reproduce:
1. Add user to Other Work Team.
2. Post time without Other Work item.
3. On following week, populate the timesheet with copy from previous time period.
Expected Results: Other work should not be on there.
Actual Results: Other work item shows.
Cumulative Patch Summary
Because patches are cumulative, when you install a single patch, it includes all the fixes in all previous patches, keeping you up-to-date.
Clarity PPM Base Release
15.3
15.4.0
15.4.1
15.5.0
15.5.1
Latest Patch:
 
15.3.0.5
15.4.0.1
15.4.1.4
15.5.0.1
15.5.1.4
JasperReports
 
6.4.2_5.4.2.15
or
7.1.0.6.1.0.X
6.4.2_5.4.2.15
or
7.1.0.6.1.0.X
6.4.2_5.4.2.15
or
7.1.0.6.1.0.X
6.4.2_5.4.2.15
or
7.1.0.6.1.0.X
7.1.0.6.1.0.X
Changes Introduced by the 15.5.1.x Patch
The following changes are introduced only the first time you install 15.5.1.1 or any newer edition of this cumulative patch. Because patches are cumulative, if you are installing a subsequent version of this patch for the first time, your users might encounter the following functionality as though it were new.
New! The Clarity PPM Brand is Back
With the acquisition of CA Technologies by Broadcom, the original 
Clarity
 product name, formerly rebranded as CA Clarity PPM and CA PPM, has been restored in the 15.5.1.1 patch. The product is now branded Clarity Project and Portfolio Management, or simply Clarity PPM, as seen in the user interface.
Historic references with mixed branding will continue to appear throughout the application and in the documentation, online community, Support KB articles, videos, and other content.
New! Introducing the Phoenix UI Theme
The 15.5.1.1 patch also introduced the new Phoenix UI theme designed to invite Classic Clarity PPM users into the modern aesthetics and styling of Clarity PPM (formally introduced with 15.1 as the 
New User Experience
).
To learn more about applying UI themes, see CA Clarity PPM Studio UI Themes in the Reference section of the documentation.
Extension of Digital Certificate for MSP and OWB Integrations
This patch includes an updated digital signature for optional Clarity PPM integrations with Microsoft Project (MSP) and CA Open Workbench (OWB). The original expiration date of April 5, 2019 has been extended until 2020. The embedded certificate is exclusively available through the installer. (CA Support can trace this change using DE44578.) 
Special Instructions for DE46395: Load Data Warehouse Job Fails If Using a Custom Lookup for 'Time Entry User Lookup Field 1'
 
If you encounter defect DE46395 in your current 
unpatched
 environment...
  • ...and you are a Clarity PPM SaaS customer, contact CA Support to resolve this issue.
  • ...and you are a Clarity PPM on-premise administrator, follow these steps 
    before
     you apply the 15.5.1.x patch for the first time only; skip this section if you already performed these steps for a previous version of this cumulative patch):
  1. Read CA Support KB00022205 and KB00126406.
  2. After reviewing the considerations, decide if you want to continue using a custom lookup for "User Value 1 Lookup" on the 
    Administration
    Timesheet Options
     page. We recommend that you use the system-defined 'Time Entry User Value 1' static lookup. However, the use of a custom dynamic query lookup on the Timesheet Entry is possible with specific requirements and special considerations for storing and displaying data for this field.  
  3. If you decide to use a custom lookup, perform the steps in the KB articles.
    1. Verify that your custom lookup is defined with the required structure for the data warehouse as documented in KB000022205.
    2. Clean up the metadata 
      before
       applying this 15.5.1.x cumulative patch for the first time as documented in KB000126406. Delete two rows from the DWH_META_COLUMNS table as directed.
  4. Run the Load Data Warehouse job and verify that it has successfully completed 
    before
     applying this 15.5.1.x patch. 
  5. Apply the 15.5.1.x patch for the first time on top of 15.5.1.0.
  6. After changing the User Value 1 Lookup field, run the Load Data Warehouse job again with the 
    Full Load
     parameter selected.
How to Install the Patch:
  1. Back up all files and the database on the target system.
  2. On the CSA server, copy the installer into a temp directory.
  3. Navigate to the temp directory and enter the following command to extract the contents:
     
      jar xvf <patch_jar_file>
     
  4. Stop all local nsa, app and bg services:
     
      service stop nsa app bg 
     
    Note: Allow databases and reports to continue running.
  5. From the temp directory, enter the following command to execute the installer script:
     
      install.bat
     
    or
     
      install.sh
     
  6. Follow the remaining on-screen instructions to complete the installer script.
  7. Start all services:
     
      service start all
     
  8. If you are running multiple servers in a cluster:
    1. Log in to the CSA and go to the All Services page to shut down any remote app and bg services.
    2. Go to the Distribute All page, select remote servers, and click Distribute.
    3. Return to the All Services page to restart services when the distribution is complete.
    IMPORTANT: If you currently use or want to use the new Jaspersoft Reports and Data Warehouse, choose Step 9 or Step 10. If you do not use these features, skip Steps 9 and 10.
  9. If you are applying this patch and you have already configured Jaspersoft Reports and the Data Warehouse:
    1. From <install_dir>/bin directory command prompt, enter the following command to generate keystore:
       
      admin jaspersoft keystore
    2. Copy the keystore files generated in <install_dir>/config directory to <Jaspersoft Tomcat Instance Directory>/webapps/<jaspersoftContext>/WEB-INF/config
    3. Enter the following command to upgrade the report content:
      admin content-jaspersoft csk -userName <superuser> -password <password> upgrade -retryCount 50
    4. Restart all PPM services.
    5. Run the Load Data Warehouse Access Rights job.
  10. If you are applying this patch and you want to use the new Jaspersoft Reports and Data Warehouse but have not yet configured them:
    1. From <install_dir>/bin directory command prompt, enter the following command to generate keystore:
      admin jaspersoft keystore
    2. Copy the keystore files generated in <install_dir>/config directory to <Jaspersoft Tomcat Instance Directory>/webapps/<jaspersoftContext>/WEB-INF/config
    3. Enter the following command to install the release content:
       
      admin content-jaspersoft csk -userName <superuser> -password <password> -retryCount 50
      This command imports 
      jaspersoft_csk.zip
       followed by the file that has patch content (file name for patch content contains 
      jaspersoft_csk_upgrade
      ).
    4. If you encounter any error during the import of the patch content, enter the following command to re-import the patch content:
      admin content-jaspersoft csk -userName <superuser> -password <password> upgrade -retryCount 50 force
    5. Configure the Data Warehouse section in CSA. See CSA: Clarity PPM System Administration at docops.ca.com/ppmop.
    6. Enter the following command from the <install_dir>/bin directory command prompt to apply the data warehouse patch content:
       
      admin db dwh-upgrade -Dupgrade.phase=maintenance
    7. Restart all PPM services.
    8. Run the Load Data Warehouse Access Rights job.
How to Uninstall the Patch:
Follow these steps: 
  1. Stop all local nsa, app, and bg services:
     
      service stop nsa app bg
     
  2. Restore the installation files and database from the backups above.
  3. Start all services:
     
      service start all
     
  4. If running multiple servers in a cluster:
    1. Log in to CSA and go to the All Services page to shut down any remote app and bg services.
    2. Go to the Distribute All page, select remote servers and click Distribute.
    3. Return to the All Services page to restart services when the distribution is complete
README: JasperReports Server 6.4.2 for Clarity PPM
The 6.4.2 installer is supported only as a required middle step when upgrading from an older release to JasperReports 7.1.
JasperReports Server 6.4.2 is a maintenance release that includes security updates and improvements requested by customers. CA PPM 14.3 and higher on-premise customers must use the CA PPM Jaspersoft installer to apply it, which is a customized wrapper written on top of the original third-party installer. 
Only the CA installer can be used to install Jaspersoft and integrate it with CA PPM for reporting. Do not install software, download patches, or apply hot fixes directly from TIBCO.
: After installing or upgrading to CA PPM 15.5, you must install or upgrade your reporting environment using the installer provided by CA. On-Premise customers can upgrade the same database to 6.4.2 or perform a fresh install with 6.4.2 (and optionally migrate their reporting content). You cannot remain on JasperReports 6.2.1. Due to security fixes, we recommend that you upgrade to 6.4.2 as soon as possible. JasperReports Server 6.2.1 is not supported beyond June 28, 2018 when it reaches its End-of-Support (EOS) milestone.
JasperReports 6.4.2 is no longer supported with Clarity PPM 15.5.1 and higher. We include it here only because it is required for upgrades from older releases of CA PPM as an interim step in upgrading from an older release of Jaspersoft to the new version (currently 7.1).
The 6.4.2 update resolves a number of security vulnerabilities associated with 6.2.1, supports same-database upgrades from the previous 6.2.1 release, and introduces new dashboard improvements. 
Highlights of this release include:
  •  
    New Supported Platforms
    : The following components included in the installer are updated: Apache Tomcat 8.5.20, Oracle JDK 8 version 1.8.0_144 (8u144), PostgreSQL 9.3.18, and Spring Framework 3.2.18.
  •  
    Dashboard Enhancements
    : Dashboards can now be scheduled (limited support; do not over-schedule). Dashboards also support hyperlinks for dashlets that can replace the current dashboard with a web page, report, dashboard, or ad hoc view. New formatting options for text dashlets are also available. New Undo, Redo, and Undo All buttons on the dashboard toolbar allow you to undo and redo recent changes made to the dashboard, including changes to input control values. You will also see new Time-Date wildcards for dashlets. Image dashlets have a Browse button for selecting images from the repository.
  •  
    Import-Export Enhancements
    : Organization admins can now export individual resources or entire folders from the repository page. Superusers also have new options to export resources and folders without full paths or dependencies, so that the resulting catalog can be imported by organization admins. A new Include Dependencies option is available when exporting. In Jaspersoft 6.2.1, the export.zip contained all the dependencies.
     image2018-2-28 10:27:38.png 
  •  
    Jaspersoft Studio Enhancements
    : Our advanced report designer now supports improved customizers for JFreeCharts in the JasperReports Library:
    • New chart customizers classes for working with specific chart types.
    • Support for configurable chart customizers, which let the user enter values at report runtime.
    • Support for multiple chart customizers applied to a single chart.
    • User interface support for chart customizers in Jaspersoft Studio using a JSON file that can be uploaded.
HARDWARE AND SOFTWARE REQUIREMENTS
 
  • See the CA PPM Release Notes and TIBCO Documentation.
  • CA PPM SaaS customers enjoy an automatic upgrade to JasperReports 6.4.2.
  • CA PPM 15.4.x on-premise customers must download the CA PPM Jaspersoft 6.4.2 installer, which is a customized wrapper written on top of the original third-party installer. Only the CA installer can be used to install Jaspersoft and integrate it with CA PPM for reporting.
README: JasperReports Server 7.1 for Clarity PPM (Recommended Version)
Jaspersoft 6.2.1 was released as a patch. Jaspersoft 6.4.2 was a maintenance release; however, if you already had 6.2.1 installed, you experienced 6.4.2 as if it were a patch.
Upgrading to Jaspersoft 7.1?
 
You might perceive a same-database upgrade from 6.4.2 to 7.1 as if it were a relatively minor patch update. However, if you are upgrading from an older release, plan your migration to Jaspersoft 7.1 as if it were a full release upgrade. For example, when upgrading from 6.2.1, you will have to make 
two hops
, first to 6.4.2 and then to 7.1.
JasperReports Server 7.1 is the newest release that includes new features, enhancements, and security updates. All CA PPM SaaS customers automatically receive this new release. CA PPM on-premise customers must use the CA PPM Jaspersoft installer to apply it. The installer is a customized wrapper written on top of the original third-party installer.
After installing or upgrading to CA PPM 15.5.1, you must install or upgrade your reporting environment using the installer provided with CA PPM. On-Premise customers can upgrade the same database to 7.1, or perform a fresh install of 7.1, and optionally migrate their reporting content. You cannot remain on JasperReports 6.2.1 (supported ended June 28, 2018) or 6.4.2 (not compatible; the native reporting solution certified for 15.5.1 is Jaspersoft 7.1). Due to security fixes, we recommend that customers on all releases of CA PPM upgrade to 7.1 as soon as possible.
Highlights of the 7.1 release include:
  • Resolves a number of security vulnerabilities associated with previous releases including 6.4.2.
  • Supports same-database upgrades from the previous 6.4.2 release.
  • New Visualize.js
  • New Jaspersoft Studio data source support for domains and TIBCO Spotfire® information links
  • Improved JasperMobile App Experience
  • JasperReports engine simple text in field property expressions
  • TIBCO Datasource Visualization JDBC driver
  • Native Java 8 support (no longer supports Java 7, SOAP APIs, and Jaspersoft REST API v1.0)
  • Security Fixes
  • New Ad Hoc Views
 
HARDWARE AND SOFTWARE REQUIREMENTS
 
  • See the Clarity PPM Release Notes and TIBCO Documentation.
  •  
    Clarity PPM
     SaaS customers enjoy an automatic upgrade to JasperReports 7.1.
  •  
    Clarity PPM
     on-premise customers must download the CA PPM Jaspersoft 7.1 installer, which is a customized wrapper written on top of the original third-party installer. Only the CA installer can be used to install Jaspersoft and integrate it with CA PPM for reporting
 
Jaspersoft Upgrade Tips
:
  • For best results, always clear the browser cache on each client workstation after installing, upgrading, or patching Jaspersoft.
  • The Create and Update Jaspersoft Users job Full Sync option deletes all user folders with no content.
  • Create a small amount of custom Jaspersoft folders for each team. For example, only for PPM admins, project managers, and a few business analysts.
  • If this is not convenient, create users in PPM and place a small file inside each folder to avoid it from being deleted.
  • For better performance, do not create more than 500 user folders.