[MAGNOLIA-6246] Send and show fewer messages when deleting multiple items at once Created: 05/Jun/15 Updated: 11/Mar/21 |
|
| Status: | Open |
| Project: | Magnolia |
| Component/s: | admininterface |
| Affects Version/s: | 5.4.8 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major |
| Reporter: | Jozef Chocholacek | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | development, messages, ux | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||
| Issue Links: |
|
||||||||
| 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)
|
||||||||
| Epic Link: | Redesign action capabilities | ||||||||
| Story Points: | 8 | ||||||||
| Description |
|
When you delete multiple items, you will get a confirmation message in Pulse (confirming that the long-running "delete" action has completed successfully) and an "info" banner (announcing this new Pulse message) for every single node you attempt to delete. This is both disturbing and time consuming to acknowledge. Example: Delete a config tree of 50 nodes. You get 50 banners laid over each other at the bottom of AdminCentral and 50 messages in Pulse. We should show fewer message banners and Pulse messages when batch-deleting items. How to show less messagesWhat we want is to aggregate multiple messages into a single one. When aggregating messages, we have to both provide an overview of a series of messages and at the same time make sure users don't miss anything important or extraordinary. It's not enough to just show a single message that stands in for dozens of messages, especially when these messages are of a different type. A typical design pattern to solve such a problem is:
Typically, confirmations and info messages are treated differently than warnings and errors. While the former are aggregated as described above, (severe) errors are still displayed one by one in order to be able to show the problem in detail. I thus suggest we start by only aggregating delete "info" (confirmation) messages, but continue to show all warnings and errors using one message for each. ExampleA user attempts to delete 19 items in the Configuration app. Magnolia detects that the deletion will take some time and sends the action to the background.
Instead, we should get:
Advanced exampleA user attempts to publish 25 items at once in a content app. The action is again sent to the background. Of these 25 publications, let's assume that 19 work fine, 4 raise a warning, 2 fail due to a severe error. Here's what we could get in such a case. I'm assuming that the aggregation time period is 5 seconds:
We thus get a total of 9 Pulse messages and message banners:
|