Second Business Rule on Clarity Modern UX, does not gets triggered if the first Business Rule condition is not met
search cancel

Second Business Rule on Clarity Modern UX, does not gets triggered if the first Business Rule condition is not met

book

Article ID: 377960

calendar_today

Updated On:

Products

Clarity PPM SaaS Clarity PPM On Premise

Issue/Introduction

Issue/Introduction

On a Project Blueprint if there are two separate business rules, respectively acting on the same Child Object, the Rule 2 does not get invoked, if Rule 1 condition is not satisfied. In the blueprint, if the Rule 1 is then disabled, the Rule 2 gets invoked and works as per expectation

 

STEPS TO REPRODUCE:

1 Log onto Clarity Modern UX and create a custom copy of the project blueprint

2 Create the following two rules for this blueprint and then save and publish the blueprint

Rule 1: 

Target Object: Project

Rule Type: View Page

Match Filters: All

Create a filter for the Project attribute, "Work Status = "Complete"

Actions:

Disable Adding Child: Select Risk object

Disable Editing Child: Select Risk object

Disable Deleting Child: Select Risk object

Rule 2:

Target Object: Risk

Rule Type: View Page

Match Filters: All

Create a filter for the Risk attribute, "Category Type = Funding"

Actions:

Disable Deleting Target Object

Reference:

3 Associate this blueprint to a Project 

4 Change the Project's Work Status field to a different value, example: "Requested", so that the Rule 1 condition is not satisfied

5 Navigate to the Risk module of the Project and create an instance having the attribute: Category Type = "Funding", so that Rule 2 condition is satisfied

6 Select the Risk data instance created on the above step and try to delete this instance

 

Expected Results :-

The Delete option should be greyed out and not available for the Risk data instance, since it satisfies Rule 2 and also since Rule 1 is not applicable

Actual Results :-

The Delete button is available and the record can be deleted, the Rule 2 is not considered even if it is valid, when Rule 1 is invalidated

 

Environment

Clarity PPM 16.2.2 and 16.2.3

Cause

DE154186

Resolution

This issue is fixed in Clarity version 16.3.0