Dynamic form
General context
Don't be discouraged. It only looks complicated at first glance. The basic idea is that the data profile gets data via the form profile from the form, changes it and then sends it back again. It is therefore only an addition to the manual data entry in the form. In the end, the data is sent to the form profile as in our previous example .
On our previous form pages, we transferred data via forms. We also showed how to define default values and selection values for fields.
Now we want to show how you can return values to the form in reaction to input values in the form. For this we use our previous example as a basis. Instead of entering an order number and item numbers and sending them to the form profile, we now want to develop a simple search functionality. We enter an order number and want the form to be filled with all item numbers for this order number.
On a technical level, this is implemented by assigning an additional, so-called data profile to a node in the form profile . This data profile can be triggered in various ways (initially when opening the form, when values in form fields are changed or simply by pressing a button).
So we enter an order number in the form and because of this value change or because we press a button we want the data profile to insert the item numbers for this order number in the form.
Note: The two diagrams are simplified to show the data sources of the form. Technically, the data profile returns its output data to the form profile (in which it is included) and the form profile builds the form page (with the integrated dynamic data).
Creating/Integrating/Triggering the data profile
See sections Creating/Integrating/Triggering the data profile and Dynamic selection values.
Further notes on data evaluation
Evaluating value changes
If you want to evaluate if rows in a data list have been created, changed or deleted, you can create an additional field named " row_change_kind" with value " _hidden_" for the field attribute "DataCockpit control" in the associated node . This field then automatically receives one of the values " created" , " updated" or " deleted" or is empty and thus shows the way the row has been modified . Important note: If you use multiple "row_change_kind" fields, they get a field name suffix (e.g. "row_change_kind-1"), because field names must be unique. In this case, please use a match code with condition "Equals" and the value "row_change_kind" on all these fields.
Passing on values from outside the data node
It is possible to pass the current value of a form field located outside the node that has the data profile assigned to it to the data profile. To do this, set the value "_keepInSession_" in attribute "DataCockpit control" of this field . See examples .