With the Address Verification Flow Component now installed and in a Digital Experience, it is essential to provide access to CSP Trusted Sites to our component.
This article will explain what settings are required for users to be able to use AddressTools Verification Flow Component functionality.
Provide Access to our Component in Digital Experiences
Salesforce Setup | navigate to CSP Trusted Sites
Click Edit on https://addressvalidation.provenworks.com | Context "All"
With Address Verification Flow Component now installed in your Org, it is essential to provide your users with the correct permissions to use the solution.
This article will explain what permissions are required for users to be able to use Address Verification Flow Component functionality.
It is recommended that a permission set is created for Address Verification Flow Component so that it can be applied to multiple users/profiles but these settings can be directly applied to the profiles.
Apex and Visualforce
The user/profile will need access to all Apex Classes with the prefix:
pw__avfc.
The user/profile will need access to the following Visualforce Pages:
pw__avfc.SessionIdPage
License Allocation
(Skip this step if you have been provided an Address Verification Flow Component Site License)
After deployment to production, a licenses must be allocated to each users.
This can be managed in Setup | Installed Packages | Manage Licenses next to Address Verification Flow Component.
Typeahead address searching in a CRM enhances efficiency by quickly suggesting relevant address options as the user types. This offers several benefits. Firstly, it results in reduced manual entry time and effort. It also improves data accuracy with up-to-date address databases and auto-completion that directly minimise errors. Lastly, it can also provide functionality to standardise addresses for consistency.
Key benefits:
Improved efficiency by suggesting relevant addresses as a user types.
Enhanced data accuracy through integration with up-to-date address databases and auto-completion.
Standardised addresses for consistency and easy analysis.
Intuitive searching for enhanced user experience and productivity.
Reduced manual entry time and effort.
What are Salesforce Flows?
Salesforce Flows give admins a chance to implement advanced processes into their Org with clicks, not code. Many additional components such as typeahead address entry have been designed by developers allowing anyone to implement and utilise such functionality with little technical knowledge.
To optimise the address entry process, we are going to look at the Address Verification Flow Component by ProvenWorks designed to verify address data at point of entry.
What are some of common use-cases for creating Contacts in a Flow?
There are so many use cases available – way too many to list here! Nevertheless, here are some key ones that can spark your imagination:
Service agents needing to create new Contacts at speed
Customers entering their information in an online checkout
New users registering their details to access a service
What is typeahead address search?
The typeahead address search allows users to start typing an address and a list of addresses will be presented associated with the text entered. Once a user clicks on an address in the list, the address will be populated into a familiar address fields format.
This is preferred to traditional address entry where users must individually enter the relevant address data in full into separate street, city, state, postal code and country fields.
What does this article cover?
We’ve established that a typeahead address search can improve user efficient and the quality of data, and we’ve also explored use cases where Salesforce Flows can optimise record entry in Salesforce. Now let’s combine the two and explore a common use case for Salesforce Flow Screens: Service agents capturing a Contact’s information where we’ll also implement typeahead address search to capture the address.
In this article, we’ll cover:
Creating a new Flow to create a new Contact
Utilising a Flow Screen to capture the Contact fields
Implementing typeahead address search functionality with the Address Verification Flow Component by ProvenWorks, and
Saving this information to a new Contact record.
Pre-requisites
Your Salesforce Org will require two managed packages available from the Salesforce AppExchange to obtain the typeahead address entry component.
It must be noted that these packages are paid for, with return on investment realised through improved staff efficiencies, reduced process abandonment, and better data quality.
💡 Do you have any questions before getting started? Contact us at support@provenworks.com.
Create a new Screen Flow
We’ll start by creating a new Salesforce Screen Flow and creating a new variable to store the Contact details being entered.
Go to Salesforce Setup | Flow
Select New Flow
Choose Screen Flow
Select Done
Add New Resource | Variable
API Name we used NewContact
Data Type | Record
Object | Contact
Select Save
Add a Screen to the Flow to capture the Contact’s information
Now we’ll introduce a Screen element to the Flow which will be responsible for capturing the Contact’s information. This information will be captured in dedicated fields that will eventually be saved to a new record.
Add Element | Screen
Name the Screen
Navigate to Fields (Next to Components) | Record Variable | NewContact
Drag the following fields onto the Screen:
First Name
Last Name
Email
Optionally add any additional fields that you need to capture, i.e. Mobile Number, but leave out the Address fields for now.
Navigate back to Components in the panel on the right of the Screen editor.
Add Address Verification by ProvenWorks into the Screen.
Click on the Address Verification by ProvenWorks component to open the component parameters on the right of the interface.
Scroll down the parameters and tick Manually assign variables
Assign the following Values:
City Value > {!NewContact.MailingCity}
Country Value > {!NewContact.MailingCountry}
Postal Code Value > {!NewContact.MailingPostalCode}
State/Province Value > {!NewContact.MailingState}
Status Value > {!NewContact.pw_ccpro__MailingAddressStatus__c}
Street Value > {!NewContact.MailingStreet}
Click Done
Create the Contact Records
Now that we’ve completed a Flow Screen to capture the Contact’s information, we need to save it to a new Contact record in Salesforce.
Add Element | Create records
Name the Label
Create a Record from These Values | Record | NewContact
Click Done
Save the Flow
With a Flow now capable of capturing Contact information and saving it to a new Contact record, let’s save the Flow so we can utilise it in our Salesforce Org.
Select Save
Provide a Flow Label to help you identify the flow in the future, i.e. “Service Agent Contact Capture”
The Flow API Name will be auto populated, change this if required.
Click Save
Activate the flow
Copy the Flow’s URL
From Setup, enter in the Quick Find box, and then select Flows
Click the down arrow in the Flow we created, then click View Details and Versions
Copy the flow’s URL from the Flow Detail page
Incorporate the Flow into a Button
Buttons are a great way to distribute Flows to users in Salesforce. If you have a service agent taking calls, providing them an easy to access button to create a new contact can be a speedy way to get the job done with little hassle.
Go to Salesforce Setup | Contact | Buttons, Links, and Actions
Select New Button or Link
Label | Verify New Contact
Name | Verify_New_Contact
Display Type | List Button
Behaviour | Display in existing window with sidebar
Content Source | URL
Select Field Type | Contact
Paste the Flow’s URL link we copied earlier in the large text box like the example below (your link may differ as it is dependent on naming)
Click Save
Add the Button onto the List View Button Layout
Go to Salesforce Setup | Object Manager | Contact | List View Button Layout
List View Button Layout | Edit | Custom Buttons
Add the newly created custom button to Selected Buttons
Click Save
The Button will now be available in the Contact List View
Summary
And there you have it – our complete follow-along guide for creating a Screen Flow to enter a Contact record with a verified address!
We hope this article has given you the tools you need to set up your Salesforce CRM for better address data quality alongside a better use experience. If there’s anything you’re stuck on, or if you have any questions, please don’t hesitate to get in touch with us.
If you’re ready to get started with your own address data journey, why not jump on a kick off call with our team and let’s help you make the most of your Salesforce investment!
Please note: To leverage this component, your org must have AddressTools Premium installed from the AppExchange with Address Verification credits.
We always look to improve our products and the Address Verification Flow Component is no different! We have been hard at work enhancing the component with additional functionality to improve your user experience and up your address data game.
Here is the list of updates we will cover in this article:
Custom CSS is now available via a Salesforce Flow Screen
Users no longer need “View All Custom Settings” permission enabled on their profile
Additional accessibility tags have been implemented
Improved search results by filtering and prioritising countries
Street Line 2 parameter
Release notes
How to upgrade
Custom CSS is now available via a Salesforce Flow Screen
Ensuring a Salesforce Org matches your company’s brandingis important, and even more so in digital experiences. We want to ensure that you don’t need tocompromise yourvisuals when using our flow component. We’ve made changes to simplify adding a CSS file to the componentso that you no longer need to wrap it in an Aura component first.
Users no longer need “View All Custom Settings” permission enabled on their profile
Previously, users required the “View All Custom Settings” permission on their profileto utilisethe Address Verification Flow Component. This is now no longer a requirement; all you need to do is update the package and then the permission can be revoked.
Additional accessibility tags have been implemented
We believe our tools should be able to be used by everyone, and that’s why we’ve improved the accessibility tags within the flow component to make them more descriptive.
Improved search results by filtering and prioritising countries
We understand how important it is to provide the most relevant results first when looking up an address. That’s why we’veimplemented ‘Top Priority Country’ to help promote the best results, saving the usertime and reducing keystrokes.
Adding Street Line 2 provides the flow componentwith the ability to split the street responses across 2 fields. Thisfeature means it is easier tocomply with strict character limits you might face. Street Line 2 is now available in the Address Verification Flow Component.
To see the full list of enhancements and improvements, please refer to the Release Notes.
How to Upgrade
To access the new features, you will need to upgradethe Address Verification Flow Component package. You can upgrade your version of the AddressTools Verification Flow Component by installing the latest package from the AppExchange.
The AddressTools Flow Component is installed in your organisation, find it here on the AppExchange.
The AddressTools Flow Component will need to be in a Screen-Flow before starting the configuration. If you need to add the component to a Screen-Flow, the steps of how to achieve this can be found here.
Display Company Name in Address
Navigate to your Salesforce Flow in Salesforce Setup
Click the Address Verification by ProvenWorks component that you previously setup.
Ensure that Return Company in Street is set to {!$GlobalConstant.True}.
With AddressTools now installed in your Org, it is essential to provide your users with the correct permissions to use the solution.
This article will explain what permissions are required for users to be able to use AddressTools functionality.
It is recommended that a permission set is created for AddressTools so that it can be applied to multiple users/profiles but these settings can be directly applied to the profiles.
Object and Field Permissions
Setup each object and associated fields with the permissions noted in the table below.
Object
Object Permission
Field Name
Field Permission
Users
N/A
QuickComplete Country
Read
Countries
View All
All fields
Read
States
View All
All fields
Read
Apex, Visualforce and Custom Settings
The user/profile will need access to all Apex Classes with the prefix:
pw_cc.
The user/profile will need access to the following Visualforce Pages:
pw_cc__CountriesJavaScript
pw_cc__SessionIdPage
The user/profile will need access to the following Custom Setting Definitions:
pw_cc.CountryComplete Settings
pw_cc.AddressTools Fields to Validate
License Allocation
After deployment to production, a site licenses is provided.
One of the first steps during the installation walkthrough is ‘Installing a Default Country’. QuickComplete is the specific functionality in the solution that leverages this value to life. If you need to install a default country to all your users, follow the installing a default country article, then come back here when you’re done.
Installing a separate default country for different users
The user records in Salesforce are provided with a new field “QuickCompleteCountry(pw_cc__QuickCompleteCountry__c)” when AddressTools is installed. This field is what stores a text value of the default country for the user for use with QuickComplete Country. Before you can update the field in the user interface, add this field to the User page layout.
Navigate to the User record that you want to add a default country to.
Select Edit.
In the QuickComplete Country field, type the name of the country you want to add.
When complete, Save the record.
Repeat for any additional users you want to update.
Note: The QuickComplete Country field is a text field that can accept any value, however, you should only write in country names that you have installed in your organization. Failure to match these values may result in validation rules failing.
Enabling QuickComplete Country
Go to App Launcher | AddressTools Administration.
Select Settings from the sidebar.
Click the pencil next to QuickComplete Country Enabled and tick the checkbox.
Default country installation will become available once enabled. Use the Default Country Installation picklist to choose the default country for the organization.
To use QuickComplete Country functionality, you are required to install a default country. This populates the custom field pw_cc__QuickCompleteCountry__c on the User object for all users in the organization.
You can find out more about the QuickComplete by reading the article here. This is covered later in the installation walkthrough.
To install a default country:
Go to App Launcher | AddressTools Free Administration.
Use the picklist and select a Country under Default Country Installation.
If the picklist is empty, you may need to refresh the page after completing a data installation.
Select Install.
A process will begin in the background to populate the records in the organization. The time taken will vary in relation to how many users are in your organization.
AddressTools Free is the ultimate address functionality tool for Salesforce jam-packed with features. This article will guide you through configuring the product for the first time and provide guidance on updating settings on an ongoing basis.
Our solution AddressTools is an award-winning suite of functionality that is native to Salesforce CRM. Off-the-shelf, verify global address data, standardise your addresses for integrations and use native functionality including validation rules and lookup fields to make the most out of your CRM address data.
If you’re deciding between AddressTools v Google Maps API that Salesforce offers out of the box, this article is for you. We hope it sheds light on when it’s the right option for you to buy AddressTools versus the right option for you to use the Google Maps API that Salesforce offers.
First off let’s have a quick glance at some broader reasons you might choose to buy AddressTools or to use the Google Maps API.
3 reasons to choose AddressTools
Verify address data at the point of entry and in batch jobs
Includes an address status field so you can see and report on cleanliness of data
Populates a County field and ZIP+4 Code* as default
You don’t require or rely on any address and/or accurate address data
You don’t need to understand, report on or act upon the quality of your address data
Let’s dive deeper into a few key factors we’ve introduced here, starting with arguably the most important.
Need answers quickly? We provide a bitesize summary at the bottom of each section.
Quality of address data
Google Maps API does not provide verified address data. Google Maps API makes it easy to enter addresses, but it does not provide any guarantee of ensuring proper addresses are captured.
As ServiceObjects explains, “The Google Maps API uses spatial interpolation to return results for an address that may or may not be valid, or even exist.”
Let’s take a look at a US example: 9011 Marymount Way in Goleta, California.
Google Maps API data quality
In Salesforce, the Google Maps API returns the address for the user to select.
Looking up this address in Google Maps even gives us a pin and directions for this location.
The problem is that 9011 Marymount Way does not exist.
It is not a real address and, as you can see by the fact there is no house there, it cannot be delivered to. However, Google Maps API presents it as an actual address, allowing the user to input incorrect data.
As we can see, there is a big difference between Google data and verified data. This is not the only example.
Why don’t we take a look at a UK address: 27 Albion Terrace, Reading RG1 5BG.
The Google Maps API in Salesforce presents plenty of Albion Terraces…
…but doesn’t have 27 Albion Terrace, Reading in the UK at all (see below). Google Maps data would have you believe that this very real address does not exist. For a user, this means they need to manually type additional keystrokes, increasing the risk of human error and leading to a frustrating user experience.
AddressTools data quality
Unlike the Google Maps API, AddressTools uses global postal authority data such as Royal Mail, USPS and Canada Post for truly verified data, reducing failed delivery rates by up to 70%.
Let’s run the same address searches using AddressTools.
When we look for 9011 Marymount Way in Goleta, California, we can see that Marymount Way exists in Goleta but number 9011 is not even presented as an option and we are only offered verified alternative addresses (including ZIP+4 Code).
Furthermore, upon selection and population of a verified address, we are shown an Address Status value so that we can be certain of the address quality.
When we search for 27 Albion Terrace, Reading, UK we are presented with this address as a verified result, sourced from the Royal Mail database.
In short: There is a clear distinction between the address data quality offered by Google Maps API and by AddressTools. It’s up to you to decide how important good address data quality is for you and your organisation.
Address status field
One important feature of AddressTools that Google Maps API does not offer is an address status field.
What does this field look like? With AddressTools, every address is assigned a status such as Verified, Corrected, Ambiguous, Parsed but not Found, Not matched, Not checked.
This address status is important because now you can clearly see and even more importantly, clearly report on the quality of your address data.
Working with address data, knowing that an address is bad can be just as valuable as knowing an address exists. With an address status field in place, you are able to develop recovery processes for unverified addresses.
Out-of-the-box, the Google Maps API does not offer an address status. This means that you cannot determine if an address was delivered by Google Maps API or manually entered by a user or imported by an integration.
💡 If you’re interested in learning more, we’ve got a two-minute clip of Callum Hurry, our Director of Product Engineering, explaining the value of an address status field.
In short: An address status field is a vital tool for reporting on and understanding the quality of your address data. It’s up to you to decide how important understanding and reporting on your address data quality is for you and your organisation.
Address data management
The most important difference when considering AddressTools v Google Maps API, aside from address data quality, is how AddressTools helps you make the most out of your address data. We’ve already started to see this with the address status field, however there’s much more to consider.
AddressTools is not just a postal address verification tool. It’s a powerful dataset that, when used strategically, can optimise your business processes. With AddressTools, you gain a bundle of objects for Country, State, US ZIP Code data and more. By customising these objects and using our Lookup field functionality, you can enrich, tidy up, and simplify your records to enhance your territory management and make the most out of your CRM address data.
What does this mean in practice? How about adding a Field Rep to relevant regions? Maybe you have a preferred regional service provider? What about using AddressTools’ Country ISO values alongside the full country name to work with an integration? You can harness the AddressTools dataset however you want to use it.
In short: AddressTools offers a suite of functionality around address data and address data management. It’s up to you to decide whether you’re just looking to populate an address (great – the Google Maps API sounds perfect for you!) or give yourself a way to manage, verify and harness the power of your address data.
AddressTools v Google Maps API – it’s your decision
Thanks for sticking with us this far! We’ve examined three key factors that you need to consider whilst considering AddressTools v Google Maps API:
address data quality
an address status value
broader address data management requirements
We hope this provides the necessary information and some food for thought on which you can make the right decision for you and your organisation’s needs.
If you’ve still got questions about AddressTools, we’re always happy to chat! If you’ve made up your mind, congratulations! Now it’s time to implement and continue your data journey!
Check out AddressTools for yourself
Let’s discuss how you can use AddressTools to leverage the power of verified address data in Salesforce! Book a demo to see AddressTools in action on a live demo with our team.
