[MGNLUI-1942] Provide a general way/recommendation how to handle multiple items of different types Created: 22/Aug/13 Updated: 09/Mar/21 Resolved: 09/Mar/21 |
|
| Status: | Closed |
| Project: | Magnolia UI |
| Component/s: | actionbar, framework |
| Affects Version/s: | 5.1 |
| Fix Version/s: | None |
| Type: | Task | Priority: | Neutral |
| Reporter: | Jozef Chocholacek | Assignee: | Unassigned |
| Resolution: | Obsolete | Votes: | 0 |
| Labels: | ui-ux-impr | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| Acceptance criteria: |
Empty
|
||||||||
| Task DoR: |
Empty
|
||||||||
| Date of First Response: | |||||||||
| Description |
|
During the work on the http://wiki.magnolia-cms.com/display/DEV/Concept+-+Multi-item+Actions for 5.1 release, the issue with different delete command for asset and folder has jumped out in the DAM module. In general, the problem is that a different action/command is called for different node type, although doing basically the same thing (at least from the user's point of view) - in this case marking the asset/folder for deletion. The problem has been "solved" by not including the "Delete items" action/button into the actionbar section for the multiple node types. But this is not ideal solution from the user's point of view, as in all the other apps the user can delete multiple items, even of different type (e.g. folders and contacts in the Contacts app, content nodes and properties in the Configuration app, etc.). The solution would be providing a "decision-making" action, that could be configured to call different "sub-action" for different node types. |
| Comments |
| Comment by Jozef Chocholacek [ 22/Aug/13 ] |
|
Another possible future use-case: a different approval workflow for different node type, e.g. a simple "4-eyes" workflow for images, but an approval from legal department required for PDF documents. |
| Comment by Andreas Weder [ 22/Aug/13 ] |
|
From a user's perspective, there's no clear distinction between deleting a folder and deleting a single item. Both actions delete, thus you would expect that you can execute them both with a single action. Thus from this standpoint, whether we unify both actions in a single one with added intelligence or have a "decision-making" action in front, doesn't really matter. As long as there's a semantic "delete" operation, which is capable of doing both, we're fine. In your comment, which describes a scenario where publishing two items leads to two different work flows with mostly different behavior, you actually touch on, what I would call, the advanced version of batch actions. We have to develop a way to signal on which item you currently work on. In addition, it would be nice to have batch changes in the future as well: change the template of several pages to a single, different one; edit the location of several contacts from "Bsel" to "Basel". We know that from JIRA. It's just a great way to work and fix many items at once. |