[MGNLUI-3001] Tree/View gets out of sync if worked on by an asynchrously running action Created: 13/Jun/14  Updated: 11/Nov/16

Status: Open
Project: Magnolia UI
Component/s: pages app, tree/list
Affects Version/s: 5.3
Fix Version/s: 5.3.x

Type: Bug Priority: Critical
Reporter: Andreas Weder Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
supersession
supersedes MGNLUI-2966 Exception when working with the page ... Closed
supersedes MGNLUI-2999 ArrayIndexOutOfBoundsException when w... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled

 Description   

IN MGNLUI-2966, we've implemented a fix that handles many cases where an asynchronously running action changes a tree without notifying the view. Basically, we track the location changes and if the browser sub-app sees that the new location is its own, it refreshes itself.

However, this fix doesn't work in cases where:

  • there is no location change (e.g. an asynchronously running delete action not using work flow)
  • the change occurs in a different session (e.g. another user approves the work flow)

There are several ways to fix this. In discussions, it seems that a combination of observation and push support would help, but also low-level conventions such as requiring an asynchronously running action to call a method once it completes, which in turn notifies apps, could be part of a solution.


Generated at Mon Feb 12 09:02:15 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.