Clarity PPM
and Jaspersoft Cumulative Patch README Files

ccppmop1571
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.
2
Clarity PPM
Cumulative Patch Summary
As patches are cumulative in nature, when you install a single patch, it includes all the fixes in all previous patches, keeping you up-to-date. The following table lists the patches released so far:
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
15.7.1
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
15.7.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
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.1.4
DE51165 - PRJ-07008 Error occurs when editing Assignments in the Classic and Modern UX
Steps to reproduce:
  1. Create a project with a single date of AUG 12 2019.
  2. Configure the Financial properties and set Financial Status = Open.
  3. Do not staff any resources.
  4. Create a task for example, Task1 with the same date as the project AUG 12 2019. 
  5. Do not assign any resources.
  6. Go to Classic, Home, Financial Management: Transaction Entry.
  7. Create one transaction on this project for this task and this date for a financially enabled resource as follows:
    • Resource1 - Transaction date = AUG 12 2019 (Task1)
    • Post To WIP and execute the 'Import Financial Actuals' job.
  8. Verify that the data is posted back to the project and assignment of Resource1 can be updated (update the Role or the Loading Pattern).
  9. Go to Classic, Home, Financial Management: Transaction Entry.
  10. Create two new transactions on this project for this same task using a different financially enabled resource as follows:
    • Resource2 - Transaction date = AUG 12 2019 (Task1)
    • Resource2 - Transaction date = AUG 14 2019 (Task1)
  11. Post To WIP and Execute the Import Financial Actuals job. 
  12. Verify that the data is posted back to the project.
  13. Now try to change the assignment of Resource2' for the Loading Pattern or the Role field.
  14. Try in Classic or Modern UX - the issue is reproduced in both the places.
Expected Results: The changes made to the assignment are saved successfully.
Actual Results: The changes are not saved and the following error is thrown: 'PRJ-07008: Finish date earlier than start date.
DE50348 - Synchronize Agile Central job is failing with 524 Time-out error
  1. Log in to Clarity.
    1. Configure Agile Central to Clarity integration. 
    2. Create a project and enable Agile Central integration.
  2. Log in to Rally.
    1. Create more than 2000 resources. 
    2. Create different user stories and tasks and assign different owners (created from step 2a).
  3. In Clarity, run the Synchronize Agile Central job.
Expected Results: Project and tasks are synchronized and the Synchronize Agile Central job is executed successfully.
Actual Results: For some projects, the job fails with the following error in logs:
java.io.IOException: HTTP/1.1 524 Origin Time-out
For those projects, the Synchronized checkbox gets cleared as there are exceptions processing the request.
DE54888: New UX - Filtering on Project Grid reverts back to original results
Steps to Reproduce:
  1. Connect to a large customer dataset
  2. Go to Projects - Grid.
  3. Note the number of projects there.
  4. Now quickly add a filter for example, Active = Yes.
  5. Note the amount of projects changing down.
  6. Within five seconds, note the amount of projects reverting to the initial number.
Expected Results: The filter results to stay as they are.
Actual Results: Results are reverted back to the original filter
Workaround: None
DE49460 - Export to CSV Per-Period Metrics are blank if 'Totals' column is not present
Steps to Reproduce:
These steps are for the Project STAFF Grid - repeat the same steps for ASSIGNMENTS grid using any of the metric fields (ETC, ETC Cost, Actuals, Actual Cost).
  1. Go to Project STAFF grid.
  2. Open Column Panel and add Totals - Allocations field.
  3. Go to View Options and select the following options:
    •    PER PERIOD METRIC = Allocations
    •    PERIOD TYPE = any configured type - use Month
    • START / END Dates - use dates that fall within the project.
  4. If the user uses FTE - set the decimal display option or change the user's SETTINGS GENERAL to use Hours.
  5. Click EXPORT TO CSV.
  6. Look at the output - the data is shown as expected for the PER-PERIOD METRICS columns.
  7. Remove the Totals column.
  8. EXPORT TO CSV.
Expected Results: To see data in the PER-PERIOD METRICS columns in the CSV output.
Actual Results: the PER-PERIOD cells are blank in the CSV output.
Workaround: Add the Totals column to the grid layout before using Export to CSV.
DE54579 - 'User Value 2' attribute in Timesheet Return page not displaying full lookup value characters in Modern UX
Steps to Reproduce:
  1. Populate the out of the box static lookup 'Time Entry User Lookup field 2' with a value like the following examples:
    • Hours Increased - Incorrect Posted to a project
    • Hours Decreased - Booked to wrong project
    • Hours Increased - PM Change
  2. In Classic, Navigate to Timesheet Options page and under the Default Content and Layout section move the attribute User Value 2 from Available Columns to Selected Columns so that it is the attribute listed at the bottom.
  3. Navigate to the Modern UX Timesheet page and Submit and Approve the timesheet and then Return the Timesheet.
  4. On the Timesheet Return page you find that the User Value 2 attribute is listed as the last column on the page.
  5. Now click on the User Value 2 lookup value selection area to list values in the lookup.
Expected Results: All the values that are entered in the lookup in the Step 1 display fully.
Actual Results: Lookup Values with characters longer than 26 are cut off and do not display the full value.
Workaround: Move the User Value 2 attribute two columns to the left on the Timesheet Return page so it is not in the last column.
Issues Fixed in 15.7.1.3
DE53998 - Help link does not work in non-English locale
Steps to Reproduce:
  1. Log in to
    Clarity PPM
    .
  2. Click Help - The documentation works as expected.
  3. Go to Home, Account Settings.
  4. Change Language to Spanish.
  5. Save.
  6. Click Help.
Expected Results: The expected behavior is that the help link opens the following supported languages pages:
  • French
  • German
  • Spanish
  • Brazilian Portuguese
  • Italian
  • Japanese
If it is in a language we do not support for localization it should default to English. Actual Results: No pop up comes up as the HID and language doesn't match.
DE54159: Unable to Import Roadmap with Custom Investments using OBS on Oracle and Postgres SQL
Steps to Reproduce:
  1. Log in to
    Clarity PPM
    .
  2. Create a Roadmap.
  3. Go to Import Roadmap from PPM and select a Custom Investment.
  4. In Custom investment import window, select an OBS and click Import.
Expected result: All associated custom investments should be imported as roadmap itemsActual result: No custom investments are imported as roadmap items.
DE53148: Unable to deploy pm.war on a second (cloned) app server, leading to intermittent HTTP 404 on Modern UX when hitting it (New UX is not deployed for Clone services of APP service)
Steps to Reproduce:
  1. Connect to
    Clarity PPM
    15.7.1 and make sure the following is set for app: <war context="pm" name="ppm-ux" enable="true"/> is set in the properties.xml
  2. Run the command service clone app.
  3. Service deploy start app2.
  4. Now go to $clarity\tomcat-app2-deploy\webapps
Expected Results: pm.war to be present deployed there as in $clarity\tomcat-app-deploy\webapps Actual Results: The pm.war file is not in $clarity\tomcat-app-deploy\webapps
DE52789: When refreshing the page while at a Channel tab, you get redirected to the first tab on the layout
Steps to Reproduce:
  1. Log in to
    Clarity PPM
    .
  2. Go to Admin, Blueprints.
  3. Create a project type blueprint or use an existing, user-defined one.
  4. Go to Modules and add a channel as the last tab.
  5. Go to a project and associate it to the new blueprint created.
  6. Edit the project.
  7. Go to the STATUS tab.
  8. Refresh the page.
  9. After the refresh, you remain on the same tab.
  10. Go to the Channel tab.
  11. Refresh the page.
Expected Results: To remain on the same Channel tab. Actual Results: You get redirected to the first tab on the layout. ADDITIONAL INFO: If you take the Channel tab URL and paste it on the browser, you also get redirected to the first tab on the layout.
DE53944: Connection leak issue in Advanced Resource Planning (AE-3262), ITD plugin defect.
Steps to Reproduce:
  1. Note the number of active connections by using the following command: clarity_host/niku/apache?alias=clarity&level=more&pool=more
  2. Go to Advanced Resource Planning, and start the Test process from there, by using the context menu item (ex. Test process). Do this a couple of times.
  3. Check again the number of active connections. It will increase with each process started and remain high because the connections created during the process start are not being closed.
Expected Results: The number of active connection should be closed. Actual Results: Check again the number of active connections. It will increase with each process started and remain high because the connections created during the process start are not being closed.
DE54205/DE52579 - The number of columns available on the Projects Grid Filter Selection/column picker is limited to 500
Steps to Reproduce:
  1. Login to
    Clarity PPM
    .
  2. Navigate to Administration, Studio, Objects.
  3. On Project Object create custom attributes and enable them for API usage.
  4. Create attributes until the count reaches more than 500.
  5. Navigate to Modern UX, Projects Grid
  6. Click on the Filter Cone Icon and select Add Filter.
  7. And verify the columns panel by click on "List Columns" on the right-hand corner of the screen
Expected Results: We should be able to see all the API Enabled attributes for selection.Actual Results: Only 500 API Enabled attributes are displayed and others are cut off.
DE54038: REST API calls using Bearer Tokens do not release DB Connections after serving request
Steps to Reproduce:
  1. Go into the Modern UX -> Administration -> API Keys -> Clients. Define a client that can be used
  2. Go into "API Keys" from the top right corner of any page in Modern UX and create an API Key
  3. Restart the app service and make note of the connections open using the following URL. Do not let any other user login to the application
  4. http://HOST_NAME/niku/apache?alias=clarity&level=less&pool=less
  5. Use the API Key generated in Step 2 along with Client defined in Step 1 as headers, to make a GET Call of the format shown below:
  6. http://HOST_NAME/ppm/rest/v1/projects?limit=5&offset=0&sort=_internalId
  7. Make note of the total ACTIVE connections using the same URL as in Step 3 
  8. Repeat Step 4
  9. Make note of the total ACTIVE connections using the same URL as in Step 3
  10. Restart the app service again
  11. Now, instead of the Bearer Token, use Basic Authentication to make the GET call from Step 4
  12. Make note of the total ACTIVE connections using the same URL as in Step 3
  13. Repeat Step 7
  14. Make note of the total ACTIVE connections using the same URL as in Step 3 
Expected Result: Count of ACTIVE connections does not increase in Steps 5, 7, 8, 10. Actual Result: Count of ACTIVE connections increases in Steps 5 and 7. They do not increase in Steps 8 and 10.
DE52095: Modern UX Risk / Issues Warning when updating resource fields: 'One or more parameters ‘param_is_active’ are not API enabled'
Steps to reproduce:
  1. Use the Standard Project Blueprint or a user-defined Project Blueprint that has the RISKS module in the Modern UX
  2. Create a project and associate it with the blueprint with the RISKS Module as noted in step 1
  3. Click on the RISKS module for the project
  4. Add 'Assigned to' to the grid column list if not there already
  5. Click the + icon to create a new risk
  6. Double click on the 'Assigned To' field for the risk and select a resource
Expected Results: The resource is assigned successfully and no error is displayed. Actual Results: The resource is assigned, but a warning is displayed “One or more parameters ‘param_is_active’ are not API enabled.  You may see unexpected results.".
DE51506 - Securability Defect.
DE53552 - Securability Defect
Issues Fixed in 15.7.1.2
Infinite Scroll for OBS:
Infinite scroll support is now available when using an OBS to import Projects, Ideas or Custom Investment to a roadmap.
DE53709
:
Modern UX: CMN-0009 error returned when updating an MVL field if a value selected is inactive
Steps to Reproduce:
  1. Navigate to Studio, project object.
  2. Create a Multi Value Lookup (MVL) type attribute based on the OOTB LOOKUP_USER_ACTIVE_SEC lookup.
  3. Provide an API Attribute ID to make it available in the New User Experience.
  4. Add the field to the project list view.
  5. Navigate to the Classic UI, Project list.
  6. Add some users to the field and save changes in a given project.
  7. Navigate to Admin, Resources.
  8. Select one of the users that we added to the MVL field and inactivate it.
  9. Navigate back to the project list and look at the MVL field and the selected values.
  10. The inactivated value is displayed.
  11. Add some further values and save. The changes are saved.
  12. Log in to the New User Experience project list.
  13. Add the MVL field to the list.
  14. On the list, you can see all the pre-selected values. Also the users who were inactivated.
  15. Edit the field. While editing, you will only see the active values.
  16. Try to add some extra values to the field.
Expected Results: The extra values added to the field are saved.Actual Results: Errror CMN-0009: Attribute 'MyMVL' has invalid Lookup Value '[5003289, 5003130, 5003267]'
DE53240:
Timeslicing Job is not working in non-prod environment
Steps to Reproduce:
  1. Pause the Time Slice job.
  2. Submit a Timesheet for a labor resource.
  3. Execute a Select statement on Prtimeentry table and filter by the Timesheet id of the Timesheet submitted.
  4. Customer has large PRID values in the Prtimeentry table (eg: 3921547957).
  5. For reproduction purposes, update the PRID value in Prtimeentry table to 3921547957 via SQL Update statement.
  6. Run the Time Slice job to post data into PRJ_BLB_SLICES table.
  7. Execute Select query on PRJ_BLB_SLICES table (eg - select * from prj_blb_slices where slice_request_id = 55555 order by created_date desc).
Expected Results: PRJ_OBJECT_ID column in PRJ_BLB_SLICES table to contain the same value as PRID value in PRTIMEENTRY table.Actual Results: A random negative number gets generated in the PRJ_OBJECT_ID column in PRJ_BLB_SLICES (eg: -373419339).
DE48284:
Incident Actuals are not posted to an investment if resource is not already on the team
Steps to Reproduce:
  1. Log in as an administrator with access to log timesheets for Resource1.
  2. Set up an Incident Category and associate some investments.
  3. Set up a resource that will be used for logging actuals on the incident.
    • Resource1 - open for time entry
    • Resource1 - granted access rights to Incidents
    • Resource1 - DO NOT allocate to the investments
  4. Create a new Incident - select the appropriate Category and Investment.
  5. Assign Resource1 to the Incident.
  6. Create a timesheet for Resource1 and add the Incident with some time.
  7. Submit, Approve and Post the Timesheet.
  8. Ensure 'time slicing' and 'investment allocation' jobs run to update the investment.
  9. Navigate to the Investment, Team Tab ( add 'Incident Actuals' field to see if the data is there).
Expected Results: To see that Resource1 has been automatically added to the Team for this investment and the Incident Actuals amount shows up.Actual Results: Resource1 is not automatically added to the investment and the Incident Actuals do not show up.Adding the Resource AFTER posting the incident actuals does not automatically show the Incident Actuals.
DE52066:
OWB Crashing with error npWBench.exe has stopped working
USE CASE #1
Steps to Reproduce when closing a project in OWB:
  1. Open OWB and click the New icon to create a new project.
  2. Create two tasks.
  3. Add a resource to the project in OWB.
  4. Assign the resource to one task.
  5. Save the project locally.
  6. Click the x right next to the project name in OWB to attempt to close the project (not the x in the upper right-hand corner that closes OWB completely).
Expected Results:  Save is successful and OWB remains open.Actual Results: OWB crashes with error npWBench.exe has stopped working. (Clicking the Close Program message in the error popup up window closes OWB).Workaround: Close OWB completely by clicking the x in the right-hand corner (However, OWB will close all open projects versus just the one project).
USE CASE #2
Steps to Reproduce when creating a new task or using filters:
  1. Open OWB and create a new project.
  2. Create three tasks: Make the first task a Phase, the second task an Activity, and the third task a regular task.
  3. Add a resource to the project in OWB.
  4. Assign the resource to the child task (the third task).
  5. In the Task menu options, select the resource from step 3 from the drop-down, and change the Type from Task to Phase.
  6. Attempt to create a new task.
Expected Results: Task is created successfully.Actual Results: OWB crashes with error npWBench.exe has stopped working. (Clicking the Close Program message in the error popup up window closes OWB).Workaround: None, aside from avoiding the use of filtering
DE52734:
Users with Instance Resource Booking rights cannot staff Custom Investments in Modern UX STAFF Module.
Steps to Reproduce:
  1. Create Users with the following Instance rights:      
  • User1 - Instance [Custom Investment] View + Instance Resource Hard Book
  • User2 - Instance [Custom Investment] Edit + Instance Resource Soft Book & Resource Hard Book
2. Log in as the specified users, navigate to an Idea or Custom Investment in the New User Experience, STAFF Tab.Expected Results: The '+' button appears. Actual Results: No '+' button, Users are unable to add resources to Staff.
DE52677:
Modern UX Timesheets performance on Review and Approve for large datasets
Steps to Reproduce:
  1. Using Chrome or Edge, on a large dataset pick a user with many resources reporting to them as manager.
  2. Navigate to the New User Experience - Timesheets - Review and Approve.
  3. Perform the following steps as a resource manager:
    1. Click on the Filter, select Resource, and double click on the drop-down to see all results.
    2. Click on the Filter, select Resource, and type few letters in the drop-down.
    3. Click Open to see Open Timesheets. 
    4. Click Submitted to see Submitted Timesheets. 
    5. Click Approved.
    6. Click Returned.
Expected Results: All actions to perform within normal limits (ideally under 5, acceptable under 10 sec)Actual Results: All the actions are over 20 sec.
DE52941:
Parent Keys Not found Error while DWH Incremental Load is running and Transaction Adjustments are made (Oracle, PostgreSQL)
Steps to Reproduce:
  1. Log in to
    Clarity PPM
    .
  2. Run a full data warehouse load.
  3. Add some financial transactions through Transaction Entry (Do not post).
  4. Run an incremental data warehouse load.
  5. While the DWH load is running, once it processes dwh_fin_transaction but does not get to the facts yet, run the Post to WIP in
    Clarity PPM
    .
Expected result: The transactions should not show up in the DWH but the jobs completes successfully.  The transactions will show up on the next DWH load.Actual Result: The datawarehouse load aborts with a 'Parent Keys not found' error.
DE52688:
Page through Assignments Sub-Tab with more than 25 Assignees on Task Flyout does not work properly
Steps to Reproduce:1. Navigate to the TASKS grid of a project or custom investment in the New User Experience.2. Click on a task row and open the Task DETAILS Fly-out.3. Navigate to the Assignments Sub-Tab in the Fly-out.4. Assign more than 25 Labor resources or Roles on this task (a second page for assignments will then be created).5. Using the navigational arrows (click on the right arrow) on this sub-tab, navigate to the second page. Try to navigate back to the first page by using the arrow on the left.Expected Results: To be able to find and use the navigational arrows without any problems.Actual Results: The arrow disappears when you want to click on it making it impossible to navigate back to the first page of the task assignments.
DE53152:
Timesheet 'Notify' button sent out email to ALL resources
Steps to Reproduce:
  1. Create a Resource of Expense type through Home, Resources.
  2. Under Settings for that resource select 'Open for Time Entry' and track mode as 'PPM'.
  3. Navigate to Timesheets in Classic and filter for Open Timesheets for 'expense' resource created in Step 1.
  4. Click on the checkmark for that resource and click Notify.
  5. Any resource with Timesheets - Edit All (Global) access right will receive an email notification
Expected Results: Notification should not be sent for an Expense type of resource.Actual Results: Notification is being sent to all users in the system with email notification enabled and having Timesheets - Edit All global access.
DE53314: XOG WSDL access through the application or Soap for Objects is resulting in Internal Server Error.
Steps to Reproduce:
  1. Log in to
    Clarity PPM
    .
  2. Replace /niku/nu with /niku/xog in the URL.
  3. Click Objects.
Expected Results: XOG WSDL Objects list is shown.Actual Results: 'Internal Server Error' is thrown.
DE52238 - Job to handle Duplicate timesheets when creating timesheets from New UX (on copying previous weeks).
Steps to Reproduce:
  1. The user submits a timesheet in the Modern UX by Clicking 'Create Timesheet' on copying previous weeks.
  2. The user gets a toaster message error notification on top of the screen.
  3. The user manually adds the work to the timesheet and there is no apparent issue.
Expected Result: A duplicate timesheet record should not be created in the database.Actual Results: A duplicate Open timesheet is created in the database.
DE50104:Cost Plan grouping attribute sequence change in the Database when you make the cost plan the plan of record.
Steps to Reproduce:
  1. Create an entity with 4 grouping attributes in the following order:Charge Code (renamed GL Account in a copy of customer environment) (SEQ 0 in DB for default cost plan)Department (SEQ 1 in DB)Role (SEQ 2 in DB)Transactions Class (Renamed Cost Center in a copy of a customer environment) (SEQ 3 in DB).
  2. Run the following query in the DB to verify the sequence IDs match as defined above:    Select * from odf_multi_valued_lookups where object like '%defa%'
  3. In a Classic PPM project, create a cost plan (by default it is set at the plan of record, changing the sequencing to make it different than default set in an entity):
    • Click on the Financial Plans tab for the project.
    • Click New Manual Plan.
    • Enter a name for the plan.
    • Clear out all the group attributes and then add all of the defaults from Step 1 in a different order then above and click Save.
  4. Observe the sequences in the DB for the cost plan.
  5. Run the following query using the IDs from the financial plan created above to get the ID needed for the next query:
    • Select * from fin_plans where object_ID=5032473 and code= 'FINPLAN538329'.
    • Run  the following query with the ID value taken from the above query: Select * from odf_multi_valued_lookups where pk_ID=7625007
    • Note the sequence IDs are in the correct order based on the sequence they were added.
  6. Create a second cost plan with the default order of grouping attributes (don't make any changes), save.
Important!
Make it the Plan of record (Prior to making the cost plan the plan of record, the sequencing shows correctly in the DB)    Select * from odf_multi_valued_lookups where pk_ID=7625008Expected Results: Sequencing matches that of what is set in step 1.Actual Results: Sequencing does not match what is set in step 1.
DE52925: Refresh button missing in Phoenix UI when opening project in PPM Gantt
Steps to Reproduce:1. Log in to Clarity, navigate to Admin and change the UI Theme to Phoenix UI.2. Navigate to Home, Projects and open any project.3. Under Open in Scheduler choose PPM Gantt.4. Observe the error "Unable to initialize embedded module for Gantt. Use the Refresh icon to complete the module initialization.", but the Refresh option is missing.Expected Results: User should be able to click on Refresh icon.Actual Results: Refresh icon is missing.
DE51762 - Unable to secure Classic Sub-Object Sub-page views of Custom Master Objects. No 'Secure' option is present on those subobjects
Steps to Reproduce:1. Create a new master object: Mymaster.2. Create a subobject for the master object above: MyMasterSub.3. Navigate to the Views tab, General Layout: Edit.4. Open the properties of the Subpage.Expected Results: There should be a field called 'Secure' below the 'Linkable' field. To be able to secure the subobject subpages.Actual results:  There is no field called 'Secure', so the sub-object sub-pages cannot be secured.
DE53192: Modern UX does not open with IE in Clarity 15.7.1, there is a blank page
Steps to Reproduce:1. Install or Upgrade Clarity 15.7.1.2. Open IE11 and connect to the New User Experience.Expected Results: To be able to login to the New User Experience although all functionality is not supported using the IE11 browser.Actual Results: Blank page. No Login page.
DE52398: Modern UX: Populating Field Shows Blank Until Page is Refreshed
Steps to Reproduce:
  1. Create a static lookup in Classic UI.
  2. Create a Multi-Select Lookup attribute on a Project object using lookup created in step one.
  3. Add the lookup attribute created in step two to the Project Summary page in the Project properties view of the Project object.
  4. Create a Project instance in Classic and associate it with a Blueprint. (ensure lookup attribute is on Project Summary page)
  5. Add the lookup attribute to the Blueprint associated with the project in step four above.
  6. In New User Experience, click to open the project and on the 'Details' tab to display Project Summary page.
  7. Select multiple values from the multi-value lookup and click away.
Expected result: Selected values should be displayed in the lookup.Actual Result: The lookup is displayed as empty just like no values were selected.
DE53768: After refresh, Load Data Warehouse fails: table does not exist due to old entries with schema name hardcoded in table DWH_INTERNAL_MD
Steps to Reproduce:
  1. Take a database backup from an environment whilst the Load Data Warehouse is still running and there are entries in DWH_INTERNAL_MD in PPM_DWH schema.
  2. Restore the backup to another environment (both Clarity and Data Warehouse).
  3. Check the table DWH_INTERNAL_MD, note the entries are there.
  4. Now run Load Data Warehouse job - Full Load.
Expected result: The Load Data Warehouse job to complete successfully and creates the indexes that were in dwh_internal_md.Actual Result: The Load Data Warehouse job fails with error [CA Clarity][Oracle JDBC Driver][Oracle]ORA-00942: table or view does not exist.
DE51892 - Securability Defect
DE52626 - Securability Defect
DE52625 - Securability Defect
Issues Fixed in 15.7.1.1
DE51763: Unable to save role demand data on portfolio plans.
Steps to Reproduce:
  1. Create an Investment Sub-object.
  2. Create a time-varying attribute and ensure that the time-varying type is 'Fiscal.'
  3. Navigate to the Investment object and verify the following three attributes:
    • Fiscal Period End Date
    • Fiscal Period Start Date
    • Fiscal Period Type
  4. Navigate to time slices in Data Administration and create one TSV attribute and link that to the current baseline team cost.
  5. Navigate to Portfolio Investment, and click on Attribute Registry, and move the above mentioned Fiscal Attributes from Available to Selected List.
  6. Navigate to Portfolios and create a new portfolio.
  7. Import one investment of type project with a few roles in the project. Also, ensure the Role Demand does populate.
  8. Create a new plan for this portfolio and ensure that the newly created plan is selected.
  9. Click the imported investment and navigate to Role Demand portlet and try to change the value in the TSV.
  10. The data is saved.
  11. Clear the cache by navigating to the system. Caches action.
  12. Navigate to the newly created portfolio and click the imported investment and change the value in the TSV.
  13. The save fails with an error: "PFM_CA_INV.odf_period_start" could not be bound.
Expected Result: The role demand portlet is saved.Actual Result: Encounter a system error.
DE49036: Negative number is generated by sequence in the PRTIMEENTRY table for 'PRID' column, as a result breaking the time entry module in Clarity PPM New User Experience.
Steps to Reproduce:
  1. Use a dataset with several timesheets.
  2. Open the PRTIMEENTRY table and note the value of PRID.
  3. Open any of the timesheets with negative PRID in Clarity PPM New User Experience.
Expected Result: The value of PRID column in PRTIMEENTRY table must be positive. Actual Result: The value of PRID column in PRTIMEENTRY table is negative. For example, -35044054.
DE50808: MSP Scheduler deletes rows from 'nbi_proj_res_rates_and_costs' table
Steps to Reproduce:
  1. Ensure the 'On-the-fly Rate Matrix' option is enabled.
  2. Create a project with two labor resources allocated to the team and assigned to a single task (not the effort task).
  3. Verify the rate matrix table 'NBI_PROJ_RES_RATES_AND_COSTS' for data.
  4. There are four rows of data (each resource having an entry for the specific task that they are assigned and an entry for the team rate with the task_id = -1) 4.
  5. Open the Project in Microsoft Project (MSP).
  6. Verify the rate matrix table 'NBI_PROJ_RES_RATES_AND_COSTS' for data.
Expected Result: The specific task assignment rows should remain in the table. Actual Result: The specific task assignment rows are deleted, and only the 'team rate' (task_id = -1) rows remain in the table.
DE51973: TSV values are automatically multiplied by 8 when the work effort is set to 'Days.'
Steps to Reproduce:
  1. From the Classic PPM, navigate to Administration, Project Management, Settings, General, and configure 'Default Display Unit for Work Effort' as 'Days.'
  2. Navigate to Clarity PPM New User Experience.
  3. Display the ASSIGNMENTS module for projects by configuring it through Blueprints.
  4. Create a Project and add a labor team member.
  5. Create a task for 1 month and assign a staff member.
  6. Navigate to ASSIGNMENTS tab, and display the following:
    1. ETC as a TSV
    2. View Options: PER-PERIOD METRICS = ETC
    3. PERIODS = Months
  7. From the Avatar, click SETTINGS and GENERAL.
  8. Set UNIT OF MEASURE = FTE
  9. Provide "1" as the input for one of the monthly periods. The value updates to 8 (1*8).
  10. From the Avatar, click SETTINGS and GENERAL.
  11. Set UNIT OF MEASURE = Hours. The value updates to 1344, which is 8 (working hours) * 21 (working days) * 8 (additional number) 10.
  12. Change the value in this one period to 8. The value changes to 64 (8*8).
Expected Result: The value entered as an FTE Unit should remain as an FTE Unit, and the value entered as HOURS unit should remain as Hours unit of measure. The Clarity PPM New User Experience currently does not support DAYS. It should not be using the Classic Administration Project Management setting to affect the display for work effort unit fields. Actual Result: Entries are automatically multiplied by 8.
DE51947 - Filtering on the Projects Grid is not consistent.
Steps to Reproduce:
  1. Log in to Clarity PPM New User Experience.
  2. Navigate to the Projects or Idea grid view.
  3. Click Add Filter.
  4. On the Search Drop Down, select ID to filter the Projects by its ID.
  5. Enter any ID.
  6. Try adding additional filters apart from ID.
Expected Result: The application should show the data that matches the records from the last filter applied. Actual Result: The application does not show the data that matches the last applied filter.
DE52133: When an existing string attribute is updated, there are duplicate entries while switching between details fly-out.
Steps to Reproduce:
  1. Log in to Clarity New User Experience.
  2. Navigate to Project, Issues module, and Grid layout.
  3. Create two issues Test1 & Test2.
  4. Click Test1 and open the details fly-out.
  5. Click Configure and add the resolution field.
  6. Click Exit.
  7. Click Test1 and open the details fly-out.
  8. Edit the resolution field and add value as 'XYZ'.
  9. Click Test2 in the Grid.
Expected Result: The row for Test1 is updated with the correct value. Actual Result: Other rows are updated with incorrect values.
DE51842: The screen is greyed out after you allow pop-up blockers more than 8 times on a system that has the Phoenix theme applied.
Steps to Reproduce:
  1. Log in to Classic PPM as an administrator.
  2. Verify that 'Phoenix' is the UI theme.
  3. Navigate to Home and Projects.
  4. Open an existing project.
  5. Click the browse icon for any of the lookup attributes.
  6. Close the pop-up that appears.
  7. Repeat the above two steps for 7-8 more times.
Expected result: The pop-up must appear the 8th time as well. Actual Result: The pop-up opens and the entire screen is stuck or greyed out the 8th time.
DE52594 - Cumulation updates to improve PostgreSQL performance
Steps To Reproduce: NA Changes Included:
  1. Modified several databases functions to change the parameter signatures, to better match indexes used in the function, when executing queries. Changed the parameters passed as numeric to integer or bigint, to ensure indexes defined to the tables are used while improving the fetch times.
  2. Added additional joins to improve the performance of portlet instance queries.
  3. Modified the instance rights checking process to check the global rights first, when running the jobs that perform process instance clean up. These jobs are usually run by administration users and uses in-memory rights checking, as opposed to database functions, to perform more expensive rights checking.
  4. Modified the temporary tables for PPM Gantt page to use integer or bigint columns, instead of numeric. This action avoids any unnecessary casting by the PostgreSQL engine when inserting data into the tables.
  5. Changed the timesheet lookups for Submitted By, Approved By, Modified By, to avoid joins with CMN_CAPTIONS_NLS.
  6. Added additional indexes to the BPM_RUN_OBJECTS table, to improve access time.
  7. Modified REST API calls with the tsvParams parameter to fetch additional attributes required by tsvParams processing in the main query. This modification avoids extra database calls to retrieve the attributes.
  8. Created a new XOG endpoint to validate all the NSQL queries in the system through a XOG export call. This endpoint is used post-migration of Oracle to PostgreSQL, to validate if all the NSQL queries in Clarity are compatible with PostgreSQL.
  9. Used dynamic SQL in functions to ensure execution plans are created to run the queries inside the function.
  10. Refactored the Timeslice rollover stored procedures to enhance the performance on PostgreSQL.
  11. Changed the Numeric datatype to bigint for PostgreSQL in scenarios where the data value had just scale and no precision.
  12. Schema changes: Changes to the following database objects for performance improvements:
    • CMN_SEC_CHK_CLS_INST_RIGHT_FCT
    • CMN_SEC_CHK_CLS_RIGHT_FCT
    • CMN_SEC_CHK_INST_FCT
    • CMN_SEC_CHK_USER_FCT
    • CMN_SEC_USER_INST_PRIVS_FCT
    • OBS_UNIT_FULL_PATH
    • ODF_BLB_SLICE_RESET_ALL_SP
    • PRJ_BLB_ROLL_ASSIGN_ACTCOST_SP
    • PRJ_BLB_ROLL_ASSIGN_ETCCOST_SP
    • PRJ_BLB_ROLLOVER_ASSIGNMENT_SP
    • PRJ_BLB_ROLLOVER_TEAM_HARD_SP
    • PRJ_BLB_ROLLOVER_TEAM_SP
    • PRJ_BLB_ROLLOVER_TIMEENTRY_SP
    • PRJ_BLB_SLICE_RESET_ALL_SP
    • BPM_RUN_OBJECTS
    • LOOKUP_RESOURCES_NAME_ONLY - New Lookup for timesheets
  13. Reporting changes: None
  14. XOG API changes:  New read endpoint: nsqlValidate. Used to validate NSQL queries.
Example:
<?xml version="1.0" encoding="UTF-8"?><NikuDataBus xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="../xsd/nikuxog_read.xsd"> <Header version="15.7" action="read" objectType="nsqlValidate" externalSource="NIKU"> </Header></NikuDataBus>
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 PPM 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.
Files Included In the Patch
  • README.txt
  • install.sh - Unix installer
  • install.bat - Windows installer
  • install.xml - Ant install script
Prerequisites
Ensure that you install this patch only on systems that are running the versions that are stated above.
Install the Patch
Follow these steps:
  1. Backup 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. Navigate 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:
      admin jaspersoft keystore
    2. Copy the keystore files generated in the following path: - <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: CA 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.
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.