Introduction 

We are proud to introduce a new, refreshed forms module in iPresso. 

The aim of the update is to improve the performance of the forms module and to add new key features. 

It is worth noting that the new forms are a separate module from the old forms. However, the two modules share the same limits’ pool.

 

New forms module can be found in the content tab:

Creating new forms in practice

Templates

The forms are created through the studio editor. The first step is to choose the forms. You can choose either HTML forms or forms via API.

The HTML option allows you to create a custom form using the html code. The API forms are used for forms that are designed outside of iPresso panel and need to be uploaded through the API. The configuration of Rest API and JS API is described below.

Fields

Selecting the template leads to the fields section. This section allows the user to set up all the fields included in the form.  The order in which the fields are created is not important. 

The first step is to choose the type of a field.

It can be one of the following:

• Contact attribute 
• Form fields 
• Consent
• eCouponing pool
• Field Key

New form fields can be created from the field definitions section in the main forms tab. 

Please note that within the Fields section, form fields can only be selected from the list of already existing ones. 

Each field is fully customizable, allowing you to adjust various settings, depending on your needs:: 

• The Settings section allows you to display or hide a given field, based on data provided in another field. After activating this option, a configuration panel will appear:

 

Here you can specify the conditions under which the field will be shown or hidden.

• In the Validations section you can mark a field as required (or mark it as conditionally required based on the information provided in  another field.) You can also specify if the information provided in the field needs to have an email or url format. You may also set the minimum and maximum character limit for the field. After activating each option you may customize the message that will be displayed if a given requirement is not met.

 

Appearance

This section allows for setup and customization of the way the previously created form fields are displayed. Designing the form is done through HTML code. Please note that this section will be available only when selecting the HTML form.

The editor allows you to preview the design of the form on both mobile and desktop versions:

Actions

In the next tab you can decide what changes to the contact should be made once they fill out the form. (i.e. setting a tag or an attribute for that contact).

 

Clicking on the setting icon will open the Additional configuration section where you will be able to decide whether those actions should be implemented in the same way for each instance of filling out the form, or only for the first filling.

Additionally an action that will be activated after completing the form (such as sending an email to a contact, or adding the contact to a scenario) can be set here.

One of these actions is two stage consent authentication - if enabled it will accept the consent only after the contact clicks on a link in a message sent to them.

Settings

Settings is the next section, where you will find all the necessary additional settings for the form, such as its name, API key or error messages. In this tab, among other things, there are options to set limits for how many times the form can be filled, messages informing that the limit is exceeded or the date range in which form remains active.

Summary

The final step is the summary, where all the information provided in previous sections is automatically reviewed and verified.  If any data is missing or has been input incorrectly, it will be displayed in red along with an appropriate warning.

What’s next ?

After saving a new form item, it will be moved to the Drafts. This is the default location for newly created forms. There is an option to activate or test the form.

In order to activate the form, click on run option on the right side.

To test the form, select the more options icon on the right handside and choose run in test mode option from the drop-down list:

The form will then be moved from Drafts to the Test Mode section.

Forms in test mode need to be uploaded to the page in the same manner as active forms (in accordance with the instructions for posting on the webpage). However, they will not be displayed if the webpage address does not contain the "iPressoTestForm=true" parameter. 

 

Example page address would be: "https://my-site.pl?iPressoTestForm=true".

 

Forms in test mode can generate reports. Upon removing the form from the Test Mode section, the reports will be automatically deleted.

Depending on whether the HTML option or the API option is selected, there is an appropriate instruction available:

Placement manual  provides quick reference for embedding the form on a page using HTML:

API call manual holds useful links for API documentation and examples for REST API, MOBILE API and JS API respectively:

 

 

The last step is to enable the appropriate JS API methods for the monitored pages where the form will be run. To enable the method, go to System >> Monitoring >> Site Monitoring. 

Next, select or add the page that will display the form and click on more options icon on the right hand side to set JS API methods:

After accessing this option, activate the last 2 available options i.e. Save Form and Get Form.

Summary

The new version of forms provides the user with many more configuration options, allowing for greater customization compared to the previous version. In the near future a new editor will be added that will make it easier to configure the appearance of forms in the HTML version. 

If you are experiencing any issues with the configuration or functionality of the new feature, please feel free to contact our Success team via e-mail at support@encjacom.atlassian.net or report on JIRA.