[MGNLUI-3841] Create a simple configuration sub-app via configuration Created: 07/Apr/16  Updated: 05/Mar/21  Resolved: 05/Mar/21

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

Type: New Feature Priority: Neutral
Reporter: Christopher Zimmermann Assignee: Unassigned
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File tool-app-1.yaml    
Issue Links:
dependency
depends upon MGNLUI-3999 Provide tools subapps with configured... Closed
duplicate
relation
is related to MGNLUI-4284 FormTool should be able to edit a JCR... Closed
Template:
Acceptance criteria:
Empty
Date of First Response:

 Description   

Just like a standard "content app" can be created with configuration alone, it should be possible to create a standard "simple configuration app" with configuration alone.

This is another common use case for apps which we could make much easier.
Being configurable would make them easy to implement by "light developers", ie non-java devs or projects using light modules.

As a user, if I opened such an app, the config subapp would be displayed.
The config subapp would look something like the mail app, (or a typical DetailSubApp) and would simply display a dialog and its actions.

It could be configured just like a standard DetailSubApp.
Developer could configure the workspace and node where the values from the form should be saved as properties. (Perhaps the existing contentConnector works for this.)

An additional benefit to someone using a standard magnolia dialog rather than a custom vaadin form is that they could take advantage of the validation, the helptext, and the saving of the data to jcr that Magnolia provides.



 Comments   
Comment by Christopher Zimmermann [ 28/Sep/16 ]

This appears to be pretty straightforward based on the work completed in https://jira.magnolia-cms.com/browse/MGNLUI-3999

I guess one would need a new version of FormToolDefinition which would accept a workspace and rootpath in order to specify where the results of the form should be saved, and probably a new action (related to SaveFormActionDefinition) to complete the save.

A simple tool app is attached "tool-app-1.yaml" - maybe its helpful as a starting point.

Comment by Roman Kovařík [ 05/Mar/21 ]

Closing this as are moving away from JCR config and from configuration from inside of admincentral in general.

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