Key Results Unexpected Locale Behavior When Entering Decimals

Products

• Clarity PPM On Premise
• Clarity PPM SaaS

Issue/Introduction

Actual Value or Target Value in the Details flyout for Key Results in Objectives show inconsistent/unexpected behavior in some locales, such as Spanish (Spain).

Steps to Reproduce:

1. Log in with a user with the locale Spanish (Spain) locale.
2. Create or open an existing Objective.
3. Navigate to the Key Results.
4. Create or open an existing Key Result.
5. Open the Details flyout and Navigate to Actual Value (or Target Value).
6. Use the Quick Create '+' button with the date of today, and for the Value column, try to enter:

Actual Results:

'10,5' [comma ',' is decimal separator in Spanish (Spanish) locale] or '10.5' [dot '.' is thousands separator in Spanish (Spanish) locale]:

The value '11' is briefly shown, then it is changed to '10'. 'Current Value' in the Key Results grid is '11'. If the Key Results grid has the Number Decimal Display set to '0.0', '0.00' or 'Auto', the grid displays '11' first, then the expected value ('10,5', '10,50' or '10,50'; respectively) for the Key Results grid.

(Specific to '10.5' only: while entering and the value and the value is exactly '10.', a message 'Please enter a valid number' is displayed, but when finishing typing and the value is '10.5', the value is accepted).

Expected Results:

• '10,5': The value in the Actual/Target Value grid is accepted and consistent with the value displayed in the Key Results grid. Also, it is not necessary to refresh the page to see this consistent value.
• '10.5': 'Please enter a valid number' message is displayed ('10.5' is not a number correctly formatted using this Spanish (Spain) locale - as a counter example, '10.500' is a valid number in that locale containing a dot (Ten Thousand Five Hundred), but this value works fine).

 

Note: Other locales may also exhibit other behaviors that do not match the locale definition expectation.

Environment

Clarity 16.3.0, 16.3.1.

Cause

DE166475

Resolution

This issue is fixed in Clarity 16.3.2.