Classic UI - Unable to save the value if same project is used by two users
search cancel

Classic UI - Unable to save the value if same project is used by two users

book

Article ID: 403602

calendar_today

Updated On:

Products

Clarity PPM On Premise Clarity PPM SaaS

Issue/Introduction

When multiple users simultaneously edit the same project in the Classic UI, changes made by one user may be inadvertently reverted or overwritten when another user saves their modifications without first refreshing their page.

Scenario:

  1. User 1's Action: User 1 opens Project A, changes its 'Status' from 'On-Hold' to 'Approved', saves the project, and refreshes the page to confirm the 'Status' update.
  2. User 2's Concurrent Action: Concurrently, User 2 has the same Project A open in the Classic UI. User 2's view of the project is from before User 1's status update (i.e., 'Status' still shows 'On-Hold'). Without refreshing their page, User 2 modifies the 'Description' field and saves the project.
  3. Observed Behavior: Upon refreshing the page for both User 1 and User 2, the 'Description' field reflects User 2's latest update. However, the 'Status' field reverts to its original value ('On-Hold'), overwriting User 1's prior change.

Environment

All supported versions

Resolution

When a user performs a save operation in the Classic UI, the system is designed to capture and store the complete state of the page, including all displayed data. This is the designed behavior of the Classic UI.

For improved functionality and user experience, we recommend utilizing the New UI. The New UI's broker functionality effectively addresses scenarios where data is updated by displaying a message that prompts the user to refresh the page.