Each new form in Upvise is assigned a Form ID, which represents its position within the list of forms for a particular template. This Form ID is automatically incremented but can be manually edited if the "Allow Editing Form ID" option is enabled.

Upvise also supports form sequencing using a combination of Form ID and a user-defined prefix. This feature ensures that each form maintains a unique ID, even when your device is operating without mobile service. Since Upvise works on a disconnected model, it allows users to continue working in low-service areas without interruption, which may result in the ID being the same when the user prefix is not enabled.

To enable sequencing by user prefix, simply turn on the option in the form settings.

Forms > Options > General:

Open

Forms > Options > General

1. Setting Up Form groups

   1. Templates can be organised by the Groups that have been set up in Form Options.

Open

Once your Groups have been established, you can navigate back to form templates and start building templates.

2. Creating form templates

a. To create a new Template, click the + icon in the top menu and provide a name for the template.

b. You will be presented with a Pop-up window where you will input the name of the form, click Save

c. Next, you are presented with a screen where you can add several types of information, beginning with Fields.

Each field type has several options which will prompt for information from the person filling out the form. Most will require a Label, Position, Default Value, and the ability to execute Javascript code when a field is changed. You can also make certain answers mandatory or hidden.

Configure the form, the name, control where the form will be Linked to in the Template info tab.

• Use the Form field type reference guide when building your form templates.

• Reference the template field screen to guide the behaviour of the form fields

Field Types:

• Question - this can be any sort of yes/no/n/a question.

• Combo Box - this field type can be set to a specified list of options or based on several data types in Upvise such as , , , etc.

• Text Box - this expects a certain string of text to be entered as the response.

• Date Box - this expects a date to be provided.

• Photo - this allows a photo to be attached to the form directly from the user’s camera or library (depending on permissions).

• Button - a button for the specified application is provided.

• Label - this displays the label text, useful for organising your form.

• Check Box - provides a box that can be checked by the user, and executes the given Javascript code.

• Section - creates a section for organisation of the form

• Formula - you can provide a Javascript code to perform a calculation.

• Signature - a signature field is added to the form, useful for when sign-offs are required.

The Forms app includes built-in management of Punch Items:

1. Edit the Template Properties in the Forms web app, and check 'has Punch Items'.

2. Add a Question field of type 'Yes - Punch - N/A' to the Form template. Example: Label="Is this issue fixed?", Options="1:Yes|P:Punch|2:N/A"

3. When a user fills in the Form and answers the Question, he has the option to tap 'Punch' if the issue is not fixed. This will automatically create a Punch Item and open a screen where the user can fill in details like: Location, planned Rectification date, owner and description, and attach a Photo.

4. The list of Punch items related to a Form appears in the Punch Items tab in the Form view screen. Close Punch items when the task has been performed.

5. In the Forms web app, a list of all Punch Items created from answering Questions in Forms is accessible from the left pane. Manage Overdue items and view Closed items.

You can control what columns you want displayed in the “All forms” view by modifying the columns in the form template display settings.

See forms/templates/display

When a Form is first created, it is in the Draft State.
The Submit Action on the Form, moves it to the Submitted State.

Templates can be extended with a Workflow, i.e. by defining additional custom States and Actions.

An Action is materialized by a Button in the Form screen. Clicking on the Action button moves the Form to the next State.
A State is defined by a Name, and by the Label of the Action Button which moves it to the next State.

To add a new State:

1. Goto the Edit Template screen in your web account, and open the 'Workflow' tab.

2. Click on + and enter the State Name and Action Button Label.

3. Note that if the State you are creating is the last in the Workflow, the Action Button Label must be left empty, as there is no 'next state' to move to.

Example:
Define a Workflow by adding two new States:
1st State Name = 'Submitted' with Action Button Label = 'Approve'
2nd State Name = 'Approved' with Action Button Label = '' (empty string)
Resulting Workflow: Clicking on Approve moves the Form from Submitted to Approved. Approved is the final State.

Note: the very first State with Rank 0. is the default state named "Draft" with action "Submit". It cannot be modified or deleted.