Sometimes you need some data, which is not shown on the screen. In most cases this will be an internal ID that you will not display, however you need it to lookup for the real data.
Example:
ID for a supplier isn't shown, but the name of the supplier must appear. In that case the ID is hidden, and the supplier name is shown. In the database you need to save the ID.
Name of supplier is shown, but the ID is a hidden element and not displayed.
{
"display": "",
"tooltip": "",
"fieldname": "nummer",
"length": 6,
"inputtype": "hidden_int",
"data": {
"endpoint": "\/tabfiles\/lever",
"buttons": [],
"file": "suppliers",
"fieldname": "id",
"pagetype": "tabgrid",
"pagesize": "",
"hidefilter": false,
"onclick": {
"endpoint": "",
"pagetype": "",
"pagesize": "",
"hidefilter": false,
"buttons": []}
},
"block": 1,
"newline": false,
"labelwidth": 0,
"fieldwidth": 0
},
inputtype: hidden_int to define this as a hidden integer. You can also use hidden_text, hidden_float, ... In most cases it will be an ID that you want to be as a hidden.
data: the data object defines which data must be saved in this fieldname.
endpoint: the endpoint that will be used to get the data.
file: this name will be used to define in which table the data can be found.
fieldname: the fieldname to copy the data from.
As soon as the endpoint to search for a supplier with thefilename suppliers is used, BOA will look for the value in the fieldname ID, and will save that data into the fieldname nummer.
This way you can keep related info into variables, and when a request PUT or POST request is send to an endpoint, the data can be saved into the database.
