Input Fields
There are three types of input field, beyond the smart fields of course, which are:
Text Field
The first option 'Text field' enables a simple answer to be provided in a single regular 1 line height box.
Multi-line text field
The second 'Multi-line text field' provides a larger text area where the answer could be large.
The third one is the most powerful
Test field with validation
This input field type enables you to create your own custom smart fields leveraging both the ability to:
set a minimum/maximum length as well as to set a
'Regular Expression' on a question's answer
For example:
In the above we can see that a minimum and maximum length have been set for the answer.
Plus, we can see a regular expression is present. The purpose, of this seemingly gobbledegook, is to ensure the format of the answer they provide is EXACTLY the format expected.
There is also a dedicated Failed Validation error message, which enables you to provide guidance if the person enters it in a manner that does not conform to the expected format.
To learn more about regular expressions have a read below:
https://www.regular-expressions.info/quickstart.html
To search for examples of regular expressions - so you don't need to learn them - please see here:
From eDesigner 2.13 - Prepopulated fields
From this release you are now able to add fields to a page that are prepopulated with data that has been added to text fields on a previous page or with today’s date. This could be used to add confirmation details to a Declaration page or to construct your own Direct Debit Mandate page for example but there will be many more use cases for this functionality.
Text fields: addition of the following options to the Text field type:
· Pre-populated value XPath
· Read-only
For a standard text field the format of the XPath is
//page[@id='page id']/field id (note this is case sensitive)
For Section fields the format of the XPath is slightly different as the field values are hardcoded and the Field ID is what you assigned to your Section when it was created. For example for the bank account validation fields the following is used:
Account number is : //page[@id='page id']/field id/AccountNumber
Sort code is : //page[@id='page id']/field id/SortCode
Example where "valid" is the FieldID for the Bank Account Details Section:
A new Resource has been added for Read Only fields to enable you to configure the indicator displayed for them. This will default to read-only but can be changed to blank if required.
Note: when adding pre-populated fields do not mark them as mandatory as otherwise the validation rules will be triggered and the data is not recognised.
Last updated