Create a Form
You create a Form by clicking 'New' in the top right corner. Once clicked, a new window will appear, asking you to fill in a name of the new form. Please note that the name must be unique; it cannot be one previously used for another form.
Form Designer overview
On the form overview, you have access to a wide selection of functionality, which is briefly covered below:
Layout - Where pages, questions and logic are setup
Fields - Maintain fields related to the form. Fields are used to store data which can be populated by external systems or by logic inside the form
Settings - Various settings for the Form, for instance updating the name or allowing self- initiation of the form.
Versions - Create new versions of the form, or load previous versions.
Initialization - Get code samples and URLs for initialization of the form.
Delete - Delete the current form (if you have privileges)
Clone - Clone the active form and make a new copy.
Publishing - Publish the form to production or sandboxes.
One page is required on a Form in order to publish it. A page allows you to group one or more page elements in order to make natural separations in the questionnaire.
To create a page, click the (+) icon on the main branch of the layout.
Fields are used to store values with can be populated through initializing (by the user or by an integration) and then manipulated during the process of form.
- Field types
- User reference
Certain field names serve a specific purpose, as can be seen below:
AssignedTo: Must be of type ‘User reference’ - If added will the form be forwarded to the user assigned to this field. Allows integrations to create and assign cases to specific users identified by their federation id.
Title: This field will overwrite the default name of the case, allowing you to create a dynamic title such as ‘Customer approval for NewCorp inc.’ This field must be of type String.
Elements are one of the key building blocks of a form, since they come in various shapes and sizes such as input questions, file/documentation requirements, conditional logic and actions.
- Question with input - A simple question where the user fill in a text string.
- Question with choices - A question where the user must select one or more values within a set of values.
- File Upload - A field which allows the user to upload one or more files.
Field update - An action which updates a field associated with the form.
Salesforce Field Update - An action which updates a field in Salesforce
Add Approver - Adds an Approver to the assessment
Email notification - Executes an outbound email message to a specified user or email string.
Condition - Build conditional logic which controls when and if a set of questions should be visible or actions should be executed
Allow user-initiated assessment
User initiated cases allows a user to initiate an case through the user interface by them self (‘New’ button made visible on the Cases page).
Publish a form
A form remains “private” and inaccessible for users until it have been published. The publishing process can be initiated by clicking ‘Publish’ which initiates a validation process. The validation process will go through the form and check if there's any inconsistencies. If any inconsistency is identified then the user will be informed; if this does not happen,t then will the user be able to push ‘Publish’ which completes the process.
Unpublish an form
A published form can be unpublished by clicking the ‘Unpublish’ button. Any assessment already in process will continue and existing completed assessments will not be influenced.