[MGNLUI-6671] Extend the UploadField with a small Download icon Created: 12/Nov/15  Updated: 22/Jun/21  Resolved: 21/May/21

Status: Closed
Project: Magnolia UI
Component/s: framework
Affects Version/s: None
Fix Version/s: 6.2.9

Type: Improvement Priority: Neutral
Reporter: Marvin Kerkhoff Assignee: Jan Haderka
Resolution: Done Votes: 0
Labels: ux-improvement-selected
Remaining Estimate: Not Specified
Time Spent: 0.1h
Original Estimate: Not Specified

Attachments: PNG File 1 Action popup.dialog.png     PNG File 47_Actions popup_Dialog.png     PNG File Screenshot_2021-04-26_at_10_25_06.png    
Issue Links:
Relates
Template:
Acceptance criteria:
Empty
Task DoD:
[X]* Doc/release notes changes? Comment present?
[X]* Downstream builds green?
[X]* Solution information and context easily available?
[X]* Tests
[X]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Release notes required:
Yes
Date of First Response:
Epic Link: UX improvements
Sprint: UI FW 28, UI FW 29
Story Points: 3

 Description   

If you use a lot of content apps which have own upload fields like the contact app. You need an easy way to download the images. One good and generic way would be if you add a small download icon beside the delete icon. It would be much better then everytime make a own download action like you have done it in the assets app.



 Comments   
Comment by Andreas Weder [ 08/Dec/15 ]

Yes, I agree with you in principle.

The plan is to rework that field both to improve its usability and its visual appearance. We also have to make sure actions like these are properly guarded by permissions. I'd like us to take a quick step back first and have a look at the entire picture before we're going to add new stuff to the field - we've hit too many bumps in the past.

Comment by Andreas Weder [ 08/Dec/15 ]

I've attached a mockup and early visual design that illustrate some of the ideas around that. One is to differentiate between what the field does - it allows to upload a file/an image in the context of a form - from controls that allow you to directly work with the content that was uploaded, possibly even in-place (i.e. an "edit" action opens the image editor without switching apps).

This is not as far off as it may seem, but it requires a bit more thought still before we attempt to refactor the component.

Comment by Jan Haderka [ 26/Apr/21 ]

Latest proposed visual: 

 

avongunten perhaps something you might want to consider for your list too.

Comment by Anja von Gunten [ 28/Apr/21 ]

yes added it it to the list, nice quick win. thanks

Comment by Miroslav Remias [ 28/Apr/21 ]

avongunten, do we know what is the use case for this "download" need? Also, does this happen frequently?

Comment by Marvin Kerkhoff [ 28/Apr/21 ]

If you you edit a PDF you can't see the PDF itself in the dialog. So downloading is the only option. But to do this, you actualy need to go outside of the editing dialog and select it in the browser app. It's a comfort feature.

Comment by Miroslav Remias [ 28/Apr/21 ]

Thank you marvink2, makes sense. Untimately, your goal is not to download the PDF, but to view it, right?

Comment by Marvin Kerkhoff [ 28/Apr/21 ]

No Miro, it's a generic way to get assets which you uploaded before, without adding additional effort. If you want to add a upload field somewhere else in the admincentral, the only option to download it is to make a seperate download action inside the browser app or to extend the field on your own. In my opinion everywhere where i upload something there should be a way to download it. Because that's where users search first. 

Comment by Roman Kovařík [ 25/May/21 ]

For release notes:

Download button added to upload fields.

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