...
How the fields of a form must be positioned in the view (= the view / layout).
Where to load and write the form model from / to.
Where to load the /wiki/spaces/DEV/pages/2482176001 from.
What to do, after a form has been submitted.
Title, description, type and other settings of the form.
Here is an example of how such a form config could look like:
...
All form configs inside the form folder will be automatically picked - up and shown in the forms overview of an app. For example, here you can see the form Add person automatically listed:
...
The color of the form icon is used. If not givenspecified, the secondary color is used, which depends on the style settings. By default this is a blue color like this:
...
The color value can be a hex color hexadecimal value, like this:"color": "#FFA500"
...
The PE variable will be interpreted at on the server side and will be replaced by the uuid UUID of the property.
The form handling pipeline can listen to a property.created event on this path then in order to get informed when a new property was created on this path:
...
Width of 900 in horizontal layout item prevents fields to cover all of the available space.
Layout In horizontal orientation, layout items and fields in horizontal orientation, by default, try to span as much width as possible, but with respect to neighbouring fields - behave responsivelyattempt to use maximum width while considering neighboring fields, making them responsive.
Both min-width and max-width can be also used in place of width to reach responsiveness within defined limits.
...
This example would produce a form like this with nested orientationorientations like the one shown below:
...
field
Inside a layout element you can place field elements pointing to field ids (widgets). This element can contain additional attributes like these:
...
It is possible to use request parameters in the form config attributes as placeholders, like this:
| Code Block |
|---|
"input": "$uri:command:workflow.history.tasks?taskId=${request.param.myTaskId}" |
...