MUX Notifications not triggered when conditions fulfilled by aprocess

Products

• Clarity PPM SaaS
• Clarity PPM On Premise

Issue/Introduction

The MUX notifications are not triggered when the raise conditions are fulfilled by a process.

Steps to Reproduce: 

1. Create a complex notification
2. Send Conditions 
   • Target attribute = Active
   • If target attribute is equal to No
   • Pick yourself for the notification
3. Create a Process
   • Primary Object - Project
   • On Demand start
   • Start step add a System Action step
   • Action = Set Active
   • Active = No
4. Create a blueprint in MUX and add this process
5. Associate a project to this blueprint
6. Open active project
7. Manually make the project inactive
8. You will receive a notification
9. Make the project active
10. Run the newly created process
11. The project will become inactive

Expected Results: A notification is sent

Actual Results: The user never receives a notification.

Environment

Clarity 16.3 and higher

Cause

This was analyzed through DE171510

Resolution

After sustaining engineering analysis it was determined this is working as designed.

The General Notifications functionality uses business rules under the covers. To be specific, the notification condition is implemented as a business rule behind the scene. The Business rules only gets evaluated when the updates are happening from modern UX but not by other means like classic/XOG/Processes. 

You might want to use a REST API call to trigger the notification.

In order to do so you need to include "x-api-rule-engine": "ui" in the header of your call. Create Business Rules for Attribute Updates