ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

Columns width and wrapping splitting up words in Classic UI

book

Article ID: 222014

calendar_today

Updated On:

Products

Clarity PPM SaaS Clarity PPM On Premise

Issue/Introduction

Column Width/Word Wrapping is not working correctly in 15.9.3, the alignment is off. You may notice this as fields being clipped. When the entire word does not fit, it starts the next line without regard to where it is in the word and everything is misaligned.  You may only see a max of 3 characters per line and see the words stretched over 5 lines. This makes it difficult to read the data / the data shows poorly. 

This happens in all browsers and all UI Themes including Phoenix.

Examples where this may be seen include:

  • Dashboards
  • Portlets (examples below):
    • Requisitions
    • Resource Planning portlets such as Workloads 
  • Cost Plans
  • Aggregated Tiles (Totals lines)
  • List views / grid in Classic (Including Status Reports object)
  • Large String fields
Large String fields are clipping in Classic UI portlets/list pages

STEPS TO REPRODUCE: 

Example 1: Project List page

  1. Log in to the Classic UI
  2. Go to Home>>Portfolio Management>>Projects
  3. Configure the Project list view to have around 10 columns, including Department and Manager

Expected Results: Word Wrap should not split words

Actual Results: Department shows Shared Serv / (next Line) ces

Example 2: Aggregation rows:

  1. Go to one of the Resource Planning portlets
  2. Select any portlet that has Aggregation set on it
  3. Ensure the first column displayed is a virtual image
  4. Look at the Word Wrapping of the Aggregation row

Below is a screenshot of how it looks prior to 15.9.3:

In 15.9.3, below is an example where the Word Wrapping happens:

Cause

DE62231

Environment

Release : 15.9.3

Component : Clarity Studio

Resolution

This is fixed in 16.0 and patched in 15.9.3.1 (15.9.3 patch 1)

Workaround for aggregation use case:

Modify the layout of the portlet, so the first column is not a virtual image

Additional Information

See also: 

  • Clarity frequently reported issues
  • Known Issues - For a highlight of the most commonly reported defects in 15.9.3. Note that this is not an all-inclusive list, so we encourage you to utilize our self-service as well if your issue is not found on this list. 

Attachments