Uploaded image for project: 'Magnolia UI'
  1. Magnolia UI
  2. MGNLUI-3001

Tree/View gets out of sync if worked on by an asynchrously running action

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open
    • Priority: Critical
    • Resolution: Unresolved
    • Affects Version/s: 5.3
    • Fix Version/s: 5.3.x
    • Component/s: pages app, tree/list
    • Labels:
      None

      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.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              weder Andreas Weder
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated: