Page count and Displaying count doubles in a list view if there is an Aggregation Row

Products

• Clarity PPM SaaS

Issue/Introduction

Classic Clarity PPM Page count and Displaying count doubles in a list view after the last row in the list view is updated that causes it to be filtered out of the list view if there is an aggregation row on the page. This is reproducible in out of the box and custom objects and can be caused by a user action such as in the steps to reproduce below or a custom process/action.

Steps to Reproduce:

1.      In Classic PPM, go to a project

2.      Click on the Properties tab drop down and select Status Reports

3.      Click Options->Configure

4.      Move ‘Report Status’ to Selected Columns if not there already and click Save.

5.      From the List Column Section tab drop down, select Options

6.      Set Rows per Page to 10 and click Save

7.      From the List Column Section drop down select ‘Aggregation’

8.      Click  ‘Add’

9.      Enter a label and for the two default attributes enter a function and Save and Return

Examples: Overall Status Function = Sum and Report Date Function = Count

10.   Create 21 status reports -  populating them with a status report name, ID, and Report Status of Draft

11.   In the filter section of the status report page, change Report Status from ‘All’ to ‘Draft’ and click filter

12.   Go to page 3 where there should be just one row

13.   From the list view, change the Value of the status report on page 3 from Draft to Final and click Save

14.   View the Page number values and “Displaying” values on the bottom right of the list

Expected Results: Page counts and display counts should reflect the number of rows / pages in the list (In this example, Page 2 of 2 and Displaying 11-20 of 20)

Actual Results: Page counts are doubled (In this example, Page 2 of 4) and Displaying also doubles (In this example, Displaying 11-20 of 40)

Environment

Release : 15.3 ,15.4, 15.4.1, 15.5, 15.5.1, 15.6, 15.6.1

Component : CA PPM SAAS BUSINESS PROCESS MANAGEMENT

Resolution

This issue is under review as DE50216

Workaround: Remove the aggregation row if not needed or click Filter again then go back to Page 2 (or the desired page)