Range Description Display Mapping Fails on Boundary Values
search cancel

Range Description Display Mapping Fails on Boundary Values

book

Article ID: 449660

calendar_today

Updated On:

Products

Clarity PPM SaaS Clarity PPM On Premise

Issue/Introduction

Range Description Display Mapping Fails on Boundary Values

STEPS TO REPRODUCE:

  1. Go to Classic UI
  2. Navigate to Administration → Objects → Project Object
  3. Create / select a Number / Custom Aggregated Calculated attribute.
  4. Configure Range & Value (Display) Mappings with consecutive numeric ranges, e.g.: Green–On Track 1–60, Yellow–Needs Help 61–80, Red–At Risk 81–120 (or) Green–On Track 1–10,
    Yellow–Needs Help 11–20, Red–At Risk 21–30
  5. Go to Modern UX, Administration → Attributes
  6. Set Display Type to "Range Description" (also reproduces with "Range Description and Value").
  7. Add the attribute as a column on a Project/Investment grid view.
  8. Ensure at least one record's underlying value equals exactly the upper bound of a range (e.g., value = 60).
  9. View the grid.

Expected Result: A value of 60 should show "On Track" (green), same as any other value between 1 and 60.

Actual Result: Rows where the value exactly equals a range's upper "To" boundary (10, 20, 30, 60, 80 etc.) display the number instead.

Environment

16.4.2

Cause

DE209701 

Resolution

Fixed in 16.5.0 and 16.4.3.1

Additional Information

Workaround:

Due to DE209701, the highest value (upper bound) in a range is excluded. To ensure boundary values are captured, overlap the ranges so the upper bound of one matches the lower bound of the next. When ranges overlap, the lowest margin is used to pick the range.

  • Fails (gaps on 60, 80, 120): 1 – 60 | 61 – 80 | 81 – 120

  • Works (60, 80, 120 are captured): 1 – 60 | 60 – 80 | 80 – 120 (e.g., 60 is captured by 60 – 80)