MUX - Making attributes mandatory based on a value selection in another attribute.

Products

• Clarity PPM SaaS
• Clarity PPM On Premise

Issue/Introduction

When attempting to update attribute using arrow keys if done fast the required attribute pop-up screen does not come up or in some cases will come when user has focus on a different row causing required attribute to be updated on the wrong record..

Steps to Reproduce: 

1. Navigate to Studio and create custom master object and API enable it.
2. Go to Attributes tab and create a lookup attribute and API enable it.
3. Go to Attributes tab and create a string attribute and API enable it.
4. Navigate to MUX->Administration and create a copy of the blueprint for the object created in step 1 above.
5. Create a rule where if certain value of the lookup created in step 2 is true make string attribute created in step 3 required.
6. Publish Business Rule.
7. Navigate to MUX->Custom Objects
8. Create few instances of this custom object and set them to the modified blueprint from step 4 above.
9. Using keyboard arrows try to attempt and update the lookup attribute and after selecting the value somewhat fast click on arrow to go down to next record.
10. Notice you either will not see required attribute pop-up or it will pop-up and by then user is on the different record and by updating required attribute via pop-up it is updating a diffirent record.

Expected Results: it should bring required attribute pop-up quickly.

Actual Results: it does not bring required attribute quickly when using arrow keys from the keyboard.

Resolution

DE156920, Fixed in 16.3.1.

Workaround: attempt to do updates a bit slower.