...
| Code Block | ||
|---|---|---|
| ||
{
"title": "Add person",
"description": "Add a new person",
"hidden": false,
"schema": "$uri:property:global/app/tld.domain.myapp/object/person/v1/schema",
"input":"$uri:property:global/app/tld.domain.myapp/object/person/v1/instance/67b07f3c-e006-4bec-a790-ef25b9fe97df",
"output": "global/app/tld.domain.myapp/object/person/v1/instance/${vars.property.uuid}",
"layout": {
"orientation": "vertical",
"items": [
{
"orientation": "horizontal",
"items": [
{
"field": "firstName"
},
{
"field": "lastName"
}]
},
{
"field": "age"
},
{
"field": "gender"
},
{
"field": "birthDate"
}
]
}
} |
...
Another example:
"color": "red-8"
...
hidden
This optional attribute defines whether the form should be shown as tile inside the app ("hidden": false) or not ("hidden": true).
The form can be still loaded by its URL if required and used embedded in lists or workflows.
If this attribute is missing, "hidden": false is used as a default.
schema
The schema attribute defines a PIPEFORCE URI which is called in order to retrieve the Form schema for this form.
...
Inside a layout element you can place field elements pointing to field ids (widgets). This element can contain additional attributes like these:
hidden
If set to true, the widget is not shown in the form, but the value from the input is sent to the backend on submit. Example:
...