What is the Inquiry Address Input component?
Inquiry Address Input is an Inquiry screen component that allows a user to enter and validate an address within a predefined format.
An Inquiry Address Input component is ideal for scenarios where structured address collection is needed, such as shipping details or residency verification.
How do you add an Inquiry Address Input component?
- Navigate to the Dashboard, and click on Inquiries > Templates.
- Find and click on the Inquiry template you want to edit, or Create a new template.
- Hover over a Screen and click the Edit button to view the Component Library.
- In the left toolbar, click Component Library and search for ‘Address Input’.
- Drag and drop the Address Input component into your screen, and reposition it by dragging it around.
- Click on the Address Input component, and go to Properties in the right toolbar.
- (Optional) Under Settings, you can Configure Autocomplete and Formatting Settings:
- Autocomplete Method: Choose whether autocomplete is enabled for this component. Selecting ‘None’ disables autocomplete, while selecting ‘Google Maps’ enables it. ‘Google Maps’ will be selected as the default.
- Address Subdivision Format: Determines whether autocomplete provides a full or abbreviated value for subdivisions/states (e.g., two-letter state codes). Choosing ‘Long name’ returns the full value, while ‘Short name’ provides the abbreviated version. ‘Long name’ will be selected as the default.
- (Optional) Under Settings, you can Configure Autocomplete and Formatting Settings:
1. **Place Type**: Defines the type of places returned in autocomplete results. Options include **Geocode**, **Address**, and **Establishment**, based on the Google Place Autocomplete API.
- (Optional) Add a customized label, placeholder, and translations:
- Edit the text in the Edit Address Manually Prompt box. The text element displayed below the Address Input component provides an option for a user to enter an address manually.
2. Edit the text in the **Label** box. The **Label** is a text element displayed above the Address Input component to describe its purpose, such as “Enter your address” helping users understand what information to provide.
3. Edit the text in the **Placeholder** boxes. The **Placeholder** boxes display temporary text inside the Address Input components, such as “Street, City, State, ZIP” offering an example or guidance on the expected format until the user enters their own input.
4. Add translations for the text by clicking **Edit translations.** You can **Translate All** or **Translate** individual languages, manually or automatically. If you don’t set translations, you’ll be prompted to do so upon **Publishing** the template.
- In the Fields toolbar tab, you can set up and customize the behavior of the Address Input component.
- Required: Choose whether the field is mandatory (Yes), optional (No), or based on conditions (Conditional). If you choose Conditional, you will need to set a Logic rule, you can read more about Logic below.
- (Optional) In the Logic toolbar tab, you can add rules that govern when the component appears and when it does not. You can read more about Logic below.
- Close the step. You’ll have to Save and Publish the template to begin using it.
Translations
Persona can automatically translate new text into other languages in the component’s Properties tab. You can also customize the translation for any particular language.
Logic
Persona provides you with the ability to add logic to an Address Input component. For example, a component may only become visible to a user if certain conditions are met. On the Logic tool bar tab, there are two options for logic rules:
- On screen load: Logic rules are evaluated only when the screen loads. They can reference any field configured on the template.
- On screen update: Logic rules are evaluated in real time. They can only reference inputs on the current screen.
For form components a field can be labeled as required under specific conditions.
- Require field: Logic rules are evaluated in real time referencing inputs on the current screen. They can only reference inputs on the current screen.
Logic Rules
Logic rules consist of three main components:
- Field: The object that will have a condition linked to it.
- Condition: How the field is compared to the value (e.g., equals, does not equal).
- Value: The value to test against.
Creating Logic Rules
- AND Statements: Combine multiple conditions that must all be true for the rule to pass. Add these using the "Add" button.
- OR Groups: Combine conditions where only one needs to be true for the rule to pass. Create these by clicking "Add OR Group".
How to Use Logic Rules
- Click on the Address Input component, and go to Logic in the right toolbar.
- Choose either “On screen load” or “On screen update” and click Add.
- Choose what Component Update to apply. This determines what happens to the component when the logical rules are met.
- Create a logical rule by filling in the three boxes following When, which correspond to an object, its condition, and its value being assessed, respectively. When that logical rule passes, the component update is applied.
- (Optional) Add additional logical rules by clicking either + Add (if you want to add 'AND' rules, where all must be passed to continue) or + Or (if you want to add 'OR' rules, where one must be passed to continue). You can also nest a group of OR statements within an AND statement by clicking + Add Group.
- (Optional) To edit the logic directly, you can open the code editor.
Plans Explained
Address Input component by plan
Startup Program | Essential Plan | Growth Plan | Enterprise Plan | |
---|---|---|---|---|
Address Input component | Limited | Available | Available | Available |
Translations for Address Input component | Limited | Limited | Available | Available |
Logic for Address Input component | Limited | Limited | Limited | Available |
Learn more about pricing and plans.