Static form
Now we will create our first form page with a very simple form.
Creating the form profile
Create a new profile named "Static_form".
Set the mapping type in area "Main settings" 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 user . 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
(1) Window left: Here you can see all active portals based on form profiles. Important note: You can remove an entry here by either setting the profile to inactive or by deactivating the portal under "Orchestration/Portals". Please note that you must select the "Is bound to profile" checkbox there for the portal to be displayed. In addition, with both options, it may be necessary to select the "Reload main menu" option in the user menu afterwards to ensure that the display is updated.
(2) If you select a portal, the form page created by it appears in the window on the right.
Entering data into the form
(3) To enter data into the form, you have to click the plus icon.
(4) Enter the new value in field "field" (4).
Your entered value now appears in (5). 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 (6). 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
(7) Send data: Sends the data in the form to the form profile.
The input data of the form profile
Now go to "Search logs" on the left.
There you will see the profile job (8). If you click on it, another dialogue opens.
Via (9) you can view the file uploaded to the profile.
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. You must also select your own user in phase 1 in the Input Agent so that the portal is displayed to you.