Change Details

**Feature request** Similar to how users can pre-load form fields using the "query string" property. For example: 1 {{#formlink: form=Foo | query string=Foo[Bar]=SomeValue }} or 2 {{#formlink: form=Foo | userparam=SomeValue }} **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 }}} 1 {{{field | Members | input type=combobox | values from category=Type[Engineers] }}} or 2 {{{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, we 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.

**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 }} ``` or ``` {{#formlink: form=Foo | userparam=SomeValue }} ``` **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, we 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.

**Feature request** Similar to how users can pre-load form fields using the "query string" property. For example: ``` 1 {{#formlink: form=Foo | query string=Foo[Bar]=SomeValue }} ``` or ``` 2 {{#formlink: form=Foo | userparam=SomeValue }} ``` **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 ``` 1 {{{field | Members | input type=combobox | values from category=Type[Engineers] }}} ``` or ``` 2 {{{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, we 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.