Process driven data update not notfiying user about the outdated data

Products

• Clarity PPM On Premise
• Clarity PPM SaaS

Issue/Introduction

In a Clarity environment where PPMBroker is successfully deployed, users are not receiving page refresh notifications when data changes are driven by a process, even if they are subscribed to the relevant page.

Consider this example:

• User A creates an auto-start process to update a project's "Project Description" field to "LIVE" if it's not already "LIVE."
• User B is subscribed to the project's properties page.
• User B manually updates the "Project Description" field to a value other than "LIVE."
• The process is then initiated and changes the "Project Description" back to "LIVE."

Expected behavior: User B gets the page refresh notification as per Notify users about outdated Data 

Actual behavior: User B does not get the page refresh notification banner

Environment

Clarity 16.3.2

Cause

By design, Clarity handles process-driven data updates in a way that does not display a page refresh banner to the user who initiated the data update (even if that update then triggered a process).

Resolution

Clarity does not send a page refresh notification banner to the user who initiated the update, even when that update triggers a process that further modifies the data.

Here's a breakdown of the example provided:

1. User B manually updates the "Description" field to a value that is not "LIVE." This initial update is broadcast to all subscribed users except User B, as User B made the change and is presumed to know the data has been updated.
2. When User B's update to the "Description" field starts a process, and that process subsequently updates the "Description" field to "LIVE," this event is also broadcast to all subscribed users except the user who initiated the process, which is User B.

It's important to understand that the system's behavior is based on who INITIATED the process, not who CREATED it.

Therefore, if User A (who created the process) were viewing the project's properties page, User A would receive the page refresh banner because the data was updated by a process initiated by User B.