Business Rule Not Dynamically Updating Grandchild Module Visibility.

Products

• Clarity PPM On Premise
• Clarity PPM SaaS

Issue/Introduction

We have observed an issue where a Business Rule used to hide a Grandchild module based on a condition in its parent object does not dynamically update the UI. The module visibility only changes after a manual page refresh.

 

Steps to Reproduce: 

 

1. Create three custom objects:

 

a. Test Master (parent object)

b. Test Child (child of Test Master)

c. Test Grandchild (child of Test Child)

 

2. Assign Access:

 

a. Ensure that Admin global rights are granted to manage all three objects.

 

3. Configure Blueprints:

 

a. In the blueprint for Test Master, add Test Child as a module.

b. In the blueprint for Test Child, add Test Grandchild as a module.

c. Save and publish all blueprint changes.

 

4. Create a Business Rule:

 

a. Add a custom attribute (e.g., checkbox or dropdown) to the Test Child object.

b. Create a Business Rule on Test Master that hides the Test Grandchild module based on a condition in Test Child (e.g., when the field is empty).

c. Ensure the rule is correctly targeted at the Test Child level, not Test Master.

 

5. Test the Behavior:

 

a. Open an instance of Test Master.

b. Modify the custom field in Test Child to meet or not meet the rule condition.

 

Expected Results: The Test Grandchild module should automatically appear or disappear based on the rule condition without requiring a manual refresh.

 

Actual Results: The rule logic works, but the UI does not reflect the module visibility change unless the browser is manually refreshed. Without refreshing, the Test Grandchild module remains visible or hidden incorrectly.

Environment

Clarity 16.3.1, 16.3.2

Cause

DE172343

Resolution

Not reproducible in 16.3.3.

Workaround: Rule works as expected in the Details Flyout.