...
If this attribute is missing, "hidden": false
is used as a default.
schema
A PIPEFORCE URI pointing to the location where to load the List Schema from.
...
Code Block |
---|
{ "type": "object", "properties": { "firstName": { "type": "string", "title": "First Name", "description": "The first name of the person." }, "lastName": { "type": "string", "title": "Last Name", "description": "The last name of the person." }, "age": { "type": "number", "title": "Age", "description": "The age of the person." }, "gender": { "type": "string", "title": "Gender", "description": "The gender of the person.", "enum": [ "male", "female", "neutral" ] }, "birthDate": { "type": "string", "format": "date", "title": "Date of birth", "description": "The date of birth of the person." } } } |
input
A PIPEFORCE URI pointing to the location where to load the input model from (must be a JSON array whereas each item represents a single row in the table).
...
Code Block | ||
---|---|---|
| ||
{
"id": "person",
"title": "person",
"public": false,
"description": "",
"schema": "$uri:property:global/app/io.pipeforce.t169/schema/person",
"output": "$uri:property:global/app/io.pipeforce.t169/data/person/#{property.uuid}",
} |
Additionally, we need to change this so that the fields uuid
, readPath
and writePath
are not shown in this form. To do so, add the layout
section to this Form Config as shown in this example:
Code Block | ||
---|---|---|
| ||
{ "id": "person", "title": "person", "public": false, "description": "", "schema": "$uri:property:global/app/io.pipeforce.t169/schema/person", "output": "$uri:property:global/app/io.pipeforce.t169/data/person/#{property.uuid}", "layout":{ "items":[ {"field": "firstName"}, {"field": "lastName"}, {"field": "birthDate"}, {"field": "age"}, {"field": "gender"} ] } } |
...
Done. If you open your list and click a row, the form will load the current row data by using the PIPEFORCE URI of column readPath
and shows this data in a form defined by the form config. On SUBMIT it will use the PIPEFORCE URI of column writePath
to store changed data back to the backend.
Internationalization (i18n)
Text elements of the list can also be internationalized (= translated to different languages). See here for more details, how this works: Internationalization (i18n).