Conditional Required Modal rule type is not working on Staff Properties page
search cancel

Conditional Required Modal rule type is not working on Staff Properties page

book

Article ID: 388382

calendar_today

Updated On:

Products

Clarity PPM On Premise Clarity PPM SaaS

Issue/Introduction

Summary: A Conditional Required Modal rule is not working when the user updates a ‘Target Attribute’ on a blueprint that is configured with the Staff Module and ‘Enable Properties Navigation’ is toggled on.  

 

The ‘View Page’ or ‘Attribute Update’ rule types work as expected.

 

Steps to Reproduce: 

  1. Create a new project or other investment type Blueprint
  2. For the 'Staff' module 'Enable properties navigation'
  3. Configure the Module to display the following fields:
    • Staff Type
    • Requested Manager 
    • Custom Field - 'Requested Experience' (plain string field) 
  4. Create a new Conditional Required Modal rule
    • Target Object = Staff 
    • Rule Type = Conditional Required Modal 
    • Target Attribute = Requested Manager
    • Next - on the modal add the 'Requested Experience' field 
  5. Publish the blueprint changes
  6. Create a new project or use an existing project and associate the blueprint 
  7. Ensure you have a few ROLES staffed on the project 
  8. In the Grid, you can successfully trigger the rule by updating the 'Requested Manager' field 
  9. Click on the Role hyperlink to open the Staff 'properties' page
  10. Update the 'Requested Manager' field 

Expected Results: When updating the ‘Target Attribute’ on the Staff Properties page that meets the condition for the rule, the modal should display and prevent the user from updating the value unless the conditional required fields are filled in.

Actual Results: The value for the Target Attribute is updated without forcing the user to enter values for the required fields defined on the rule.

Workaround: Do not add the ‘Target Attribute’ on the Staff Properties page when it is enabled for navigation. This will prevent the user from updating the field without forcing them to update the required fields. 

Environment

Clarity Release 16.3.1 

Cause

DE166320   

Resolution

DE166320 - Fixed in Release 16.3.2