Pagination in Classic PPM broken portlets

Products

• Clarity PPM On Premise
• Clarity PPM SaaS

Issue/Introduction

The pagination on Classic PPM portlets gets broken when an attribute whose ID is 'clarity' is placed on the portlet filter

STEPS TO REPRODUCE:

1. Classic PPM > Studio > Objects
2. Create a string type attribute which id is 'clarity'
3. Go to the project list and notice the pagination works and can navigate across pages
4. Go to the project list and add the attribute with id 'clarity' to the filter
5. Try to navigate across pages

Expected results: Pagination to work
Actual results: Pagination breaks and arrows do not respond

Cause

This is caused by DE80280

Resolution

Workaround: create a new attribute with a different id or exclude the attribute from the filter

This is fixed in 16.2.2

Additional Information

The cause of the problem is that the main javascript in clarity.js sets up a global object on the window called - clarity. Off this object, the application adds all sorts of functions and properties. When an attribute with ID=clarity is created and added as an input field to a filter or property page in Classic an <input> element with name="clarity" is added to that page. This element overlays the clarity object that the UITK shell created and none of the functions or properties that were on that property are available in that page. So, things like pagination don't work because the paginate function was added to clarity.uitk and the clarity property is now an input element. 

Studio will be modified to add clarity to the list of reserved words that CANNOT be used when making the ID of an attribute: