6.1.1 The main Form element's Other tab

The Other tab of the main Form element contains many important settings that enhance the way the form works. The options are explained in detail below.

Language and Country

These options decide the national settings to be used in the Zegeba web app in your browser, such as spelling, decimal sign, currency etc.

Word Break (not PDF)

This option decides what type of word breaks you want in text entered in a form open in the browser. The default is “Automatic” – a ‘gentle’ form of breaking words. You can also select “Anywhere in a word” or “Never break a word”.

Min/Max view width

These widths controls how much a form will change size when viewed on a phone screen. Zegeba forms are responsive, they will change the way they look on a phone or tablet to fit all parts of the form in one screen, so some elements may look very small. If you put Min view width to 700, the form will not go below 700 pixels in width, but rather show a scrollbar that you must use to see the entire form.

Form Group ID Variable / Form Id Variable

“Form Group” is the internal Zegeba name for a folder. These two properties are created for the numeric IDs of the form and the folder that the form is placed in. Form designs created before Zegeba v 4.0 will show the automatically generated ID numbers here. From v 4.0 onwards, IDs are not numbered that way and placed here, but you may enter your own numbers to be used as numeric IDs. These numbers will be displayed by the description formulas {§groupId} and {§formId}.

On load action

In this field you can enter an action to be executed when the user opens the form for data capture. This can be actions such as goTo, setValue, setOption, etc., as described in Designing: 6.6 Links / Go to / Actions.

Hide Remark functionality (star next to input fields)

When there is a star to the left of an input element, you can press this to get a screen where you can add remarks of the types Follow up, Incomplete or Note. The remark will be displayed right below the input element, but it will not be printed on the PDF nor be transferred to Power BI or other types of software integrated with Zegeba.

The Hide Remark functionality is by default switched Off for all elements. To use the Remark functionality you must turn this general property On and then then turn it Off for individual elements who should not have this property.

Hide + and – buttons in Decimal and Number elements

Select this to remove the + and – buttons on all Decimal and Number elements. When this option is selected you cannot turn the buttons On for individual Decimal and Number elements.

Allow upload without captured multimedia

If the form will be used under difficult conditions, for instance with international lines of poor quality, select to send the data capture without captured multimedia that require good bandwidth to be uploaded.

Flag Signature if data has been changed

If a signature set in e.g. the first version of a report, end data in the report is changed in later edits, this will be flagged.

Hide ‘Do not Send’ / ‘Send Unfinished’ / ‘Lock’ state

Select these options if you do not want users to have access to these form states on the Summary page.

Unfinished forms should not be sent

This ensures that all elements are filled in before the PDF reports are mailed.

Reapply rules, validations and calculations when loading existing data

Select this to ensure that everything is recalculated when data is loaded for instance from a task template.

Hide navigation bar at the bottom

If you prefer to use customized Link buttons on the form pages to navigate from page to page, you can select this to get rid of the page bar at the bottom of the form screen. Note that you will then not be able to access the Summary page, so you have to place Action elements as [Save] buttons etc. on the form pages instead.

Hide Summary page

When this is checked, user’s will not get the button to go to his page on the Navigation bar at the bottom. You must then create Action elements or Link buttons on the form pages to ensure that people are able to Save and Close, or Cancel, the form capture.

Show Audit Info

When this property is switched on, form elements will during data capture show the username, date and/or time when users fill them in. This is handy for instance when several people work on the same form – to track who entered what. You can set the audit for individual elements in a form or for all at once in the main form element.

Check Show Audit Info and then select the way you wish to show the user info:

In the example shown below, we have selected to include Username and Date & Time.

You can exclude Audit Info from being printed on the PDF, either for the entire form or for individual elements. This option can be found in the PDF tab.

Enable Email Notifications

This option is described in detail in Designing: 8.2 Automatic email notifications with PDF reports and form links.

Configure Form states

The standard Zegeba setup provides the states of form completion pictured above. Users access these from the Summary page by pressing [Set Form State] after a capture or by pressing a [Set Form State] Action button inside the form (see Designing: 4.1 List of elements. In Configure form states you can enter code to change these states to the ones you want to use in your workflow. Press here to open a separate window with an example of a JSON code for 3 form states. You can enter as many form states as you wish using these parameters:

“color”: type an ordinary color name here. The color will be displayed as small circle next to the report in the Zegeba app.
“state”: the one-word, lower-case name you type here will be used as the internal name. If you must use more words, use an underscore between them, such as “send_to_manager”. You can only use regular letters and numbers in the name. This state name will also be displayed in the list in the menu option Data Views, so it should resemble the display name listed in the line below it.
“displayName”: type any text string in any language. It will be shown in the form’s Summary Page as the “official” form state.
“progress”: you can specify a percentage value here to indicate the progress of work on a form report. The percentage will be appended to the name of the form state and listed in a separate, sortable column in Data Views.

“action”: this is used when a specific action should take place in the app when the state is selected. The actions available are “readOnly” and “locked”:
“action:” “readOnly” will allow the report to be viewed and read, but not edited.
“action:” “locked” will lock the form so it cannot be opened in the app.

These action states have no effect in the Dashboard, but in the app they will be shown with an eye icon (readOnly) or a lock icon (locked) on the reports:

Prefill form with data

This option is used when you want to prefill a form before the user starts entering data in it.

Press here to open a separate window with the JSON code for a prefill of two fields. You can copy the sections between the commas to enter more prefill fields in “Prefill form with data”.

From Zegeba v 4.4 you can also prefill a form with data entered for the current user in the Dashboard’s Users screen. Press here to see the code for prefill of all user fields, such as Username, email, etc. By using this kind of prefill, the current user does not have to enter their own name, email, etc. into each report they make.

Contact Zegeba Support if you want more information on this.

Enable Server Fill Mapping

This property is used by Zegeba staff to e.g. set a sequence number for each report as it is synced to the server.

Enable form state mapping rule

The answer to an element can set the form’s state. In the example below we have a Single Select element with the option IDs option_1, option_2, option_3. If the user selects Option 1, the form state will be set to default. Option 2 selected will set from state incomplete. etc. The state name to be used is the internal name you choose, as mentioned in the “Form state” section above. You can use as many options as you want in this rule, but only for one element in the form.

You can copy the code shown in the picture here, and change it to suit the settings in your form.

Enable exposed answer mapping

If your company has started using “custom task views“, you can create special table views of the data entered in a task. When this box is checked, a small pane for entering JSON code appears. Zegeba Support will supply this code. In addition, you must for each element in the form that you wish to see in the view, select “Expose element data” in their Other tabs. Release Notes: Zegeba v 4.4 has an illustration of a custom task view. Please contact Zegeba Support for more information on this feature.

Automatically prefill any sub element with matching data from the Task/Context

This option was introduced in Zegeba v 4.6, and makes prefill from tasks to forms much simpler to set up. When the option is checked, the system will look for task meta data that have IDs identical to element IDs in the form, and prefill the form with the task meta data. You can also – or instead – set prefill on individual elements, on their Other Properties tabs. See Designing: 4.2.6 Other tab for more information on that.