Clarity
and Jaspersoft Cumulative Patch README Files

ccppmop1581
HID_clarity_readme
Cumulative patches for
Clarity
and Jaspersoft for
Clarity
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
on this page because they behave like patches for existing
Clarity
customers with Advanced Reporting environments.
  • 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:
2
Clarity PPM has now been 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. Clarity refers to the New User Experience, and Classic PPM refers to the Classic PPM Studio.
Issues Fixed in 15.8.1.6
DE60481: Error 401 User Not Registered Error in Advanced Reporting
Steps to Reproduce
  1. Login to Clarity as an administrator.
  2. Navigate to Advanced Reporting, create an Adhoc report, and save it under a folder (it can be OOTB or customer).
  3. Create a new user and add the following group and rights.
    1. Groups - Basic: A group for user access
    2. Rights: Advanced Reporting – Navigate and Advanced Reporting - Report Create
  4. Run the Create and Update Jaspersoft User job.
  5. Log into Clarity with the newly created user and navigate to Advanced Reporting.
  6. Go to the folder where the Adhoc report is stored and click the Adhoc view.
  7. The user will get an error page with the text - 'Please contact your system administrator or log in as a user with permission.'
  8. If the user clicks the highlighted section, they get directed to http://clarity/reportservice/exituser.html and this page when you call from Jaspersoft it triggers a logout. However, in Clarity, we are not logging out the user since it's embedded. The user is directed to the http://clarity/niku/nu#action:union.userInvalid page with the following error message - 'Error 401 - User not registered'.
Expected Results
: The user should be able to navigate back to the home page or see some meaningful message.
Actual Results
: The user gets Error 401 User is not registered on the reporting server.
DE61027: XOG Failing With Some Special Characters Like Logos
Steps to Reproduce:
  1. Add the logo (option + shift + K in a Mac) to a project title.
  2. Use XOG to read the project.
  3. Without any modification, use XOG to write the project.
Expected Results
: XOG write completes successfully.
Actual Results
: XOG write fails with a 'FATAL' error and "Input document contains Illegal HTML character for object project" exception.
DE60403 - Users are able to create timesheets for periods *before* their hire date
Steps to Reproduce
  1. Create a user ResA with relevant access rights.
  2. In Classic PPM navigate to Home, Resources, and edit the resource you created in the previous step.
  3. Set the Date of Hire as 12/4/20 (December the 4th).
  4. Ensure the Track Mode is set to PPM and the Open for Time entry option is enabled.
  5. Create a project that spans from 11/1/20 till 12/31/20.
  6. Add ResA as a team member.
  7. Log in as ResA.
  8. Go to Classic PPM and select View, Timesheets.
  9. Go to the Nov 30-Dec 6 timesheet.
  10. Enter time on any day prior to the DOH you set.
  11. Click on Submit, Approve buttons.
  12. Run the Post Timesheet job.
Issues Fixed in 15.8.1.5
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.
DE59678
:
Unable to create a new cost plan in Clarity if there are more than 500 attributes ahead of the Start field on the Project object.
Steps to Reproduce
  1. In the Classic PPM, go to Administration, Studio, Objects, Project, Attributes.
  2. Add additional attributes to the project object so that there are at least 500 attributes ahead of the Start field alphabetically. Ensure the attributes all have an API Attribute ID.
  3. Create a new project in Clarity.
  4. Populate the Department to financially enable the project.
  5. Click on the Financial Plans tab.
  6. Click the New Plan button.
Expected Results:
You will be able to see and populate the cost plan.
Actual Results
: Receive error: "API-1006 : The value ''undefined'' for Attribute 'startDate' is not in the expected format or is invalid and cost plan cannot be created.
DE58860
:
Multiple Task Selection Issue In Open Workbench (OWB)
SUMMARY: In OWB selecting a few tasks at the top of the Task List, then scrolling to the bottom and selecting more Tasks may result in multiple additional Tasks being selected.
Steps to Reproduce
  1. Open Project Plan in OWB that has about 380 Tasks associated with it.
  2. From the top of the page click on a few tasks - let's say four, one at a time.
  3. Now scroll quickly to almost the bottom of the page and again click to select (highlight) a few tasks.
Expected Results
: Only one Task to be highlighted at a time.
Actual Results
: Multiple tasks get highlighted.
Issues Fixed in 15.8.1.4
DE58107 - Tomcat access log import/analyze job does not load data after the job is completed
Steps to Reproduce:
  1. Ensure that app-access-2020-07-28.log file is available and it has below sort of sample log entries.
  2. Copy the below sample log entries into app-access-2020-07-28.log file.
    172.30.120.3|[28/Jul/2020:10:36:12 +0530]|GET /niku/nu HTTP/1.1|400|409|151|- 172.30.120.3|[28/Jul/2020:00:00:00 +0200]|GET /niku/nu HTTP/1.1|400|409|151|- 172.30.120.3|[28/Jul/2020:00:00:05 +0530]|GET -|400|-|0|- 172.30.120.3|[28/Jul/2020:00:00:00 +0200]|-|400|-|0|- 172.30.120.2|[28/Jul/2020:00:00:03 +0200]|-|400|-|0|- 172.30.120.3|[28/Jul/2020:00:00:05 +0200]|-|400|-|0|- 172.30.120.2|[28/Jul/2020:00:00:08 +0200]|-|400|-|0|- 172.30.120.3|[28/Jul/2020:00:00:10 +0200]|-|400|-|0|-
  3. Save changes in the file.
  4. Login to Clarity.
  5. Navigate to
    Home
    ,
    Reports and Jobs
    , and click the link.
  6. Go to the
    Jobs
    tab, and navigate to
    Available Job
    s
    .
  7. Search for
    Tomcat access log import/analyze
    job.
  8. Open the job and set the "Log Date" parameter as "2020-07-28" to run the analysis.
  9. Once the job is executed, navigate to
    Administration
    ,
    Security and Diagnostics
    and
    Log Analysis
    .
  10. Set the Date parameter as log date (2020-07-28), select the environment and hostname parameters, and click the filter button.
  11. The page has many portlets. Verify "Slow Actions by Day" portlet to reflect the log entries.
Expected Results: Tomcat access log import/analyze job loads data for system analysis after the job is completed.
Actual Results: Tomcat analysis job completes with the following message and fails to load any rows into the log tables.
"imported 0 log lines for service app..."
DE59227: API-1018 Error Message is displayed in the Tasks Board view (Clarity UI)
Steps to Reproduce:
  1. Open a project in Clarity UI.
  2. Switch to Tasks - Board view.
  3. Create a new card.
  4. Click on the card.
  5. Assign name through the Details fly out on the right-hand side.
  6. Press the Enter key.
Expected Results: The task is created.
Actual Results: The task is not created, instead, the following error message is displayed.
"API-1018: Could not process the request. Refer to error code for more details"
DE55922: API-1004 Error Message is displayed while creating a To-Do Item (Clarity UI)
Steps to Reproduce:
  1. Login to Clarity UI, and make a note of the account used to log in.
  2. Navigate to any project where the account being used is the project manager.
  3. Navigate to the Task Board.
  4. Create a new task on the Task Board, enter a task name, press Enter.
  5. On the same task flyout switch to the To-Do Tab.
  6. Create a new To-Do, enter a to-do name, and press enter.
Expected Results: A new To-Do is created.
Actual Results: The To-Do is not created, instead, the following error message is displayed.
"API-1004 error"
DE59105: 'Could not update the value.' An error message is displayed while adding a new column to an existing view for a custom investment (Clarity UI)
Steps to Reproduce:
  1. Create a custom investment.
  2. Create custom attributes to an extent that there are more than 200 API enabled attributes.
  3. In the Clarity UI, navigate to Investments - <the custom object>.
  4. Add about 20 attributes to the view and then remove them.
  5. Repeat step 4 with additional attributes until the following query returns 200:
    SELECT COUNT(*) FROM odf_ui_list_cols WHERE view_id =
  6. Add 1 more attribute to the view.
  7. Attempt to remove the attribute from the view.
Expected Results: The attribute gets removed from the view in the UI and its IS_SELECTED value in the table gets updated to 0.
Actual Results: The error message "Could not update value" is displayed. The attribute gets removed from the view in the Clarity UI, but it remains with an IS_SELECTED value of 1 in the table.
DE56355: User Without the API - Access Permission is Getting API-1029: Authentication Error after Clarity UI Times Out
Steps to Reproduce:
  1. Create a basic user. Do not provide the API-access permission. Just give view access rights to Project/Idea and basic rights to Timesheets.
  2. Connect to Clarity.
  3. Wait for the Clarity UI to timeout.
  4. Now, click anywhere in Clarity UI.
  5. Re-enter the login credentials.
Expected Results: The user is able to connect successfully.
Actual Results: The user gets API-1029: Authentication Error.
Issues Fixed in 15.8.1.3
DE58604 -Securability Fix
Steps to Reproduce: No Steps revealed for security reasons.
DE58255 - Classic Timesheet - Time Entry Note issue
Steps to Reproduce:
  1. In Clarity Classic Timesheet, enter some hours on a Timesheet and submit (in a scenario where values of PRID column in Prtimeentry table has 10 digits, for example, 3931834583).
  2. Ensure that the 'Note Icon' is available on the first column of the Timesheet page.
  3. Click on the Note Icon and you find that Resource, Time Period and Task name details are populated as expected.
  4. Go back to the Timesheet entered in step one and click the Note Icon.
Expected Results: Timesheet - The Time Entry Note portlet must populate Resource, Time Period, and Task name details.
Actual Results: Timesheet - The Time Entry Note portlet does not populate Resource, Time Period, and Task name details. The notes that you entered are lost.
DE57954 - In GCP SSO - Modern UX login pop up window comes post Inactivity timeout
Steps to Reproduce:
  1. Log in to Clarity using SSO in GCP SaaS System.
  2. Set the inactivity time out to 60 minutes.
  3. Leave the system idle for 60 minutes.
Expected Results: Once the system is idle for 60 minutes it should you log out and display the logout page.
Actual Results: The Clarity login page shows the same screen after inactivity of 60 minutes.
DE57943 - A task-based process with an auto-start event-create is triggered for a XOG assignment update operation
Steps to Reproduce:
  1. Create a simple Process based on the Task object. From Start Options set Start Event to Create.
  2. Create Project - Project1 with ID P1 and also create a Task called a Task Called Task1 with ID set to T1.
  3. Allocate a labor resource to the project.
  4. Use a XOG file which contains the Project name & ID and Task name & ID created in step 1, XOG in an Assignment using the resource from step 3.
Expected Results: The Assignment, which is added to a task-based process created in step one, does not start.
Actual Results: The Assignment, which is added to Task but the Task-based process also gets started although no task, is created.
Issues Fixed in 15.8.1.2
DE57747 - Investment specific charge codes are not honored in Modern UX Financials module
Steps to Reproduce:
  1. Log in to Classic PPM.
  2. Enable Investment specific charge codes under Administration, Project Management, Settings.
  3. Create an investment specific charge code under Administration, Project Management, Charge codes Log in to Clarity.
  4. Configure Financials in Project Blueprints.
  5. Open a Project and navigate to the Financials module.
  6. Create a Cost Plan with Charge Code as Grouping Attribute.
  7. In Cost Plan Details add a row and click on Charge Code.
Expected results: The investment specific Charge Code appears in the drop-down. Actual results: The investment specific Charge Code does not appear in the drop-down.
DE56189 - A User With Instance Rights for Approve/Edit Time May Not See All Timesheets in the New UX Timesheet Grid
Steps to Reproduce:
  1. Log in to Classic PPM.
  2. Create a new user that has only the following rights:
    1. Global
      1. Timesheets - Navigate
    2. Instance
      1. Resource - Approve Time
      2. Resource - Enter Time (add some instances, such as 10 different resources)
  3. Log in as this user to Clarity.
  4. Navigate to Timesheets, Review and Approve, and select any period (ideally a period in the future where timesheets have not been created).
  5. 10 timesheets are displayed as Open.
  6. Go to the Timesheets grid tab.
  7. Filter by the same period and the status is Open.
Expected Results: 10 timesheets are displayed. Actual Results: Zero timesheets are displayed.
DE57824 - Expose underlying tables via ODATA used in view ODATA dwh_inv_security_v, dwh_res_security_v
Steps to Reproduce:
  1. Prerequisite to reproduce the problem is to have medium size dataset with around 8+ million records in view dwh_inv_security_v, dwh_res_security_v.
  2. Log in to Classic PPM and navigate to Administration, General Settings, Data Warehouse ODATA SERVICE.
  3. Use the DATA WAREHOUSE ODATA V4 ENDPOINT URL and connect through Postman.
  4. Perform a GET Call. https://cppmbixxx.ondemand.ca.com/api/odata4/cppmxxxxtDataSourceV4/DWH_INV_SECURITY_V
Expected Results: The API get call dwh_inv_security_v should be able to fetch records but it times out after 15 minutes.
Actual Results: The API get call dwh_inv_security_v takes too long in PostgresSQL.
DE56821- Post to WIP job doesn't post all the transactions when we pass Obs parameter in the job
  1. Create more than 100 financially enabled projects (have the same OBS associated).
  2. XOG in transactions for the projects. Invalid transactions show all the transactions that are XOGed in.
  3. Run the Post Transactions to Financials job.
  4. From the Post to WIP page, filter in between transaction dates and verify all the transactions that are XOGed in are present.
  5. From the job filter for post to WIP and pass the OBS parameter (same as the OBS selected in the project).
  6. Run the job.
Expected Results: All the transactions are posted.
Actual Results: Only a few transactions are posted, other transactions are in the Post to WIP page.
DE55232 - Subpage of custom subobject is not created under master object for partition
Steps to Reproduce:
  1. Create a master object under the partition.
  2. Navigate to Views and click [Layout: Edit].
  3. Make changes to the General section and click Save.
  4. Create a subobject under the master object that you created in Step-1.
  5. Navigate to the master object and go to the Views tab.
  6. Select Views for the non System partition, click [Layout: Edit].
  7. The subpage for the custom subobject is not created.
Expected Results: Subpage for custom subobject is created for the non-system partition.
Actual Results: Subpage for custom subobject is not created for the non-system partition.
DE51165 - PRJ-07008 Error occurs when editing Assignments in the Classic and Modern UX
Steps to Reproduce:
  1. Log in to Clarity.
  2. Create a project with a single date of AUG 12 2019.
  3. Configure the Financial properties and set Financial Status to Open.
  4. Do not staff any resources.
  5. Create a task, for example, Task1 with the same date as the project AUG 12 2019.
  6. Do not assign any resources.
  7. Log in to Classic PPM.
  8. Navigate to Home, Financial Management: Transaction Entry.
  9. Create one transaction in this project for this task and this date for a financially enabled resource as follows: Resource1 - Transaction date = AUG 12 2019 (Task1)
  10. Run the Post To WIP job and execute the Import Financial Actuals job.
  11. Verify that the data is posted back to the project and the Resource1's assignment can be updated (update the 'Role' or 'Loading Pattern').
  12. Navigate to Classic, Home, Financial Management: Transaction Entry.
  13. Create two new transactions on this project for the same task using a different financially enabled resource as follows:
    1. Resource2 - Transaction date = AUG 12 2019 (Task1)
    2. Resource2 - Transaction date = AUG 14 2019 (Task1)
  14. Run the Post To WIP job and execute the Import Financial Actuals job.
  15. Verify that the data is posted back to the project.
  16. Change Resource2's assignment for the Loading Pattern or the Role field.
  17. Try in Classic PPM or Clarity - 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 displayed: 'PRJ-07008: Finish date earlier than the start date.
DE57138 - After GCP Upgrade missing timeslices
Steps to Reproduce:No specific steps to reproduce as this was an environmental issue.
DE57537 - Performance on Hierarchy Tab
Steps to Reproduce:
  1. Configure the hierarchy grid to have a custom attribute.
  2. Navigate to the hierarchy tab on a project that has one or more child investments.
Expected result: Reasonable performance.
Actual result: Performance is slow and sometimes the page times out.
DE57571 - Resource Planning Workloads slow to load
Steps to Reproduce:
  1. Create a process.
  2. Create a process step which runs the following gel script:
    1. <gel:script xmlns:gel="jelly:com.niku.union.gel.GELTagLibrary" xmlns:core="jelly:core" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://www.w3.org/2001/XMLSchema"> <!-- Create the xog client --> <core:new className="com.niku.xog.client.XOGClientInterface" var="XOGAdminClient"/> <!-- Get the Clarity Version for XML Header --> <core:invokeStatic className="com.niku.union.config.ConfigurationManager" method="getInstance" var="thisClarityConfig"/> <core:set value="${thisClarityConfig.getVersionProperty('version')}" var="ClarityVersion"/> <gel:log>Clarity version: ${ClarityVersion}</gel:log> <!-- *** Project XML Creation *** --> <gel:parse var="xml"> <NikuDataBus xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="../xsd/nikuxog_project.xsd"> <Header action="write" externalSource="NIKU" objectType="project" version="${ClarityVersion}"/> <Projects> <!-- insert the project tag here --> </Projects> </NikuDataBus> </gel:parse> <!--Create XML for Project --> <gel:parse var="Project"> <Project name="Test" projectID="test123456"> <Tasks> <!-- insert the task tag here --> </Tasks> </Project> </gel:parse> <!-- Create XML for task --> <gel:parse var="Task"> <Task finish="2020-12-31T17:00:00" internalTaskID="5078120" milestone="false" name="Test" outlineLevel="1" start="2020-06-01T00:00:00" status="0" taskID="~rmw"> <estimateRules/> </Task> </gel:parse> <gel:set insert="true" select="$Project//Tasks" value="${Task}"/> <gel:set insert="true" select="$xml/NikuDataBus/Projects" value="${Project}"/> <gel:log>XML: <gel:expr select="$xml"/> </gel:log> <gel:log>Project/Task XML To be XOGGED: <gel:expr select="$xml"/> </gel:log> <!-- Send the XOG request to Clarity --> <core:invoke method="invoke" on="${XOGAdminClient}" var="xogResponse"> <core:arg type="java.lang.String" value="xoguser"/> <core:arg type="org.w3c.dom.Document" value="${xml}"/> </core:invoke> <!-- Print the read response of XOG --> <gel:log>Response: <gel:expr select="$xogResponse"/> </gel:log> </gel:script>
  3. Connect the step, validate, activate and run the process .
Expected results: Process with the gel script to run successfully as it was in PPM 15.8.0 and older releases. Actual results: Process fails with gel tag exceptions captured in BPM errors and BG-ca.logs. BPM-0704: An error occurred while executing custom script: org.apache.commons.jelly.JellyTagException: null:32:68: <gel:set> Missing or invalid XML
DE56573 : Gel Scripts fail after upgrade to 15.8.1
Steps To Reproduce:
  1. Create a process.
  2. Create a process step which runs the following gel script:
    <gel:script xmlns:gel="jelly:com.niku.union.gel.GELTagLibrary" xmlns:core="jelly:core" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://www.w3.org/2001/XMLSchema"> <!-- Create the xog client --> <core:new className="com.niku.xog.client.XOGClientInterface" var="XOGAdminClient"/> <!-- Get the Clarity Version for XML Header --> <core:invokeStatic className="com.niku.union.config.ConfigurationManager" method="getInstance" var="thisClarityConfig"/> <core:set value="${thisClarityConfig.getVersionProperty('version')}" var="ClarityVersion"/> <gel:log>Clarity version: ${ClarityVersion}</gel:log> <!-- *** Project XML Creation *** --> <gel:parse var="xml"> <NikuDataBus xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="../xsd/nikuxog_project.xsd"> <Header action="write" externalSource="NIKU" objectType="project" version="${ClarityVersion}"/> <Projects> <!-- insert the project tag here --> </Projects> </NikuDataBus> </gel:parse> <!--Create XML for Project --> <gel:parse var="Project"> <Project name="Test" projectID="test123456"> <Tasks> <!-- insert the task tag here --> </Tasks> </Project> </gel:parse> <!-- Create XML for task --> <gel:parse var="Task"> <Task finish="2020-12-31T17:00:00" internalTaskID="5078120" milestone="false" name="Test" outlineLevel="1" start="2020-06-01T00:00:00" status="0" taskID="~rmw"> <estimateRules/> </Task> </gel:parse> <gel:set insert="true" select="$Project//Tasks" value="${Task}"/> <gel:set insert="true" select="$xml/NikuDataBus/Projects" value="${Project}"/> <gel:log>XML: <gel:expr select="$xml"/> </gel:log> <gel:log>Project/Task XML To be XOGGED: <gel:expr select="$xml"/> </gel:log> <!-- Send the XOG request to Clarity --> <core:invoke method="invoke" on="${XOGAdminClient}" var="xogResponse"> <core:arg type="java.lang.String" value="xoguser"/> <core:arg type="org.w3c.dom.Document" value="${xml}"/> </core:invoke> <!-- Print the read response of XOG --> <gel:log>Response: <gel:expr select="$xogResponse"/> </gel:log> </gel:script>
  3. Connect the step, validate, activate and run the process.
Expected results: Process with the gel script to run successfully as it was in PPM 15.8.0 and older releases. Actual results: Process fails with gel tag exceptions captured in BPM errors and BG-ca.logs. BPM-0704: An error occurred while executing custom script: org.apache.commons.jelly.JellyTagException: null:32:68: <gel:set> Missing or invalid XML
DE56247 - Classic UI Timesheets - Error 401 Unauthorized thrown when Create Task option is used
Steps to Reproduce:
  1. Create a new resource from Administration, Resources. Navigate to Home, Projects. Create a new project.
  2. Navigate to the Team tab, make the resource created in Step-1 a Team member.
  3. Provide the resource from Step-1 the following Access Rights:
    Note: The project right should be over the one created in Step-2.
    1. Instance Rights
      1. Project - View
      2. Project - View Tasks
      3. Project - Edit Project Plan
    2. Global Rights
      1. Timesheets - Navigate
  4. Navigate to Home, Resources, <resource>, Setting.
  5. Set the following options:
    1. Track Mode - PPM
    2. Open for Time Entry - True for the resource from Step 1.
  6. Log in using the account created in Step 1.
  7. Log in to Classic PPM. Navigate to Timesheets.
  8. Open any timesheet.
  9. Click Add Task. Click Create Task.
  10. Select the investment from Step 3 and provide Task Name and ID.
  11. Click Save and Return.
Expected Result: That a new unplanned task is created. Actual Result: The following error appears: Error 401 - Unauthorized. You are not authorized to view the page. If you are sure you have access, try logging in again or contact your system administrator.
DE57172 - NSQL Lookup with concat not showing full value in New UX (GCP/Postgres)
Steps to Reproduce:
  1. Log in to a Classic PPM environment using a Postgres database (does not occur in Oracle).
  2. Create a new lookup using concat to combine two values. Example:
    SELECT @SELECT:S.CODE:[email protected], @SELECT:S.NAME:[email protected], @SELECT:S.FULL:[email protected] FROM (select ID as ID, CODE as CODE, NAME as NAME, concat(concat(NAME,' - '),CODE) as FULL FROM ODF_CA_CUSTOM_OBJECT) S WHERE @[email protected]
  3. Create a new lookup attribute on the Project object using this lookup.
  4. Add an API Attribute ID on this attribute to make it available in Clarity.
  5. Log in to Clarity.
  6. Add the newly created field to a blueprint.
  7. Associate any existing or new project to this blueprint.
  8. Open the project details.
  9. Click the drop-down for the lookup.
Expected Results: The available values display as full name - code.
Actual Results: The values only display the name. However, when a value is selected it does display the value as full name - code in the field.
DE57561: New UI Admin: Blueprint Changes Don't Save Consistently
Steps to Reproduce:
  1. Log in to Clarity as a user with administrative rights.
  2. Click Administration, Blueprints.
  3. Edit an existing Blueprint or create a new one.
  4. Pick a section to modify, for example, Project or Idea Summary.
  5. Drag the fields to the right.
  6. Make some longer than others, others smaller.
  7. Click Save. The layout is not saved. This is inconsistent.
Expected Results: Layout changes to a Blueprint are saved consistently. Actual Results: Layout changes to a Blueprint are not saved consistently.
DE56875 - Performance: Datamart Extraction jobs run for more than an hour in GCP postgres
Steps to Reproduce:
  1. Run the Datamart Extraction jobs in postgres GCP environments.
DE57663 - GCP Only - Load Data Warehouse deadlocks on grant GRANT SELECT ON ALL TABLES IN SCHEMA sXXXXpdwh TO sXXXXpdwh
Steps to Reproduce:
  1. Lock a record in the Data Warehouse.
  2. Run the DWH Load.
Expected Results: DWH Load finishes.
Actual Results: DWH Load gets deadlocked.
DE57649 - Report and Job's scheduled job Log list page takes time to load and sometimes times out. In Postgres environment, the job log page sometimes takes a long time to load.
Steps to Reproduce:
  1. Log in to the system as a user with rights to execute jobs.
  2. Navigate to Home, Reports and Jobs, Jobs, Log.
Expected results: The page should load quickly.
Actual: Page loads very slowly and sometimes times out.
DE57216 - Multi level lookup attribute values are not displayed in Modern UX Grid view until the object instance is created
Steps to Reproduce:
  1. Log in to Classic PPM. Create a custom investment object.
  2. Ensure it is enabled for Clarity.
  3. Create a lookup type attribute MyLkp.
  4. Use the Investment Type (INV_TYPE) lookup.
  5. Enable the attribute for Clarity.
  6. Log in to Clarity.
  7. Navigate to Investments.
  8. The custom investment object is created.
  9. From the grid view, add the MyLkp attribute to the grid.
  10. Place the column in between Name and ID, both are required fields.
  11. Give a name, select a value for the MyLkp field.
Expected Results: The value selected to be displayed.
Actual Results: The selected value does not display. Fill the ID in and as the instance gets created, the lookup selected value displays.
DE57600: Charge Code values not available in the dropdown in Modern UX
Steps to Reproduce:
  1. Log in to Clarity.
  2. Open any project.
  3. Financially enable it.
  4. Create a cost plan with charge code as Grouping attributes.
  5. Add a cost plan detail row and try to select a charge code.
Expected Results: You are able to select a charge code.
Actual Result: None of the charge codes are available to be selected.
DE57629 - Subobject instance click takes a long time
Steps to Reproduce:
  1. Log in to Classic PPM.
  2. Open project "Test Project".
  3. Hover over Properties and click the subobject.
  4. Open any instance.
  5. It takes a long time to open the edit view of the sub-object.
  6. Make a change to the subobject and click Save.
Expected Results: The action is completed quickly.
Actual Results: It is very slow. The action takes more than 5 times the time expected.
DE54742 - New UI: In Financial a list is cut off if browser Zoom is increased
Steps to Reproduce:
  1. Increase the Zoom in the Browser settings.
  2. Log in to Clarity, open a Project.
  3. Navigate to the Financials section.
  4. Create a Plan or click an existing plan.
  5. On the plan screen click the blue plus (+) icon to add a new row.
  6. On the new row double - click Role to select an item.
Expected Results: In most circumstances, to see an alphabetical list of items.
Actual Results: If the Zoom is increased on the browser, the list goes up, and only shows the items at the bottom of the list. It is not possible to scroll through the options.
DE57275: Can not enable attribute for Audit
Steps To Reproduce:
  1. Navigate to Administration, Objects.
  2. Search for the Task object.
  3. Navigate to the Audit Trail tab.
  4. In Attribute Audit, from the list of available attributes select Duration and move it to the list of Audited attributes.
  5. Click Save.
Expected result: the save is complete and the attribute is enabled for audit trail.
Actual result: after pressing the "Save" button, it keeps loading until you get an "Internal server error".
DE54302  - PPM Gantt Scroll Bar disappearing when zooming out in Firefox 79 or later
Steps to Reproduce:
  1. In a Firefox browser window, open an existing project or create a new project having enough tasks at least fill two browser windows on the Gantt.
  2. Make sure that the browser zoom is set to 100% or greater.
  3. Open the task list in the Gantt and notice that the vertical scroll bar is present.
  4. Change the browser zoom to anything less than 100%.
Expected Results: The vertical scroll bar is still present to scroll to the bottom of the task list.
Actual Results: The vertical scroll bar disappears so there is not a way to scroll to the bottom of the list.
Issues Fixed in 15.8.1.1
DE57188  - Export to CSV: Hyperlinks with char length more than 255 do not work
Excel has a limitation of 255 characters for links and Excel will truncate the link. This fix will check if the link is more than 255 characters, we will display the only label with no link.  If the link is less than or equal to 255 characters, we display the label and link.
Steps to Reproduce:
  1. Click on Project list.
  2. From the upper right hand corner, click on the gear icon.
  3. Click on Export to CSV.
  4. Verify the exported csv files and verify the links are properly exported.
  5. Now click on any existing project.
  6. Click on the Status Reports subpage ( using he down arrow next to Properties Tab).
  7. Create a new status report with name as "sr_test".
  8. From the status report list page click Export to CSV.
Expected Results - The csv is generated with working links
Actual Results - The links do not work
DE56341 - Query Dependent Lookup Values on the custom object module list page does not preserve the value
Steps to Reproduce:
  1. Log in to Classic PPM and Navigate to Administration, Object.
  2. Create a sub object of Project and name it as for example, AAA.
  3. Create a Dynamic Query lookup.
  4. Create a lookup attribute using the above created dynamic lookup.
  5. Save the attribute and now set the Lookup Parameter Mapping to --Object ID--.
  6. Now Navigate to Clarity and add the AAA object as a module in your blueprint.
  7. Navigate to the AAA module list page and add the attribute Lookup Attribute.
  8. Create an instance of Dependency and fill the value for Lookup Attribute.
  9. Refresh the browser and now the Lookup Attribute value does not appear, however in the details layout the value remains.
Expected Results: The value of lookup attribute (Lookup Attribute) should be shown on the list page.
Actual Results: The value of lookup attribute (Lookup Attribute) disappears.
DE55738 - Calculated attribute with DateDiff doesn't work properly in PostgreSQL
Steps to Reproduce:
  1. Using Classic PPM, add the following calculated attribute called:
    "% Schedule Gap" (DateDiff(schedule_finish,baseline_finish,"Day")/+DateDiff(baseline_finish,baseline_start,"Day"))*100
  2. Add the field to the view: "Project Summary::projectGeneral".
  3. Review a project that has the following fields populated:
    • Property Label
    • % Schedule Gap
    • Baseline Start
    • Baseline Finish
    • Finish Date
  4. Review the "% Schedule Gap" field.  The calculation is incorrect.
Expected Results: Calculated attribute using DateDiff report is correct calculation.
Actual Results: Calculated attribute using DateDiff shows "0" or some other incorrect value.
DE50348 - Patch 15.8.1.1: Synchronize Agile Central job is failing in Production
Steps to Reproduce:
  1. Log in to Classic PPM.
    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 Classic PPM, 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 unchecked as there are exceptions processing the request.
DE55120 - Rally sync error API-1019 post upgrade to 15.7.1 for some projects
Steps to Reproduce:
  1. Log in to Classic PPM.
    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 milestones.
  3. In Classic PPM, run the Synchronize Agile Central job.
Expected Results: Project and tasks sync successfully and the Synchronize Agile Central job is executed successfully.
Actual Results: For some projects, the job fails with the following error: There was a problem syncing tasks for the CA PPM project: <Project Name>500api.internalErrorAPI-1019 : Could not process the request due to internal error.
DE56197 - OBS filtering on Custom Object is not working
SUMMARY: Unable to filter  OBS unit on Customer Objects
Steps to reproduce:
  1. Log in to Classic PPM as Administrator.
  2. Create a customer master object (example: Suman Custom Object) and API enable the object.
  3. Either create an OBS or use an existing OBS and associate the object created (example: Suman Custom Object).
  4. Once the OBS association is done, you can enable the API Attribute in order to see even in Clarity.
  5. Go to the Custom object Menu from Classic PPM and create a couple of instances for the object created and update the OBS unit.
  6. Configure the Custom Object List Page to add OBS Unit in filter and list section.
  7. On the filter section select an OBS Unit and filter.
Expected Results: The list page should fetch the result based on the OBS UNIT match.
Actual Results: The list page does not show any records even when filter value matches.
Workaround: Log in to Clarity and filter the OBS unit and it shows the correct value.
DE54888 - New UX - Filtering on Project Grid reverts to original results
Steps to reproduce:
  1. Connect to a large customer dataset (see environmental details below).
  2. Go to Projects - Grid
  3. Note the number of projects there.
  4. Now quickly add a filter, i.e. Active =Yes.
  5. Note the amount of projects changing down.
  6. Within 5 seconds, note the amount of projects that are reverting to the initial number.
DE56718 - Error 401 - Unauthorized when returning to the project Team Staff list
STEPS TO REPRODUCE:
  1. Create a user UserA .
  2. Create a project MyProject and add a team member.
  3. Add every instance access right related to the project object for MyProject.
  4. Add also the Projects Navigate global right.
  5. Log in as UserA.
  6. Go to Project Management, Projects, and edit the MyProject project.
  7. Go to the Team tab.
  8. Click Staff Member Properties.
  9. Click Return, Save and Return.
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.
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
      Clarity
      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.
To learn more about installing Jaspersoft, see Install and Configure Advanced Reporting with Jaspersoft 7.1.3. To learn more about upgrading to the latest version of Jaspersoft, see Clarity Jaspersoft 7.1.3 Upgrade Assistant.
Issues Fixed in JasperReports Server 7.1.3_6.3.0.1 for
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
    Classic 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
    Classic 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
Clarity
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
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.