[MGNLUI-6806] Changing template does not force mandatory properties to be filled in. Created: 04/Aug/21  Updated: 12/Aug/21

Status: Open
Project: Magnolia UI
Component/s: content app
Affects Version/s: 6.2.6
Fix Version/s: None

Type: Improvement Priority: Neutral
Reporter: Lee Salter Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: ux-improvement
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

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)
Date of First Response:
Epic Link: UX improvements

 Description   

Steps to reproduce

  1. Log in to Magnolia author as superuser 
  2.  Open the pages app and create a new page using the Basic Template.
  3. Save changes
  4. Click to select the page and when highlighted, click "Change Template"
  5. Select a template that includes mandatory fields
  6. Save
  7. Notice that the template is immediately changed and the author is not prompted to fill in the mandatory fields on the new templates properties dialog.

.. Logs, screenshots, gifs...

Expected results

The author is immediately presented with the page properties dialog for the chosen template and is alerted to the mandatory fields. Cancelling out of this dialog should not change the template but revert to the original one.

Actual results

The template is changed immediately without any warning given to the author that there are mandatory fields that need to be filled in.

Workaround

Manually open the new templates properties to fill the fields in.

Development notes



 Comments   
Comment by Simon Lutz [ 05/Aug/21 ]

Thanks for reporting this issue, lsalter. I have changed it from a bug to an improvement request. There is no straight-forward solution to it and it raises some UX concerns.

  • Possibly configured autogeneration won't be triggered for the new template
  • Properties of the old template are left in JCR
  • Cancelling out the dialog and reverting back to the previous template is not trivial and needs a thorough UX pattern to not confuse users
Comment by Lee Salter [ 12/Aug/21 ]

Thanks for the update Simon. We can obviously workaround it, but look forward to seeing this implemented in a future version.

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