Clarity PPM
15.7.0.1 and Jaspersoft Cumulative Patch README Files

ccppmop157
HID_clarity_readme
Cumulative patches for
Clarity PPM
and Jaspersoft for
Clarity PPM
are periodically available. Before applying a patch, see the README for important information.
Although they are technically not patches, we list the Jaspersoft installers for
Clarity PPM
on this page because they behave like patches for existing
Clarity PPM
customers with Advanced Reporting environments.
  • SaaS Customers:
    Contact Support to request and schedule patch installation on specific
    Clarity PPM
    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 Support and follow the README instructions on this page.
This section contains the following topics:
3
Clarity PPM
Cumulative Patch Summary
Because patches are cumulative, when you install a single patch, it includes all the fixes from all previous patches.
Clarity PPM
Base Release
15.3
15.4.0
15.4.1
15.5.0
15.5.1
15.6.0
15.6.1
15.7.0
Latest Patch:
15.3.0.5
15.4.0.1
15.4.1.4
15.5.0.1
15.5.1.3
15.6.0.1
15.6.1.3
15.7.0.1
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
7.1.0.6.1.0.X
7.1.0.6.1.0.X
7.1.0.6.1.0.X
Issues Fixed in 15.7.0.1
DE50296: Delete Log Analysis Data Performance Issue
Steps To Reproduce:
  1. Login to
    Clarity PPM
    .
  2. Ensure that Tomcat Analysis job is running for more than 30 days and that daily there are atleast 300K requests that get handled.
  3. On 30th Day the count of LOG_DETAILS table should be around 9 million rows.
  4. Delete Log Analysis job is scheduled to remove Log entries greater than 30 days.
Expected Results: Job completes within a reasonable amount of time.
Actual Results : Performance get's hogged as the LOG_DETAILS table is too large and each DELETE operation consumes significant amount of Database Time, User I/O.
DE49803: Open Workbench Crashing When Manually Adding Tasks to Project
Steps To Reproduce:
  1. Use a project that has a few tasks. They can all be at the same level.
  2. Open the project in OWB.
  3. Click on one of the middle rows and click Insert (either on OWB or keyboard).
  4. Enter task ID and name.
  5. Click insert again.
  6. Repeat 2 or 3 more times.
Notes:
Sometimes you can insert 2 but after 3 you usually get the error.
You can also just try clicking on insert to insert new lines before you type in task info.
Expected Result: You can insert new lines.
Actual Result: Either get npWBench.exe has stopped working or OWB just closes. Nothing in the logs.
DE51120: Color Coding is missing in the New UX Staffing for 3 row styles unique to the Resource Workspace.
Impacted row styles:
  1. Soft booked rows – Should have Blue Background color.
  2. Inactive rows – Should have Gray Background color.
  3. Locked investments – Should have Text greyed out.
Steps To Reproduce:
  1. Create 3 new projects in Clarity and add the same resource to all 3 projects.
    1. For project2, make the investment inactive (this can be done in Modern UX by clicking on the Details tab in the project and unchecking Active).
    2. For project3, lock the investment (one way to do this is open the project in a scheduler tool such as Open Workbench in read/write and keep it open during the steps).
  2. Navigate to the Staffing section of the Modern UX.
  3. In the Resources to Investments portlet, click on the resource added to the 3 projects above to view the projects beneath the resource.
  4. For project1, click on project1.
  5. In the Detail fly out window that appears, change Booking Status to Soft if not set already.
  6. View the row colors for project1, project2, and project3.
Expected Results: The row for project1 should be blue (since the resource is soft booked), the row for project2 should be gray (since the project is inactive), and the row for project3 should be read only (since the project is locked).
Actual Results: All rows are white color.
DE50849: Reporting link is missing in NSA for a fresh clarity installation
Steps To Reproduce:
  1. Download Clarity 15.7.0.jar and install Clarity.
  2. Navigate to <clarity runtime directory>/bin and start beacon and nsa services.
  3. Login to NSA and click on server name.
Expected Result: Reporting link  is present to provide Jaspersoft details
Actual Result: Reporting link is missing
DE50516: Board is blank or Cards are not visible when individually removing the CARD FIELD that is not the last field from the right
Steps To Reproduce:
  1. Login to Clarity PPM Modern UX.
  2. Click on any board (Project, Idea, Custom Investment, or Task).
  3. Click on view options and goto CARD FIELDS.
  4. Remove first card field.
  5. Nothing will display on board.
Expected Result: Board should always display cards along with the fields mentioned in card fields.
Actual Result: In card fields on removing the first field, nothing will display on board (no columns or cards)
DE50774 : DEFAULT Timeline Monthly Fiscal Period Labels are not showing
Steps To Reproduce:
  1. Go to PROJECT01 > TASKS > Timeline.
  2. The timeline area does not show the default monthly fiscal period labels.
  3. Go to PROJECT02 > TASKS > Timeline.
  4. The timeline area does not show the default monthly fiscal period labels.
  5. In this PROJECT02 change the View Options to 'Quarters', then change to 'Months' and save the view.
  6. This project now has the monthly labels.
  7. Go to PROJECT03 > TASKS > Timeline.
  8. The timeline area does not show the default monthly fiscal period labels.
  9. Go BACK TO PROJECT02 using the saved view - labels show up.
  10. Now delete this saved view so it goes back to the default OOTB view.
Expected Results: To have the default Monthly period labels show on the Timeline.
Actual Results: The labels do not show until the user changes the configuration. 
Files Included In the Patch
  • README.txt
  • install.sh - Unix installer
  • install.bat - Windows installer
  • install.xml - Ant install script
Prerequisites
Install only on systems running the version stated above.
Install the Patch
Follow these steps:
  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. Run the following command to stop all local nsa, app and bg services: service stop nsa app bg
  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. Run the following command to 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.
    4. 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:
    2. admin jaspersoft keystore
    3. Copy the keystore files generated in the path - <install_dir>/config directory to <Jaspersoft Tomcat Instance Directory>/webapps/<jaspersoftContext>/WEB-INF/config
    4. Enter the following command to upgrade the report content:
    5. admin content-jaspersoft csk -userName <superuser> -password <password> upgrade -retryCount 50
    6. Restart all PPM services.
    7. 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:
    2. admin jaspersoft keystore
    3. Copy the keystore files generated in <install_dir>/config directory to <Jaspersoft Tomcat Instance Directory>/webapps/<jaspersoftContext>/WEB-INF/config
    4. 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).
    5. 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
    6. Configure the Data Warehouse section in CSA. See CSA: CA PPM System Administration at docops.ca.com/ppmop.
    7. Enter the following command from the <install_dir>/bin directory command prompt to apply the data warehouse patch content:
      1. admin db dwh-upgrade -Dupgrade.phase=maintenance
      2. Restart all PPM services.
      3. Run the Load Data Warehouse Access Rights job.
Uninstall the Patch
Follow these steps:
  1. Run the following command to 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. Run the following command to start all services: service start all
  4. If you are running multiple servers in a cluster, log in to CSA and go to the All Services page to shut down any remote app and bg services.
  5. Go to the Distribute All page, select remote servers and click Distribute.
  6. Return to the All Services page to restart services when the distribution is complete.
JasperReports Server 7.1.3 for Clarity
Jaspersoft Server 7.1.3 version includes critical security fixes and it is highly advisable to upgrade to 7.1.3 version. In addition, falling too far behind can increase your risk exposure and compound maintenance time and cost. To learn more about the security vulnerabilities which were fixed in Jaspersoft 7.1.3 version, refer to the security advisories issued by Tibco.
Issues Fixed in JasperReports Server 7.1.3_6.3.0.1 for Clarity SaaS
DE57233 - Spinning Issue When a New Join Condition is Added to an Existing Domain in the Domain Designer
Steps to reproduce:
  1. Login to
    Clarity PPM
    and click
    Advanced Reporting
    .
  2. Navigate to
    Domains
    and edit any domain (Ex: Project Management domain).
  3. Click
    Edit Domain with Domain Designer
    .
  4. Click the
    Tables
    tab and add a new table to the selection list.
  5. Click the
    Joins
    tab and create a join with the new table you added.
  6. Click the
    OK
    button.
Expected Result: The page reloads successfully and a new join is created.
Actual Result: The Page does not reload and the Javascript error is displayed.
DE57234 and DE57235 - Unable to See Tables in Domain Designer
Steps to reproduce:
  1. Login to
    Clarity PPM
    and click
    Advanced Reporting
    .
  2. Navigate to Domains and edit any domain (Ex: Project Management domain).
  3. Click
    Edit Domain with Domain Designer
    .
  4. Click the
    Tables
    tab.
Expected Result: You can see a list of tables and select the relevant table.
Actual Result: You see the
List of Invalid Reference
error.
DE57236 - Added Support for New Fixed Date Format "dd MMM YYYY" as Additional Adhoc Mask Date Format
You can now see the date value as "13 May 2020" for 05/13/2020.
Issues Fixed in JasperReports Server 7.1.3_6.3.0.1 for Clarity On-Premise
DE57233 and DE57236 have been addressed for
On-Premise customers. The details associated with these defects can be found in the Issues Fixed in JasperReports Server 7.1.3_6.3.0.1 for the Clarity SaaS section.
Install the Patch
  1. Stop the application server (Apache Tomcat Server), on which Jaspersoft is deployed.
  2. Find the root web application folder (e.g. Windows - c:\\apache-tomcat\\webapps\\reportservice and Linux - /fs0/apache-tomcat/webapps/reportservice).
  3. Create a back-up of that folder to a new, separate location.
  4. Extract the Jaspersoft Patch zip file to the relevant location.
  5. Navigate to the "patch directory"/bin folder. The bin folder contains installer scripts, that you need to run on the OS command prompt.
  6. For interactive installation, enter install.bat/install.sh based on your operating system.
  7. Run command 'install.bat/install.sh' command. Ensure the property values in 'install.properties' file has relevant values.
    • patch.deploy.tomcat: The absolute path of the Tomcat Server base folder.
    • patch.deploy.jrs.webapp.name: Enter the webapp name of Jaspersoft.
    • patch.deploy.capb.name: The value should always be "clarity".
    • patch.install.mode: The value can be 'standalone' or 'cluster' based on the node you install the patch.
  8. Clear the application server (Apache Tomcat Server) 'temp' directory.
  9. Clear the application server (Apache Tomcat Server) 'work' directory.
  10. Start the Apache Tomcat Server, on which Jaspersoft is deployed.
  11. Clear browser cache on the client.
Uninstall the Patch
  1. Stop the application server (Apache Tomcat Server), on which Jaspersoft is deployed.
  2. Find the root web application folder.
  3. Restore all the files under /reportservice from backup.
  4. Restart the Tomcat instance.