[MGNLFORM-136] As a user i would set up a default value for an input field Created: 04/Oct/12  Updated: 19/May/22  Resolved: 19/May/22

Status: Closed
Project: Magnolia Form Module
Component/s: field
Affects Version/s: None
Fix Version/s: None

Type: Story Priority: Neutral
Reporter: Marvin Kerkhoff Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: next
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to MGNLFORM-141 Freemarker default Value Closed
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:

 Description   

It will be also possible to fill in freemarker code in this default value field in dialog to get GET or POST Variables here.



 Comments   
Comment by Christopher Zimmermann [ 03/Dec/13 ]

Hi Marvin,
So, is this ticket requesting that a site editor/administrator/developer can configure a default value to be displayed in a form?

Also, can you try to clarify: "It will be also possible to fill in freemarker code in this default value field in dialog to get GET or POST Variables here."
So, you'd like the ability to use a snippet of freemarker in this new "Default" field to specify which request variable should be displayed as a default?
So if request was http://mysite.com/form.html?country=japan, then i could put something like ${requestVar['country']} in the "Default" field and the user would see "japan" in that field?

Comment by Marvin Kerkhoff [ 05/Dec/13 ]

Exactly. It should be the same behaviour like here:

http://www.bison-group.com/ueber-uns/karriere/Stellen/bch_Collaborateur-support-informatique-LANDI.html

If you click at the button "Onlinebewerbung" the next form page will be filled with some GET Parameters.

Comment by Christopher Zimmermann [ 05/Dec/13 ]

Thanks for the clarification and use case.
Adding to backlog.

Comment by Roman Kovařík [ 19/May/22 ]

Hello,

This ticket is now marked as closed due to one of the following reasons:

  • A long period of inactivity
  • Uses an old or Beta version of an application, module, or framework that we no longer support
  • The issue is no longer reproducible or has been fixed in later versions

If you are still facing a problem or consider this issue still relevant, please feel free to re-open the ticket and we will reach out to you.

Thank you,
The Magnolia Team

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