Static form

Now we will create our first form page with a very simple form.


images/download/attachments/137309048/11-version-1-modificationdate-1733118368083-api-v2.png


Creating the form profile


  • Create a new profile named "Static_form".

  • Set the mapping type in area "General Data" to "Mapping". Note: The encoding must be set to UTF8 (is the default value).

  • Select the Input Agent "Portal" in phase 1 and select at least one Web Monitor user or Web Monitor role. This defines for whom the form page is visible. Note: This automatically sets the document type to "JSON".

  • We create a node node in phase 3 (matchcode is not necessary) with a field field and generate a 1:1 mapping. You have to set attribute "Show in list" to "Yes" for the field, otherwise no form will be created. Note: In general, a valid form profile must have at least one field with the "Show in list" attribute set in every node. Note: You cannot create fields directly on the top level.

  • Set the profile active and save it.

Your form page


images/download/attachments/137309048/datafox_1_EN-version-1-modificationdate-1688711801572-api-v2.png


(1) Window left: Here you can see all active form profiles. If you select one, the form page created by it appears in the window on the right (2).

Entering data into the form


To enter data into the form, you have to click the plus icon (3).


images/download/attachments/137309048/datafox_3_EN-version-1-modificationdate-1688711801591-api-v2.png


Enter the new value in field "field" (4) and then click "Apply" (5).


images/download/attachments/137309048/datafox_4_EN-version-1-modificationdate-1688711801589-api-v2.png


Your entered value now appears in (6). At this point, the entered data is only stored "locally" in the form and has no effect on the form profile yet.

You can delete the value again via the context menu (7). This can also be suppressed ("_noDelete_").

Note: The " Show in list" attribute, which we have already mentioned above, only refers to the list below. Even if you decide not to show a field in the list (which is not possible here, because at least one field needs to be shown), it will still appear as an input field in (4). To prevent this, you can use the field formatting " _hidden_" .

Sending form data to the profile


(8) Send data: Sends the data in the form to the form profile.

(9) Cancel: Removes all data that has been entered into the form.

The input data of the form profile


Now go to the "Log search" tab.


images/download/attachments/137309048/datafox_5_EN-version-1-modificationdate-1688711801567-api-v2.png


There you will see the profile job (10). If you click on it, another dialogue opens.


images/download/attachments/137309048/datafox_6_EN-version-1-modificationdate-1688711801583-api-v2.png


Via "form.data" (11) you can view the file uploaded to the profile.


images/download/attachments/137309048/datafox_7_EN-version-1-modificationdate-1688711801587-api-v2.png


The value entered in the form field "field" can be seen here in a JSON file.

However, this is only a technical note at this point, as the data is automatically read in for you in the profile by the Input Agent " Portal" and the document type " JSON" .

Example profile


To save you the work and for verification, here is the described profile to import. After importing the profile, do not forget to set it active. Also, you need to create your own Web Monitor user, if you haven't already, and select it (or the role it has) in phase 1.