Clarity and Jaspersoft Cumulative Patch README Files

ccppmop1591
HID_clarity_readme
Patches are intended to be timely fixes and are not fully regression or integration tested, and are only tested against the issues listed below. We feel confident that this patch will resolve the defects targeted in this patch, but a patch could have adverse side effects to the function of your Clarity application. Do 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 Support.
Clarity PPM is now rebranded as Clarity. You can see the new Clarity logo on the login screen and in the New User Experience. The documentation is updated to reflect the new brand. Throughout this document, Clarity refers to the New User Experience, and Classic PPM refers to the Classic PPM Studio or Classic UI.
Prerequisites
Ensure that you install this patch only on systems that are on
Clarity
15.9 version.
Enhancements Introduced
The "Resource - Update Skills" access right is listed as 'viewer' and not 'participant’ in the License User portlet. The Global right 'Resource - Update Skills - All'; still remains a 'Restricted' License Type.
This readme contains the following sections:
2
Issues Fixed in 15.9.1.1
Here’s a quick list of issues fixed in this patch:
DE60108: The Post Timesheets Job - Java Heap Space Error
Summary: When SQL curves are used there is a possibility that the Post Timesheets job my fail with the "java.lang.OutOfMemoryError: Java heap space" error.
Steps to Reproduce:
  1. In Clarity 15.9.1, ensure you have over 1000 timesheets that are ready to be posted.
  2. Run the Post Timesheets job.
Expected Results
: The Post Timesheets job is completed successfully and the timesheets are posted.
Actual Results
: The job fails and you see the "java.lang.OutOfMemoryError: Java heap space"
DE58176: NAME Column of INV_INVESTMENTS can be NULLABLE
Steps to Reproduce:
  1. Login to Clarity.
  2. Create an Idea with NAME = Test Idea, ID = test001.
  3. Add the Idea into a Portfolio.
  4. Run a database update to nullify the NAME field in the INV_INVESTMENTS table. This action is NOT supported.
  5. Run the 'Load Data Warehouse' job.
Expected Results
: The NAME field should not allow a NULL. The DWH job should complete successfully.
Actual Results
: The value in the NAME column gets nullified. The DWH job fails with the following error: [CA Clarity][Oracle JDBC Driver][Oracle]ORA-20100: ENCOUNTERED EXCEPTION IN DWH_DIM_LOAD (DWH_PFM_INVESTMENT_MAPPING). SQLERRM : ORA-01400: cannot insert NULL into ("XXXXXXXXXX"."DWH_PFM_INVESTMENT_MAPPING"."INVESTMENT_NAME")
DE59771: Idea Values Not in Sync in Roadmaps When Coming From a NULL Value
Steps to Reproduce:
  1. Create an idea.
  2. Leave Start and Finish dates blank as those are not required. Navigate to the Idea Alignment and Risk sub-page and ensure the Goal field is blank (If your sub-pages are different/customized, you might want to pull the Goal field to the list view).
  3. Create a Roadmap, import the idea you created in the previous step and sync it.
  4. On the Roadmap Grid layout, you can see the idea has been added. The Start, Finish, and the Goal fields are blank as expected.
  5. Navigate back to the idea and populate the Start, Finish, and the Goal fields.
  6. Re-sync the Roadmap.
Expected Results
:  After syncing all values have been updated.
Actual Results
: The idea fields are not synchronized.
DE56545: Default Department OBS Not Assigned
Steps to Reproduce:
  1. Open the Idea Object, and go to the Attributes tab.
  2. Open the Department OBS attribute, and in the Default field assign a default OBS.
  3. Click Save and Return.
  4. On the same Object go to the Views tab, and click Layout: Create.
  5. Under Organizational Breakdown Structures remove Department OBS, then Save and Return.
  6. Create a new Idea. The OBS field will not display on the Create page. On the Edit page, the OBS field will be blank.
  7. If you do not perform step 5 the OBS will automatically populate with the default.
Expected Results
: The default should assign for the attribute even if it isn't displayed on the page.
Actual Results
: The default is only getting assigned if it displays on the page for the Department OBS, and perhaps other fields.
DE59199: Timesheet Gauge Ignores Resource DOH/DOT
Steps to Reproduce:
  1. Open MSP and create a New Project and create several phases with 2 tasks below each phase.
  2. Save the project to Clarity.
  3. In MSP, Select / Highlight the entire row for Phase 2 and the two tasks below it (Task3 and Task4).
  4. Copy the tasks selected and paste below Task 6.
  5. Rename the pasted phase/tasks to distinguish the tasks pasted from the tasks they were copied from. (Example, Phase2copy, task3copy, task4copy).
  6. Click the Outdent Task button for the pasted phase to move it to the same WBS level as the original Phase2.
  7. Save the project to Clarity and close the project in MSP.
  8. Open the project back from Clarity to MSP and view the tasks.
Expected Results
: Tasks appear in the same structure as prior to the save and close of the project (There are no duplicates and tasks haven’t moved unexpectedly to a different place in the project)
Actual Results
: Some tasks have duplicates and others have moved to the incorrect spot in the plan.
DE59745: Idea Convert to Project in Classic not setting Blueprint Correctly
Steps to Reproduce:
  1. Add the Blueprint attribute to the Create and Layout Views for a project.
    1. Go to Administration->Studio->Object->Project->Views.
    2. Next to Project Properties, click Layout: Create.
    3. Click the properties icon next to General.
    4. Move Blueprint from Available to Selected and click Save and Return.
    5. Click Return to navigate back to Views.
    6. Next to Project Properties, click Layout: Edit.
    7. Click the + icon next to Project Summary.
    8. Click the properties icon next to the second Project Summary line.
    9. Move Blueprint from Available to Selected and click Save and Return.
  2. Create a new project and set it as a template.
  3. Create an idea in Classic Clarity.
  4. Submit the Idea for approval.
  5. Approve the Idea.
  6. Add the Blueprint field to the Idea list view.
  7. Assign a blueprint to the Idea created in step 4 and click Save.
  8. Click on the Idea.
  9. Click Convert.
  10. Under Investment Type select Project from Template and click Next.
  11. Select the template created in step 2 and click Next.
  12. View the Blueprint value on the Create Project page.
Expected Results
: Project Blueprint (from template) is displayed.
Actual Results
: Blueprint assigned to the Idea is displayed. If you click save, the Blueprint value changes to blank. From the Project list view, if you add the Blueprint field there, the Blueprint displays as the idea’s Blueprint.
DE59820: Cannot enable API settings on a Sub Object of a Sub Object
Steps to Reproduce:
This issue happens only in environments that need to be upgraded to 15.9.1.
Steps to Reproduce:
  1. Create a new Object, and make it a Sub Object of Status Report. Note that the Status Report is a Sub Object of "Project".
  2. Attempt to enable API on the Object and click Save.
Expected Results
: The Object should be enabled for API usage.
Actual Results
: An error is received: "ODF-0248: Cannot API enable custom sub-object."
DE59814: Cannot Use Parameterized Lookup at the Third Level Object in Clarity
Steps to Reproduce:
  1. Under the Master Object: Project Create a Child object: "Deliverables" "visa_deliv_prj_l2".
  2. Under the Master Object: Project Create a Child object: "Deliverables" "visa_deliv_prj_l2".
  3. Create an attribute on the Funding object: "Funding Department" --> API Attribute id: "v_fund_dept" Lookup Parameter: prj_id ----> odf_grand_parent_id.
  4. Navigate to Clarity, Project List, Open a Project.
  5. Go to the Deliverables tab.
  6. Select a Deliverable.
  7. In the Deliverable detail, select "Funding".
  8. You will get an error: "One or more parameters 'param_prj_id' are not API enabled. You may see unexpected results."
Expected Results
: You should be able to use parameterized look up at the third level object in Clarity.
Actual Results
: Error received when using parameterized look up at the third level object in the Clarity.
DE59798: Several Views in Clarity stopped working after upgrading to 15.9.1
Steps to Reproduce:
  1. Log into Clarity.
  2. Set your last view as one of the 3 "bad" views.
  3. Exit Clarity.
  4. Launch Clarity from Classic PPM.
  5. Choose the Project list page.
  6. Click on the view dropdown. The field becomes squished but through some odd workarounds I can select the one "good view".
  7. Select that view.
  8. The page still does not show results.
  9. Refresh the page, and results show.
  10. Flip back to the "bad" views, and data now shows.
  11. But if you open a project from one of the "Bad" views, and then choose to return to the list, the problem starts all over.
Expected Results
: Views in the Clarity are not broken with the upgrade to 15.9.1
Actual Results
: Views in the Clarity that worked perfectly fine in 15.9.0 are not broken with the upgrade to 15.9.1
DE59834: Per-Period Metrics Selections Cause All Rows in the Grid to be Removed Due to Column/Row size limit
Steps to Reproduce:
Prerequisite: Ensure you have 10 years monthly Fiscal Periods created (Example Monthly Fiscal periods from 2017-01 through 2028-01.
  1. Create a project in Clarity.
  2. Go to the Staff tab and add at least one team member.
  3. Click on the ‘View Options’ dropdown.
  4. Select 3 fields in PER-PERIOD METRICS (IE Allocation, Actuals, ETC).
  5. For Periods select Months.
  6. Start Period: 2018-01.
  7. End Period 2027-01.
Expected Results
: Rows for staff members display with the added Per Period Metrics selected.
Actual Results
: The Staff rows are removed and the “No Rows to Show” message appears.
SQL Curve Performance
Steps to Reproduce:
  1. Create a project with team members.
  2. On the Staff Tab, select Remaining Availability in Per-Period Metrics.
  3. Set Periods = Months.
  4. Start Period: January 2020.
  5. End Period: February 2022.
Expected Results
: Results return in a reasonable amount of time.
Actual Results
: Page hangs for about 5 minutes with the “Loading data..Please wait” message.
DE60039 - OOTB Time Slicing Group By Scheduled Job Not Working
Steps to Reproduce:
  1. Upgrade to Clarity 15.9.1.
  2. Make sure the OOTB job Time Slicing by Group By is running as scheduled.
  3. Go to the Clarity Financial Module for a project that has an existing cost plan.
  4. Open a plan to see the plan details.
Expected Results
: Planned costs show correct values.
Actual Results
: Planned costs are blank.
DE59686: Timesheet Review and Approve Drop Down Text Color Issue
Steps to Reproduce:
  1. Login into Clarity.
  2. Navigate to Timesheets,  Review & Approve tab.
  3. Dropdown text is not readable.
Expected Result
: The Text must be readable.
DE59337: After fixing DE55011 Clarity - Create project performance is slow on merge in ODF_ITEM_POSITIONS.
Steps to Reproduce:
  1. Connect to a large dataset with at least 35k of projects and 50 picklists on every project (and select count(*) from odf_item_positions should be about 1.7M).
  2. Go to Classic UI and create a project. Note the time is under 5-10 sec.
  3. Connect to Clarity.
  4. Go to either Board or Grid view and enter the fields to create a new project.
Expected Results
: The project to be created in a similar amount of time as in Classic.
Actual Results
: The project 'Create' action takes over 20 sec. Before the fix for DE55011, it used to take 40-50 sec, now it's better but still slower than expected.
DE59637: Post 15.9.0.1 - Time Slicing Failing Due to Deadlock Errors
Steps to Reproduce:
  1. Ensure the Time Slicing job is scheduled to run frequently.
  2. Update Allocations in Clarity.
Expected Result
: Timeslice job is successful.
Actual Results
: Timeslice job fails.
DE59946: Sql Curve Extract Function Doesn't Handle Old Curves
Steps to Reproduce:
  1. Running time slice job or time slice group by job may encounter the error on curves created early in the history of Clarity.
Expected Result
: Timeslice group by job is successful.
Actual Results
: Timeslice group by job fails.
DE59445: Multiple Projects Created On New Card
Steps to Reproduce:
  1. Log in to Clarity.
  2. Go to the 'Projects' workspace (not the 'Project Tiles').
  3. Navigate to the Board layout.
  4. Click New Card.
  5. On the right side of the screen, in the fly-out, you can populate the project information.
  6. Populate a 'Name'.
  7. Enter information in the other attributes, leaving 'ID' untouched.
On a smaller dataset environment, the ID should auto-populate once the name is entered. In larger dataset environments, the ID may get generated 'late', or sometimes not at all. This distinction is likely why the problem is not seen in smaller datasets.
Expected Results
: Only one Project should be created with the ID field auto-numbered.
Actual Results
: As you populate the separate fields, a new Project is created for each field, with the same name.
DE58448: (Reopen for DE49361) Load Data Warehouse - Incremental fails intermittently with ORA-02298: cannot validate (PPM_DWH.DWH_RDM_ITEM_POSITION_FK2) - Parent Keys Not Found.
Steps to Reproduce:
  1. On a large database of a customer who heavily uses roadmaps, schedule the Load Data Warehouse - Incremental to run every hour.
Expected results
: The job will run successfully.
Actual Results
: Once in a while the job will fail with error: [CA Clarity][Oracle JDBC Driver][Oracle]ORA-02298: cannot validate (PPM_DWH.DWH_RDM_ITEM_POSITION_FK2) - parent keys not found at org.pentaho.di.trans.steps.sql.ExecSQL.processRow(ExecSQL.java:251) at org.pentaho.di.trans.step.RunThread.run(RunThread.java:60) at java.base/java.lang.Thread.run(Thread.java:834) Caused by: org.pentaho.di.core.exception.KettleDatabaseException: Couldn't execute SQL: ALTER TABLE DWH_RDM_ITEM_POSITION ENABLE VALIDATE CONSTRAINT DWH_RDM_ITEM_POSITION_FK2
DE59201: TMA-0906 Clarity Timesheet Toaster Message Remains on the Screen
Steps to Reproduce:
  1. Create a user ResA with all rights.
  2. In Classic, go to Home, Resources, to edit the resource created in the previous step.
  3. Set the Date of Hire (DOH) as of 12/4/20 (December the 4th).
  4. Ensure the Track Mode is set to PPM and is Open for Time Entry.
  5. Create a project that spans from 11/1/20 till 12/31/20.
  6. Add ResA as a staff team member.
  7. Log into Clarity as ResA .
  8. Navigate to the Timesheets page.
  9. Go to the Nov 30-Dec 6 Timesheet.
  10. Create a timesheet with the assignments from the project.
  11. Try to enter time on any day prior to the DOH set (enter time on multiple cells). You get an error: TMA-0906: Resource ID ResA, ResA starts on 12/4/20. Creating a timesheet requires an existing, active, resource who is open for time entry and has a time track mode set.
  12. Navigate across periods, Go to the projects menu and back, Navigate across the application.
Expected Results
: The error message should disappear within a short time. I am out of the timesheet where the action caused the message.
Actual Results
: The message remains on the screen as you navigate.
DE59601: FTE 'Totals' values are Incorrect
Steps to Reproduce:
  1. Create a Project that has a date range of more than one fiscal time period January 1, 2021, through June 30, 2021.
  2. Add Staff, Tasks, and Assignments.
  3. Configure the STAFF Module with the following options:
    1. The stock number(scalar) fields for Allocation and ETC
    2. 'Totals' for Allocation, ETC
    3. Per-Period Metrics for Allocation, ETC
    4. Period Type = Monthly
    5. Start Date = Project Start
    6. Finish Date = Project Finish
  4. Set the User's SETTINGS, GENERAL to Hours View the data in Hours - the scalar values match the 'Totals'.
  5. Set the User's SETTINGS, GENERAL to Days View the data in Days - the scalar values match the 'Totals'.
  6. Set the User's SETTINGS, GENERAL to FTE View the data in FTE - the scalar values DO NOT match the 'Totals'.
  7. The 'Totals - Allocation' value shows 6 as compared to the number(scalar) Allocation value of 1 Each of the 6 Monthly Period is showing 1 FTE as expected, however the 'Totals' shows 6 when we would expect it to show 1 FTE
  8. Enter a value in the 'Totals' Allocation field to set it to 2 FTE Watch the value change from 2 to 12 (2 FTE for 6 periods) Compare this to the number(scalar) Allocation value and it correctly shows 2.
  9. Repeat for each of the different 'unit' fields on the STAFF and ASSIGNMENT Modules.
Expected Result
: The 'Totals' values match the scalar values. For 1 person that is allocated 100% the FTE =1, however the 'Totals' amount is inflated because of the number of periods shown.
Actual Result
: The 'Totals' values DO NOT match the scalar values when the view is configured to cover the entire duration of the investment.
DE59773: 15.9.1 Upgrade Failure for DWH schema when Foreign Key dwh_fin_plan_ln_fk1 is Not Present Prior to the Upgrade
Steps to Reproduce:
  1. Source version 15.9.0.1.
  2. On DWH Schema drop the Foreign Key constraint dwh_fin_plan_ln_fk1.
  3. Run the upgrade to 15.9.1.
Expected Results
:- Upgrade completes successfully and re-creates the foreign key constraint dwh_fin_plan_ln_fk1.
Actual Results
:- Upgrade fails during DWH Post-Upgrade with below error Process - post-upgrade: POSTUPG_FOREIGN_KEYS.xml org.postgresql.util.PSQLException: ERROR: column "plan_key" referenced in foreign key constraint does not exist Where: SQL statement "ALTER TABLE DWH_FIN_PLAN_LN ADD CONSTRAINT DWH_FIN_PLAN_LN_FK1 FOREIGN KEY (PLAN_KEY) REFERENCES DWH_FIN_PLAN(PLAN_KEY) ON DELETE CASCADE"
Install the Patch
If you are an on-premise customer, download the patch from the Download Center on the Broadcom Support site.  If you are a SaaS customer, contact Broadcom Support.
  1. Back up all the 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.
  4. Enter the following command to extract the contents:
    jar xvf <patch_jar_file>
  5. Stop all local nsa, app and bg services using the following command:
    service stop nsa app bg
    Note: Allow databases and reports to continue running.
  6. From the temp directory, enter the following command to execute the installer script:
    install.bat or install.sh
  7. Follow the remaining on-screen instructions to complete the installer script.
  8. Start all services:
    service start all
  9. If you are 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 All Services page to restart services when the distribution is complete.
Uninstall the Patch
  1. Stop all local nsa, app, and bg services using the following command:
    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.