CA Clarity PPM 15.4.1.4 Patch and Jaspersoft 7.1 README Files

Cumulative patches for cappm 15.4.1 and updates to Jaspersoft components for PPM are periodically available. Before applying a patch, see the README for important information.
ccppmop1541
Cumulative patches for 
Clarity PPM
 15.4.1 and updates to Jaspersoft components for PPM are periodically available. Before applying a patch, see the README for important information.
  • SaaS Customers:
    Contact CA Support to request and schedule patch installation on specific CA PPM instances in the CA 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 Advanced Reporting environments. For example, a 15.1 environment on Jaspersoft 6.2.1 would apply patches for 6.2.1, followed by the 6.4.2 maintenance release, and then the 7.1 update.
This image reminds you to install the latest CA PPM patch.
2
 
HID_clarity_readme
SaaS customers can contact CA Support to request and schedule patch installation on their CA PPM instances in the CA On Demand Portal. Any fixes for reports are automatically deployed in your SaaS environment. For on-premise environments, to install a patch and update reporting content, see the instructions in the README on this page.
Clarity PPM
 15.4.1.x Cumulative Patch Summary
Because patches are cumulative, when you install a single patch, it includes all the fixes in all previous patches.
Patch GA Date
Patch GA Announcement
Feb 27, 2019
Dec 5, 2018
Oct 10, 2018
Aug 15, 2018
General Availability (GA) indicates the software has been released for public consumption.
: CA PPM 15.4.0.0 base release customers have the following options:
  • OPTION A
    : Apply the 15.4.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.4.0.1 patch, and then apply the 15.4.1 service pack and the latest cumulative patch.
  • OPTION C
    : Skip the 15.4.0.1 patch and apply the 15.4.1 service pack on top of 15.4.0.0. Then apply the latest 15.4.1.x cumulative patch (such as 15.4.1.4 in March 2019).
In addition to providing the same fixes delivered in the 15.4.0.1 patch, the 15.4.1 service pack includes new features and enhancements that extend your 15.4 product. See the CA PPM 15.4.1 Release Notes. Product release schedules do not include a 15.4.0.2 patch target; however, 15.4.0.1 remains a supported option (see
OPTION A
above).
To switch the documentation, select a release such as 15.4 or 15.4.1 from the
Versions
menu at the top of this page.
CA PPM 15.4.1.4 Cumulative Patch README File
4
3
Version #: 15.4.1
Patch #: 4
**** NOTE *************************************************************
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.
***********************************************************************
INCLUDED FILES:
---------------------------------------------
README.txt -> This file
install.sh -> Unix installer
install.bat -> Windows installer
install.xml -> Ant install script
PRE-REQUISITE - ADDITIONAL NOTES:
------------------------------------------------------
- Install only on systems running the version stated above.
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 available exclusively through the patched installers for MSP and OWB. (CA Support can trace this change using DE44578 and DE46638.) 
image2019-2-22_10-8-21.png
-------------------------
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:
--------------------------
  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.
--------------------------------------------
Issues Fixed in 15.4.1.4
--------------------------------------------
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 server).
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.
DE44318: MSP New Driver: Task Start Dates are changed to Actuals Thru date even though no time was 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.
DE43118: IRR for Ideas not Calculating in Some Scenarios
Steps to Reproduce:
1. Create an idea with dates 1/1/2018-12/31/2021
2. Financially enable the idea and set Cost of Capital to 0.
3. Create a cost plan (can be manual). Again use Annual Type (2018-2021).
4. Enter values as follows:
2018: 1,000000
2019: 75,000000
2020: 72,000000
2021: 72,000000
5. Create a benefit plan. Period Start: 2019 - Finish: 2026
6. Add a manual line with these values:
2019: 2,000000
2020: 2,000000
2021: 13,000000
2022: 97,000000
2023: 97,000000
2024: 97,000000
2025: 97,000000
2026: 97,000000
7. Linked benefit plan to cost plan
8. Check IRR on Financial Summary
Expected Result: IRR is populated
Actual Result: IRR is blank. Note there is a payback period. Breakeven is 2/29/2024
DE44708: Project Allocation Team Audit Trail Last Updated Date is updated, but not Last Updated By
Steps to Reproduce:
1. Log in as active User A.
2. Make a change to a 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.
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.
DE42701: Cannot Select Investment-Specific Charge Codes in New User Experience Financial Plans
Steps to Reproduce:
1. Log in to the Classic user interface for CA Clarity PPM and click Administration, Project Management, Settings. Select the "Enable Investment-specific Charge Codes" check box.
2. Create a project.
3. Navigate to Properties, Charge Code page.
4. Create a new charge code.
5. Navigate to the New UI. Open the project created in step 2. Navigate to "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 4.
Expected 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. It is however selectable in the Old UI.
DE42821: No Results Found when trying to filter using Virtual Attribute
Steps to Reproduce:
1. Create MVL virtual attribute on team object
2. Add few values in the virtual attribute
3. Add the virtual attribute in filter layout
4. Try filtering with virtual attribute
Expected Results: Records should be returned based on the filter value.
Actual Results: 'No Results found' error appears.
DE42548: Expired Request Message Occurs If You Click the Add Tasks Button on a Timesheet
When a user follows a link in the Returned Timesheet notification email and logs into their SSO-enabled CA PPM environment, and then clicks 'add tasks', they get an expired request message.
STEPS TO REPRODUCE:
1. Receive a default Returned Timesheet email notification.
2. Click the link "go to Timesheet"
3. Log into the environment using SSO credentials
4. Click 'Add Tasks' button on the timesheet.
Expected: The list of available tasks to add to the timesheet should appear in a List view.
Actual: The Expired Request message appears in the user interface.
Workaround: Click the Back button and click the "Add Tasks" button again. The expired request message disappears. The issue only occurs with a new browser session (when the user is logged out of the application).
DE42036: Timesheet hours for Incidents not showing in Capacity Overview Portlet
Steps to Reproduce:
1. Associate an incident with an NPIO. Tested with Application.
2. Assign resource to team and make sure they have the rights to post time to the associated incident
2. Have resource enter time to the incident.
3. Approve and post timesheet
4. Check application
5. Click Home, Resource Management, Capacity Overview portlet and configure the TSV to show Incident Actuals.
Expected Result: Incident Actuals show in TSV
Actual Result: Incident Actuals do not show in TSV.
DE44357: Cost Plan Issue - Non-standard fiscal periods do not follow expected Edit 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 allows edits.
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.
DE45317: Security Fix
This security issue was resolved in this patch. The steps to reproduce the issue are omitted for security reasons.
DE45555: Locale formatting is not correct in the denominator of the Timesheet Review & Approve Row & Fly-out
Steps to Reproduce:
1. Log in 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 comma
Expected Results: All numbers where a comma should appear have: "," 
Actual Results: Numbers appear with both comma and decimal points (for example, 10,50/37.5).
--------------------------------------------
Issues Fixed in 15.4.1.3
--------------------------------------------
DE41789: Icon Display Mappings Not Exported to Excel
Steps to Reproduce:
1. Log in to Classic CA PPM and click Administration, Studio, Objects. (This behavior applies to all objects; however, this example uses the Project object.) 
2. Create an attribute of type Number.
3. Choose Icon Display Mapping.
a. Map 0 to 100 to "Down Arrow - Red"
b. Map 101 to 200 to "Up Arrow - Green"
4. Create another attribute of type Number
5. Choose "Colour" Display Mapping
a. Map 0 to 100 to "Black"
b. Map 101 to 200 to "Red"
6. Create a Portlet out of the Project object
7. Display the attributes created in Steps 2 and 4 in the Portlet
8. Configure the Portlet. Go to "Fields" sub page of the Layout view. Configure the above attributes to display as both "Image" and "Value"
9. "Export to Excel" from the portlet
Expected Result: Color Display Mapping has two subcolumns in Excel - "Value" and "Color". Icon Display Mapping also has both "Icon" and "Value" exported.
Actual Result: Icon Display Mapping just exports the Image, and leaves out the Value.
DE42121: bg-ca.log error after upgrade to latest version
Steps To Reproduce:
1. Create a process with GEL script that does not define any action.
2. Run the process on Process tab under Organizer.
3. The process runs successfully.
4. Verify bg-ca.log.
Expected Results: We do not have any errors on bg-ca.log.
Actual Results: bg-ca.log populates the success process run details, as error information.
DE43018: New UX Users Can Submit Over 40 Hours In One Week Through the Timesheet Hook
Note: This issue applies only to environments with the pre-installed Global Delivery Timesheet Hook add-in.
Steps to Reproduce:
1. Log in to CA PPM 15.4.1.
2. Navigate to New UX
3. Open a Timesheet
4. Enter 8 hours for each day from Monday to Thursday. (Press the Tab key to move to the next entry box.)
5. Enter 100 hours for Friday.
6. Directly click submit without clicking anywhere on the screen and without pressing any button on the keyboard
7. Total time submitted will be 8*hrs from (Mon-Thu) + 100*hrs (Fri) = 132hrs
Expected Result: Based on the Timesheet hook rule, the timesheet should throw an error stating not more than 40rs allowed per week
Actual Result: All the timesheet values are saved successfully without any errors
DE41903: Allocation Cost Dividing by 3600
Steps To Reproduce:
1. Log in and navigate to Projects
2. Create a New Project for 2 week
3. Associate the project to a rate matrix
4. Add resource to the team - Make sure the resource is included in the matrix
5. Make the allocation 10 hours for 1 week.
6. Run Rate Matrix job with first 3 options
7. Run the Update Cost Totals from the Team tab
Expected Result: The allocation cost should be calculated as Allocation * Rate per hour.
Actual Result: The cost is incorrectly calculated as Alocation * Rate / 3600.
DE43000: New UX 'Approve all' and 'Return all' options do not properly work with high number of timesheets to approve or return
Steps to Reproduce:
1. Submit a number of timesheets (higher than 10).
2. In the new UX for Timesheets, go to Review and Approve.
3. Select the period that has greater than 10 timesheets.
4. Click on Submitted > Approve all (or Reject all)
Expected Results: View automatically autorefreshes with 0 pending timesheets to approve or reject. All timesheets have been approved (or rejected).
Actual Results: Apparently, nothing happens. View does not automatically refresh. On manual refresh, only 10 timesheets have been approved (or rejected).
DE41901, DE44759: Rate matrix duplicates NBI_PROJECT_RES_TASK_FACTS
Steps to Reproduce:
1. Create Rate Matrix with 3 columns. Only two are probably needed but this example has 3
- Resource
- Resource Class
- Input type code
2. Use a financially enabled resource for your example, (resource used here is'lw') and create the matrix rows as follows:
- 1/1/90-1/22/17 Resource: lw
Resource Class: *
Input Type Code *
Rate/Cost: 50.00
- 1/23/17-5/26/18 Resource: lw
Resource Class: *
Input Type Code: *
Rate/Cost: 34.00
-12/1/17-12/31/25 Resource: *
Resource Class: *
Input Type Code: Band3
Rate/Cost: 50
3. Create a project with dates 1/1/2018 - 12/31/2018
4. Add team member used in Step 2
5. Create a task with dates 1/1/2018 to 6/30/2018
6. Assign the resource to the task to cover the whole task range
7. Run Rate Matrix Extraction job with first 3 options
8. Query NBI_PROJECT_RES_TASK_FACTS
Expected Result: Each FACT DATE will have one record for the task
Actual Result: FACT DATES which overlap based on matrix have 2 dates.
DE43623: Updates to Roadmap Items Can Cause the Load Data Warehouse Job to Fail
Steps to Reproduce:
1. Trigger the Load Data Warehouse job.
2. Keep creating Roadmap Items, and Roadmaps or Keep changing Roadmap Item positions
Expected Result: Load Data Warehouse job completes without any issues
Actual Result: In two scenarios, a Foreign Key constraint error occurs. These errors were thrown in two different instances of LDWH job, and it covers two scenarios – one of new Items causing it, and another one of change in Item positions causing it.
--------------------------------------------
Issues Fixed in 15.4.1.2
--------------------------------------------
DE38175: New User Experience Detailed Timesheets Do Not Display All Data for Submitted Timesheets
Steps to Reproduce:
1. Submit PPM Timesheet for a labor resource by adding 12 or more tasks.
2. Login to New Timesheet UX as the Resource Manager (RM) for the resource who submitted Timesheet in step one above and navigate to 'Review and Approve' page.
3. Click on the name of the resource to open a Timesheet pop up window. Here all the listing of Submitted Timesheets are displayed.
4. Now click on the 'Detailed Timesheet' button to review details all timesheet data entered.
Expected Results: The listing of all the submited Timesheet in step one to be displayed.
Actual Results: The listing on Detailed Timesheet page displays only the first eleven items of submited Timesheets.
DE43321: Slow Performance with New User Experience Timesheets
Steps to Reproduce:
1. Log in to New UI and navigate to new UI Timesheet page 
2. Ensure a user has Timesheet Navigate Right that is inherited at the OBS level 
3. Ensure you have good volume of resources in the system similar to the data for the customer reporting this issue
Expected Results: The page to open fairly quickly like the classic UI timesheets, expectation under 10 seconds. 
Actual Results: The timing of the new UI takes about 2 min 40 sec (initially at 14 minutes but tuned from the DB level to 2 minutes 40 seconds)
Note: This is dependent on data and may not be a problem on all databases.
DE42965: Refresh Odata Model Job Fails with Errors
Steps to Reproduce:
1. Configure the CA PPM SaaS OData integration. Create a data source using admin command.
2. Simulate the corruption of any database object. For example, introduce compilation errors in database objects. To reproduce this error, we forced compilation errors into the DWH_CMN_PERIOD_D_V database view to cause corruption.
3. Execute Refresh Odata Model job.
4. Verify the job failed with the following exception:
    The primary key column PERIOD_KEY for table DWH_CMN_PERIOD_D_V is not found or has a warning associated with it
5. Correct the database objects which have compilation errors. In this example, correct the compilation error for the DWH_CMN_PERIOD_D_V database view.
6. Run the Refresh Odata Model job.
Expected: Refresh Odata Model job is successful.
Actual: Refresh Odata Model job fails with error The primary key column PERIOD_KEY for table DWH_CMN_PERIOD_D_V is not found or has a warning associated with it.
DE43325: Why does a simple save at project level update Task last updated fields?
Steps to Reproduce:
1. Go to project properties and then Settings and make sure % Complete Calculation set to Duration or Effort.
( The issue is not reproduced if this field is set to Manual )
2. Login to CA PPM and open any project
3. Ensure project has at least 2 tasks please make sure you make one of them parent to going to Tasks->Gantt.
4. Update Stage field under project properties and notice that last updated date and last updated by has your name and the date and time when you updated the Stage. You should add Last Update By and Last Updated Date to the Task list so you can see it changing. (or simply click 'SAVE' button on any project subpage)
Expected Results: it should not update the task with the user who really was not trying to make any change to the tasks as it creates confusion to PMs.
Actual Results: it is confusing that it updates the task with the user who really was not trying to make any change to the tasks.
DE42357: When % Complete Is Modified in Microsoft Project to a Percentage Corresponding to More than One Day, % Complete Changes to 100%
Steps to Reproduce:
1. Create a project in CA PPM, open in MSP.
2. Create a new task and set the duration to 1 eweek*. (*) The issue is visible ONLY when using elapsed-time units (that is,
edays
,
eweeks
).
3. Save project to PPM and open in MSP again.
4. Change the % Complete for the task to 11%.
Expected Results: % Complete changes to 11%
Actual Results: % Complete changes to 100%, in the Gantt the task is observed as a 1 day duration task with the rest of the task length being dotted. After another save to PPM and open in MSP, the dotted line is not there, but the task remains as 100% Complete.
DE43615: Roles Do Not Appear on New User Experience Staffing Page
Steps to Reproduce:
1. Log in to PPM New UX.
2. In the main menu, click Staffing.
3. Switch to the Investments-to-Resources view.
4. Expand any project and click Add (the plus + icon).
5. In the Search Roles field type DBA (or any role name) and select the role to add it to the project. Note that you get a message indicating the resource was successfully added to the team.
6. View the list of resources under the project you just added the role to in the Investments to Resources portlet
Expected Results: The role you added appears under the project.
Actual Results: The role does not appear. Additionally, if you collapse the project and then expand it, when you click the Show More button, it does not do anything and the count in the Show More shows that it is only showing the resources, and any roles are missing from the view. Example: If the project has 3 resources, and you added one role, it will say "Showing 3 of 4"
DE42689: Service Planned Benefit data gets zeroed out on the portfolio investments if a service is updated via XOG
Steps to Reproduce:
1. Go to Home > Service Management > Services
2. Create a service "Rafa Srv"
3. On the Financial Summary Page > Populate the Planed Cost and Planned Benefit data
4. Home > Portfolio Management > Create a portfolio
5. On the Contents Editor tab and the service above and Sync the portfolio
6. Go to the portfolio Investments tab and look to the data present. Cost plan and benefit plan data is present
7. Do a XOG update of the service with the xml below:
8. The update is successful.
9. Sync the portfolio and go back to the Investments tab
Expected Result: Service Planned Benefit data to be shown
Actual Result: Service Planned Benefit data has been zeroed out
DE42973: Incremental Load Data Warehouse Job Fails With ORA-20100: ENCOUNTERED EXCEPTION WHILE INSERTING INTO DWH_INV_PER_FACTS_LOAD
Steps to Reproduce:
1. Run the Full Load DWH job
2. Create a financial plan on a project with no plans
3. Run an incremental load
4. Add a risk on the project while incremental is running
Expected Results: Investment Period Facts should populate properly
Actual Result: Incremental Load Data Warehouse job fails with the following error:
ERROR ORA-20100: ENCOUNTERED EXCEPTION WHILE INSERTING INTO DWH_INV_PER_FACTS_LOAD. SQLERRM: ORA-30926: unable to get a stable set of rows in the source tables
--------------------------------------------
Issues Fixed in 15.4.1.1
--------------------------------------------
DE41635: Time slice Job not working correctly ODF_SSL_CST_DTL_COST
Steps to Reproduce:
1. Create a Cost Plan Populate from Investment Team
2. Get the ID for the record you want to modify from fin_cost_plan_details for the plan_id (internalID of your plan)
3. Run query to verify the slices
select * From ODF_SSL_CST_DTL_COST where prj_object_id in (select id From fin_cost_plan_details where plan_id = your planID) OR select * from ODF_SSL_CST_DTL_COST where prj_object_id = (if you know the exact ID from fin_cost_plan_details)
4. Update one of the period cells
5. Make sure time slices run
6. Verify the slice updated in ODF_SSL_CST_DTL_COST
7. Repopulate the plan from Investment Team
8. Let slice job run.
9. Query ODF_SSL_CST_DTL_COST
Expected: The slice will update to the original number from the first time cost plan populated
Actual: Slice remains with the manually updated value.
DE41700: Security Fix
DE41800: Resource Enter Time instance rights not working in new UX
Steps to Reproduce:
1. Identify a resource(TUSER) who is Open for Time Entry and have rights to enter time
2. Assign this resource to tasks for time entry
3. Identify another resource (TAPPROVER)
4. Navigate to Admin -Resources -TAPPROVER profile - Instance Rights
5. Grant only the below rights
Resource - Enter Time for Resource TUSER
API - Access (global rights)
Timesheet Navigate (Global rights)
6. Login as TAPPROVER to the New UX timesheet
7. Search for user TUSER and click on the user Tmesheet
Expected Result: The TAPPROVER is able to enter time for TUSER as he has Resource Time Enter instance rights on TUSER
Actual Result: One of the following error messages appears:
API-1007: You are not authorized to TimesheetCarouselModel resource(s). Contact your system administrator for necessary security rights. or API-1007: You are not authorized to process request. Contact your system administrator for necessary security rights.
DE42065: Unable to switch from the Task Board to the List View on the Tasks Page if you Navigate From the Staff Page
Steps to Reproduce:
1. Log in to the
New User Experience
 in CA PPM SaaS.
2. In the main menu, click Projects.
3. Open a project.
4. Click Tasks.
5. Switch from the Board View to the List View.
6. Changes are successful
7. Go to the Staff page.
8. Go to the Tasks page.
9. Switch from the Board View to the List View
Expected: Tasks are loaded and you can switch between views.
Actual: Tasks are not loaded. The screen is frozen. You cannot switch between views.
DE41686: Submit button is incorrectly translated to Japanese in the New UI
Steps to Reproduce:
1. Go to Account Settings, and change language to "Japanese"
2. Login to the new UI using an account that has admin rights
3. Open the Timesheets link
3. Create a Timesheet
4. Make note of the button that is equivalent to the "Submit" button in English
Expected Results: That this button's text be translated to Japanese equivalent of "Submit"
Actual Results: This button's text is translated to Japanese equivalent to "Save and Exit", and causes confusions to end users
DE40259: Portfolio Sync Job is very slow
Steps to Reproduce:
1. Create small portfolio
2. Sync it
Expected Results: Performance time should be reasonably responsive.
Actual Results: Even small portfolios take multiple minutes.
DE39930: Default value of Relative Date type parameters is changed after a user misses a Required Field
Steps to Reproduce:
1. Login CA PPM as an Admin user.
2. Go to Home --> Reports and Jobs.
3. Under the Reports tab, search for Report Type = Resource Availability.
4. Click on the result to see the Report properties page.
5. Check that, for the "Start Date" parameter, Relative Date radio button is already selected as the default option, with the value "Start of Current Month". Remaining mandatory fields (marked with a Red Star) are all filled up.
6. Select the "period type" parameter and set the value to [--Select--], that is blank.
7. Click on Submit.
The report gives the ERROR "NJS-0119: At least one parameter is invalid. Check the parameters and submit again" which is expected as one of the required fields was left blank.
Expected Results: All the other Parameters should retain their default values as there was no change made to them.
Actual Results: Start Date parameter is now having the "Specific Date" option with a blank value.
DE42134: Error 500 - Internal Server error when filtering for Project/Idea Type in list
Steps to Reproduce:
1. Log into the CA PPM.
2. Click on Projects from within the Home tab Portfolio Management section
3. Expand the Filter and select a value from the Project Type dropdown.
4. Repeat for the Idea list clicking on Ideas from within the Home tab Demand Management section.
5. Expand the Filter and select a value from the Idea Type dropdown.
Expected Result: A filtered list based on the type will be returned for either the project or idea lists
Actual Result: The following message is displayed, 'Error 500 - Internal Server Error. The server could not retrieve the document due to server-configuration or other technical problems. Contact your site administrator.'
DE42037: IE11 Error in 15.4.1: "The server was unable to parse" when creating new attributes on object or saving Team properties
Steps to Reproduce:
1. Administration tab -> Objects
2. Open any object
3. Click Attributes tab
4. Click on New
5. You will receive this error in IE 11
Alternate Steps to Reproduce:
1. Login to PPM server.
2. Navigate to "Projects"
3. Click on the "Executive Dashboard Visibility" project.
4. Click on the Team tab.
5. Click on the Properties icon (on the far left) for any row.
6. Click "Save".
Expected Result: The page should not throw any error and data is displayed properly.
Actual Result: Error shown : "The server was unable to parse the parameters on the URL or from a form. This may be caused by too many parameters on the URL or form - the maximum allowed is 10000. The request has been rejected."
DE41626: Security Fix
This security issue was fixed in this patch.
DE37008: Load Data Warehouse - Incremental fails with ORA-01452: cannot CREATE UNIQUE INDEX
Steps to Reproduce:
1. Run a Full Data warehouse Load job.
2. Have at least 3 assignments on a task
3. Delete 2 assignments on same task
4. Update 1 assignment on the task
5. Run an incremental Load
Expected Result: The datawarehouse should reflect the change
Actual Result: The following duplication error appears:
ORA-01452: cannot CREATE UNIQUE INDEX duplicate keys found ORA-06512: at "PPM_DWH152.DWH_INV_TASK_PERIOD_FACTS_LOAD", line 56
DE41484: Staffing Telescope Does Not Display Allocation Colors for Resources in Japanese
1. In Classic PPM, set your display language to Japanese.
2. In the New User Experience main menu, click Staffing. Note: We can see the telescope icon. 
3. Click the telescope icon. 
Expected Result: The telescope displays allocation colors for the resources in Japanese.
Actual Result: The telescope does not display allocation colors for the resources in Japanese.
DE42852: Security Fix
This security issue was fixed in this patch.
JasperReports Server 6.4.2 for CA PPM README (Minimum Supported Version)
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.4 or 15.4.1, you must install or upgrade your reporting environment using the installer provided by CA. On-Premise customers can upgrade the same database to 7.1 or perform a fresh install with 7.1 (and optionally migrate their reporting content). Due to security fixes, we recommend that you upgrade to 7.1 as soon as possible. Jaspersoft 6.4.2 is also supported. JasperReports Server 6.2.1 is not supported beyond June 28, 2018 when it reaches its End-of-Support (EOS) milestone.
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.
JasperReports Server 7.1 for CA PPM README (Recommended Version)
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.4 or 15.4.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. Jasperosoft 6.4.2 is also supported. You cannot remain on JasperReports 6.2.1 (supported ended June 28, 2018). Due to security fixes, we recommend that customers on all releases of CA PPM upgrade to 7.1 as soon as possible. For a visual summary of your options, see Clarity PPM Jaspersoft 7.1 Upgrade Assistant
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 CA PPM Release Notes and TIBCO Documentation.
  • CA PPM SaaS customers enjoy an automatic upgrade to JasperReports 7.1.
  • CA PPM 15.4.1 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.
------------------------------------------------
Known Issue with Fresh Installations of Jaspersoft 7.1
In on-premise environments, you might observe the following 
Failed to execute: create index 
entry in the installation logs during a new installation of Jaspersoft 7.1.0 on Oracle 11g R2 or 12c:
[exec] [exec] init-js-db-pro:
[exec] [exec] [echo] For JDBC driver the artifactId and version properties are set:
[exec] [exec] [echo] maven.jdbc.artifactId=ojdbc8
[exec] [exec] [echo] maven.jdbc.version=12.2.0.1.0
[exec] [exec] [echo] Specified JDBC driver jar exists
[exec] [exec] [advanced-sql] Executing resource: /fs0/clarity1/install_cd/ca_ppm_jaspersoft_7.1.0/buildomatic/install_resources/sql/oracle/js-pro-create.ddl
[exec] [exec] [advanced-sql] 0 rows affected
[exec] [exec] [advanced-sql] 
Failed to execute: create index
 idx46_jiresfldr_hidden_idx on JIResourceFolder(hidden)
[exec] [exec] [advanced-sql] java.sql.SQLException: ORA-01408: such column list already indexed
[exec] [exec] [advanced-sql] 0 rows affected
[exec] [exec] [advanced-sql] Executing resource: /fs0/clarity1/install_cd/ca_ppm_jaspersoft_7.1.0/buildomatic/install_resources/sql/oracle/quartz.ddl
: You can ignore this entry. The warning appears to be alerting you about a duplicate index creation scenario; however, it is not a valid warning.
  • This warning has no impact on your installation and does not affect any Jaspersoft 7.1 functionality. 
  • CA Engineering teams confirmed that all the DDL commands are successfully executed after the reported warning.
  • The warning only appears on new Oracle installations; it does not occur with supported versions of Microsoft SQL Server 
------------------------------------------------
Express Install Steps for JasperReports Server 6.4.2 or 7.1
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. Only 
ca_ppm_jaspersoft_7.1.0_6.1.0.28.zip
on
Tomcat 8.5.30
with
JDK 1.8_171
is certified and supported. Due to performance issues, we recommend avoiding Tomcat 8.5.31.
Note
: You can also follow these steps to install or upgrade Jaspersoft 6.4.2 on your legacy 6.2.1 reporting environment (6.2.1 is no longer supported). The steps for 6.4.2 are almost identical to the steps for 7.1. For security fixes and enhancements, we recommend 7.1; however, 6.4.2 is also supported.
IMPORTANT
------------------------------------------------
JasperReports Server can be deployed as a standalone application or in a cluster for high concurrency. Clustered JasperReports Server instances use thread-safe access to their private repository database. As a result, any number of JasperReports Server instances can share the same repository and present the same environment to users.
When JasperReports Server is deployed in a cluster, it is advised to dedicate one or more JasperReports Server instances in the cluster to process the execution of scheduled reports. These dedicated instances share the same repository but are not part of the load balancer to serve web requests such as executing reports through the user interface or exploring data through ad hoc views.
For standalone deployments where only a single instance of JasperReports server is available, the instance processes report scheduling and serves normal web requests, such as report execution through the user interface or exploring data through ad hoc views.
We are providing a mechanism to make dedicated JasperReports server instances as
scheduler
instances, and the instances that are part of the load balancer to serve web requests as
non-scheduler
instances.
During installation of Jaspersoft 7.1 (or 6.4.2) for CA PPM you are prompted about a separate scheduler instance. If you answer YES, you are prompted to decide if you want to make the current instance on which the installer is being applied a scheduler instance. Select the appropriate option to make the instance a scheduler or a non-scheduler instance:
  • If
    YES
    , the installer performs the necessary configuration changes to make the current instance a scheduler instance.
  • If
    NO
    , the installer performs the necessary configuration changes to make the current instance a non-scheduler instance. To get full advantage of this configuration, ensure the non-scheduler instances are part of the load balancer.
If running only a single instance of JasperReports server, select NO.
PREREQUISITES
------------------------------------------------
- Set the JAVA_HOME environment variable and ensure the correct Java8 executable is present in the PATH environment variable.
- Create a new Jaspersoft Database/Schema before starting the installation and upgrade.
For Upgrades: 
- Export the Jaspersoft content to a zip file (exported from Jaspersoft UI only).
- Take a backup of the existing Jaspersoft instance (the Webapp) and database (Database/Schema).
INSTALLATION/UPGRADE
------------------------------------------------
1. Download the installer from the CA Download Center. Unzip ca_ppm_jaspersoft_<Jaspersoft Version>_<CA PPM Jaspersoft Version>.zip to a folder. For example, ca_ppm_jaspersoft_7.1.0_6.1.0.28.zip or ca_ppm_jaspersoft_6.4.2_5.4.2.15.zip. Unzip the installer in the root directory to avoid a long path exception.
2. Run the installer:
a) If on Windows:
Run install.bat
b) If on Linux:
Run chmod u+x install.sh
Run install.sh
------------------------------------------------
Select Installation Type:
1)
New
: This installs Jaspersoft as a brand new installation
2)
Upgrade
: This upgrades the existing Jaspersoft installation
Enter Apache Tomcat 8.5 Directory: Location on the machine where Tomcat is installed
Enter Jaspersoft Web App Name: The name of the folder where Jaspersoft is being deployed (for example, reportservice).
Enter Jaspersoft Web App Port: The JasperReports server port. The default is 8080.
Email configuration
1) Y: To setup email configuration
a) Enter Mail Server Hostname: Hostname of the mailserver (for example, mail.localhost.com).
b) Enter Mail Server Port: Port number of mailserver (for example, 25).
c) Enter Sender Email Protocol: Protocol that mail server supports. Jaspersoft currently supports smtp and smtps.
d) Enter Sender Email Username: Username of the Mail Sender (for example, test).
e) Enter Sender Email Password: Password of the Mail Sender (for example, password123).
f) Enter Sender Email Address: Sender Mail Address (for example, [email protected]).
2) N: To skip email configuration
Select the Installation Mode
1) Standalone: For standalone servers
2) Cluster: For cluster-based deployments
If you selected cluster mode:
1) Primary Node: Same as standalone installation
2) Additional Node (Web-app deploy only): Just deploys the web app only and uses primary node database/schema
Do you need a dedicated Jaspersoft instance as a report scheduler instance?
1) Yes: Choose this option if you want to have a separate scheduler instance.
2) No: Choose this option if you do not want a separate scheduler instance.
If Yes is selected in the previous step: Do you want to make the current instance as a report-scheduler-only instance?
1) Yes: Choose this option to have the installer perform the necessary configuration changes and make the current instance a scheduler instance.
2) No: Choose this option for instances that are part of the load balancer. The installer performs the necessary configuration changes and makes the current instance a non-scheduler instance.
Select DB Server type:
1) MSSQL
2) Oracle
If MSSQL is selected:
MSSQL Server Hostname: Enter MSSQL server hostname (E.g.: HOSTNAME)
Do you want to use a named instance?
a) Yes: Choose this if you are using a MSSQL server named instance for the Jaspersoft installation.
b) No: Choose this if you are using a default MSSQL server with a static port number.
If Yes is selected: 
  • Enter the MSSQL Server Instance Name: The named instance configured on the MSSQL server
  • Enter the Jaspersoft Database Name: Jaspersoft database name - default: PPM_JASPERSOFT
  • Enter the Jaspersoft Database Username: Jaspersoft Username - e.g.: PPM_JASPERSOFT
  • Enter the Jaspersoft Database Password: Jaspersoft Password 
If No is selected:
  • Enter the MSSQL Server Port Number: Database port on which MSSQL server is running - E.g.: 1433
  • Enter the Jaspersoft Database Name: Jaspersoft database name - default: PPM_JASPERSOFT
  • Enter the Jaspersoft Database Username: Jaspersoft Username - E.g.: PPM_JASPERSOFT
  • Enter the Jaspersoft Database Password: Jaspersoft Password
If Oracle is selected
1) Oracle Standalone
2) Oracle Cluster (RAC)
If Oracle Standalone is selected:
a) Enter the Oracle Database Hostname: The Oracle server hostname - E.g.: HOSTNAME
b) Enter the Oracle Database Port Number: Database port on which oracle is running - E.g.: 1521
c) Enter the Jaspersoft Database Username: Jaspersoft database - E.g.: PPM_JASPERSOFT
d) Enter the Jaspersoft Database Password: Jaspersoft password
e) Enter the Oracle SID Name: Oracle SID - E.g.: <ORACLESID>
If Oracle Cluster (RAC) is selected:
a) Enter the Oracle Database Hostname (the Oracle server hostname; for example, HOSTNAME).
b) Enter the Oracle Database Port Number (for example, 1521).
c) Enter the Jaspersoft Database Username (for example, PPM_JASPERSOFT).
d) Enter the Jaspersoft Database Password.
e) Enter the Oracle Service Name (for example, SERVICENAME).
3. Confirm the properties that you entered and wait until the installation completes.
4. After the Tomcat service starts, log in to
http://<MACHINE_NAME>:<PORT>/<JASPERSOFT_WEB_APP_NAME>
using the credentials
superuser/superuser
.
For example:
NOTE: During the installation, the license file is copied to the installation directory and user folder automatically.
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.