Interact with the user via online result processing.
General. Settings like header, description, buttons text, etc.
Fields. Configuring inputs for form fields.
Result. On-line submission processing.
API-endpoint. That defines the fields available for writing.
Form description (you can use Markdown here);
Submit button text (
Submit by default);
Re-submit button text (
Submit again by default);
Labels or placeholders. Switches the view of inputs—field names can be displayed above the field or as a placeholder;
Form max width in pixels.
You can display sections as sections or just invisible groups (useful for conditional sections):
Visibility of a section can depend on the user's choice of fields values above
If the option Quick search is ON (it is by default), objects from the linked structure will be displayed as options in selects (the visible name will be displayed, if there is no such, the
id field will be displayed). Max quantity of options is 1000.
If you marked field as a hidden one (that is possible for string and link fields), they will be get from URL query params. That looks like (fieldOne and fieldTwo are hidden fields):
Here we will get in the submitted object:
You can include hidden field for User ID, which will be filled automatically if the user is logged in.
First, you need to have a field type of link to
WebUser data structure available for posing in your API-endpoint.
Find section in Personalisation section in Fields settings:
The user's ID will be posted in this field automatically. If the user isn't logged in, the field will be empty.
If you want to edit existing object plus to creating new you can turn on that option in Fields settings section:
There are two ways to get
id of the object to edit:
From query param
@editObject=_id_ form URL, where
_id_ is id of the object you would like to edit.
id as an
id of object to edit. You could edit App user (
WebUser) object that way. Also any other object with such an
Submitted object can be processed in sync scenario, and then the result is to be displayed to the user. There three fields of the object for interpreting the result of object processing:
Result: success/fail. Boolean field. If the field is
true, the Success block is showed. If that field is
false, the error block is showed.
Result message title. String field. The title of the result block.
Result message text. String field. The text of the result block.