Platform URL | https://[enterprise].cvtr.io/v2/forms |
|---|---|
API Endpoints | Not Applicable |
Epic | GFR-50 - Getting issue details... STATUS |
Document status | DRAFT |
Document owner | |
Technical writers | |
Related Content | https://convertr.atlassian.net/wiki/spaces/PF/pages/edit-v2/3058532652 |
🏠 Feature Overview
This page describes the different lookup input types available in Forms.
AddressLookup (Provided by: T2A)
AddressLookupGlobal (Provided by: Google)
EmailLookup (Provided by: Briteverify)
InternationalCompanyAddressLookup (Provided by: Dun & Bradstreet)
TelephoneLookup (Provided by: Data8 [TBC])
TelephoneLookupInternational (Provided by: Informatica)
TelephoneLookupInternational2 (Provided by: Twillio)
1. Address Lookup
This lookup allows the user to search a UK postcode. which once selected will automatically populate 4 address lines and a postcode field.
Field settings:
Field Name | Required | Notes |
Name |
| Prepopulated with postcodeLookup |
Label |
| Prepopulated with Postcode Lookup. |
Placeholder |
| Preselected with No. If changed to Yes, the Address fields and postcode field will have a placeholder (configured via the field settings). |
CSS Class |
| Add a CSS class to allow more targeted CSS styling. |
Changing input label/placeholder values:
In the field ‘settings’ dialog, under the ‘input_descriptions’ tree, there will be a key/value item for each input where the value can be changed and will be reflected in the input label and placeholder.
Changing input required:
In the field ‘settings’ dialog, under the ‘input_required’ tree, there will be a key/value item for each input where the value can be changed to either true or false.
True: When completing the form and no value is added to the input, clicking the submit button will trigger the validation message and the form cannot be completed until this input has been populated.
False: When completing the form, this input does not require a value for the form to be completed.
Changing required messages:
In the field ‘settings’ dialog, under the ‘input_required_messages’ tree, there will be a key/value item for each input where the message shown when a required field has not been completed can be changed.
Lookup example:
2. Address LookupGlobal
This lookup allows the user to search a global address. which once selected will automatically populate 4 address lines, a country field and a postcode field.
Field settings:
Field Name | Required | Notes |
Name |
| Prepopulated with addressLookupGlobal |
Label |
| Prepopulated with Address Lookup Global. |
Placeholder |
| Preselected with No. If changed to Yes, the Address fields and postcode field will have a placeholder (configured via the field settings). |
CSS Class |
| Add a CSS class to allow more targeted CSS styling. |
Changing input label/placeholder values:
In the field ‘settings’ dialog, under the ‘input_descriptions’ tree, there will be a key/value item for each input where the value can be changed and will be reflected in the input label and placeholder.
Changing input required:
In the field ‘settings’ dialog, under the ‘input_required’ tree, there will be a key/value item for each input where the value can be changed to either true or false.
True: When completing the form and no value is added to the input, clicking the submit button will trigger the validation message and the form cannot be completed until this input has been populated.
False: When completing the form, this input does not require a value for the form to be completed.
Changing required messages:
In the field ‘settings’ dialog, under the ‘input_required_messages’ tree, there will be a key/value item for each input where the message shown when a required field has not been completed can be changed.
Lookup example: