Inconsistent behavior for Percent Type Number attributes which are set for 0 Decimals- ORACLE ONLY

Products

• Clarity PPM On Premise
• Clarity PPM SaaS

Issue/Introduction

SUMMARY: Modern UX: Inconsistent behaviour for Percent Type Number attributes which are set for 0 Decimals in Classic and Modern UX

 

STEPS TO REPRODUCE: 

1. Login To Clarity.

2. Navigate to Administration -> Objects -> Project.

3. Create a new Number type attribute, set the decimal's to 0 and select "Show as Percent".

4. Add an API Alias to this attribute.

5. Configure the attribute to property view and list view of the project object.

6. Navigate to Home -> Projects. Choose a project and add "35.45" as the value for the number attribute created on step 3 and save it.

7. Check the value that is displayed after the save and it shows the value as 35%.

8. Navigate to Projects List view and you will see the value as "35.45%".

9. Navigate to Modern ux -> Projects Grid. Add the attribute created on Step 3 to the grid. Try adding the value with a Decimal in the Grid, Modern UX doesn't allow the value with a decimal.

 

Expected Results :- The behaviour should be consistent across Classic and Modern UX.

Actual Results :- Currently Classic is allowing a Decimal value even though the decimal places are set to 0.

 

Additional Information :- 

Customer expectation is that we shouldn't allow saving of Decimal Value when decimals are set to 0 for the Number type attribute.

 

Resolution

This is currently being reviewed as DE77750.