Issues entering data in 16.2.3.1 MUX using non-English locale

Products

• Clarity PPM On Premise
• Clarity PPM SaaS

Issue/Introduction

SCENARIO 1:

Trying to update any attribute (String, Number...) from the flyout/properties page when using a non-English locale (not language) does not update its value.

This does not happen with attributes that use specific UI elements to enter data, such as Lookups, Dates...

The attribute stays highlighted and also stops updating its display value, even if a different row is selected in the Grid view.

Steps to Reproduce:

1. Go to the Project Grid view and open the Details flyout.
2. Select one project (row) and update its name from the Details flyout (e.g.: from 'My Project' to 'My Updated Project').
3. Click away from the attribute (select some other attribute).

Expected Results: The name of the project is updated in the Grid.

Actual Results:

The name of the project is not updated in the Grid (it still displays 'My Project').

Changing to a different project (e.g.: 'Their Project') does not reflect any changes in the flyout for that specific attribute, whereas the rest of the attributes show the 'Their Project' values.

The attribute stays highlighted as selected.

Inspecting the Developer Tools Console, an error similar to this can be observed:

p-6e0a64ff.js:1 Uncaught Error: E_MISSING_BUNDLE: {"locale":"en"}
    at x (p-6e0a64ff.js:1:12583)
    at B (p-6e0a64ff.js:1:12670)
    at G.exports.j.main (p-6e0a64ff.js:1:14698)
    at v (p-6e0a64ff.js:18:16297)
    at Z (p-6e0a64ff.js:18:21785)
    at e.numberParser.e.numberParser (p-6e0a64ff.js:18:25083)
    at new F (p-efa9fad9.entry.js:1:3255)
    at I.isValid (p-efa9fad9.entry.js:1:11193)
    at I.change (p-efa9fad9.entry.js:1:8466)
    at I.changeInput (p-efa9fad9.entry.js:1:6969)
    at j (p-f6d7fb2d.js:1:1644)
    at Object.emit (p-f6d7fb2d.js:1:1532)
    at e.onInputFn (p-e1da346d.entry.js:1:273)
    at HTMLInputElement.onInput (p-e1da346d.entry.js:1:1718)

 

SCENARIO 2:

Unable to create projects from template with a user whose locale is Non-English

Steps to Reproduce:

1. Login to MUX and go to the Projects grid.
2. Click on New from Template.
3. Fill all the required fields.

Expected Results: The Create button to get enabled so a project can be fulfilled.

Actual Results: The Create button is disabled and no project can be created.

 

SCENARIO 3:

Unable to create new views using the Save As option with a user whose locale is Non-English.

Steps to Reproduce:

1. Login to MUX and go to the Projects grid or any other module where views are available.
2. On the views drop-down > Click on Save As.
3. Change the view name and click on Save.

Expected Results: A new view to be created.

Actual Results: The following message displays: 'Are you sure you want to replace <Original view name> with the current view?'

 

SCENARIO 4:

Unable to create new channels on Blueprints with a user whose locale is Non-English.

Steps to Reproduce:

1. Go to MUX > Administration > Blueprints
2. Edit a project Blueprint
3. On the Modules tab, click on Edit and add a channel
4. Provide a Channel Name and URL

Expected Results: The Preview button to be enabled and be able to Publish the blueprint

Actual Results: The Preview button is not enabled and publishing the blueprint does not create the channel

 

Note: This issue is a generic issue in MUX with Non English Locale and can occur on other pages and scenarios as well such as Create Ideas etc. The above scenarios are examples.

Environment

Clarity 16.2.3.1

Cause

DE155211

Resolution

DE155211, fixed in 16.3.1 and patch 16.2.3.2