Page MenuHomePhabricator

Pass a page defined value into a form from formlink and autoedit parser functions
Closed, InvalidPublicFeature

Description

Feature request
Similar to how users can pre-load form fields using the "query string" property.

For example:

{{#formlink: form=Foo | query string=Foo[Bar]=SomeValue }}

the following capability is requested

{{#formlink: form=Foo | userparam=SomeValue }}

ref: https://www.semantic-mediawiki.org/wiki/Help:Plainlist_format/parameter_userparam

Use cases

One might also wish to have the form rendered differently based on some situational logic. Based on the example above, one could imagine the Form:Org containing some logic like:

{{{field | Type | input type=text | restricted | mandatory }}}

with

{{{field | Members | input type=combobox | values from category=Type[Engineers] }}}

or

{{{field | Members | input type=combobox | values from category=userparam }}}

where Type was defined when the page was first created and is never changed.. but all subsequent form edits should be tailored based on the value of Type

Benefits

Presently, PF requires form creators to autocomplete from one entity that must be selected for all use cases, in this example, our current approach is to use "values from category=User" which results in the user having to sift through 100 (potentially 1,000s) of users many of which are guaranteed to not be selected. The goal of this feature is to provide users with general purpose forms that can accommodate situational conditions (like autocomplete) for a set of data determined either in the form (via fields) or from the page "linking to" the form.

Event Timeline

Revansx updated the task description. (Show Details)
Yaron_Koren added a subscriber: Yaron_Koren.

I believe this is doable already, via the UrlGetParameters extension. I'm marking this as "Invalid", although feel free to re-open.

Ok. Thanks for reviewing this and pointing out the UrlGetParameters extension [1] as a way to accomplish this. I agree that that is a great solution to this use case. Hopefully this ticket will help someone else too.

[1] https://www.mediawiki.org/wiki/Extension:UrlGetParameters