Conditional Required Modal rule pop up Save button missing
search cancel

Conditional Required Modal rule pop up Save button missing

book

Article ID: 391439

calendar_today

Updated On:

Products

Clarity PPM SaaS Clarity PPM On Premise

Issue/Introduction

Unable to save changes on a Conditional Required Modal rule if an attribute is locked at that object instance.

The save button is missing when using Conditional Required Modal pop up.

Steps to Reproduce: 

  1. Login as Admin and navigate to MUX->Administration->Blueprints
  2. Create a copy of the default project blueprint and edit it.
  3. Create Rule of type Conditional Required Modal and choose Target Attribute as Sponsor if Value Changes then open the modal.
  4. Publish Blueprint and set that blueprint to whatever project you will be testing with.
  5. Navigate to Classic go to Administration->Processes
  6. Create a simple process where you will lock a custom attribute using system action. Tested with string type attribute
  7. Connect Start to Finish and validate and activate the process.
  8. Run the process against the project you will be testing your business rule for. Make sure attribute was locked.
  9. Navigate back to MUX->Projects and open the same project for which attribute was locked.
  10. Change value for Sponsor and notice Conditional Required Modal popup comes up but no Save button is showing.

Expected Results: Save button to be available so changes can be performed .

Actual Results: Save button is missing

Environment

Clarity 16.3.1

Cause

This is caused by DE168045

Resolution

This is fixed in 16.3.2.