Blueprint Rule Shows enabled for Invalid Rules
search cancel

Blueprint Rule Shows enabled for Invalid Rules

book

Article ID: 424804

calendar_today

Updated On:

Products

Clarity PPM On Premise Clarity PPM SaaS

Issue/Introduction

Some invalid business rules do not get deactivated when editing the blueprint.
 
STEPS TO REPRODUCE
  1. Classic PPM > Administration > Studio > Objects > Project object
  2. Create a new string attribute called: mystring
  3. Classic PPM > Administration > Data Administration > Processes
  4. Create a new process 'myprocess' based on the project object and validate it
  5. MUX > Administration > Blueprints
  6. Create a project blueprint.
  7. On the Actions tab > Add a process > myprocess and Enable it
  8. On the Rules tab > Create two rules.
    • Hide attribute Rule
    • Rule Type: View Page
    • Condition: If Access Groups = Basic
    • Action: Hide Attribute: mystring
    • Hide process Rule
    • Rule Type: View Page
    • Condition: If Access Groups = Basic
    • Action: Hide Actions: myprocess
  9. Enable both rules and publish the blueprint
  10. Classic PPM > Administration > Studio > Objects > Project object > Deactivate the mystring attribute
  11. On the Blueprint Actions tab disable the myprocess action
  12. Blueprint > Rules tab > Click on Edit 
  13. Notice the Hide attribute rule got disabled. The Hide Process rule is still enabled
Expected Results: All invalid rules should be deactivated
Actual Results: Some rules do not get deactivated even if invalid

Environment

Clarity 16.3.X, 16.4.X

Cause

This is caused by DE181001

Resolution

Within the current design, when you deactivate an attribute in Studio > Objects, it actually attempts to deactivate the rules where the attribute is present.

In Blueprint --> Actions, if you disable a process action, it is not until you drill down into the rule, that the UI detects that it is no longer valid. The UI will then correct the invalid data and will set the rule to disabled when saving. The user will see a banner indicating this.

New feature work will be needed to implement a different approach. The defect has been converted to a user story to work on a new feature that addressees this.