Blog

How to: deploy SimpleImport and Managed Import to users in your organization

Overview

SimpleImport has three main implementation paths:

  1. SimpleImport (requires API Enabled) [Premium, Free]
  2. Managed Import with API Enabled (requires API Enabled)
  3. Managed Import with Apex Rest Services (requires Apex REST Services but not API Enabled)

Different paths require their own dedicated permissions which need to be assigned to the user/profile in Salesforce to leverage functionality. This article has been broken down to provide you with all the permissions required for your desired approach.

Why use permission sets?

A permission set is a collection of settings and permissions that give users access to various tools and functions. Permission sets extend users’ functional access without changing their profiles. This allows to easily see the what users have access to as you are able to name the permission set.


Create a permission set

  1. From Setup, enter Permission Sets in the Quick Find box, then select Permission Sets.
  2. Click New.
  3. Enter your permission set name.
  4. Select the types of users for the permission set.

 

SimpleImport [Premium, Free]

Apex, Visualforce and Custom Settings

The user/profile will need access to all Apex Classes with the prefix:

  • pw_si__ [Premium]
  • pw_sifree__ [Free]

The user/profile will need access to the following Visualforce Pages:

  • pw_si__SimpleImport [Premium]
  • pw_sifree__SimpleImport [Free]

The user/profile will need access to the following Custom Setting Definitions:

  • SimpleImport Settings [Premium, Free]
  • Managed Import Settings [Premium]

Managed Import (with API Enabled or with Apex REST Services) [Premium Only]

Apex, Visualforce and Custom Settings

The user/profile will need access to all Apex Classes with the prefix:

  • pw_si__

The user/profile will need access to the following Visualforce Pages:

  • pw_si__SessionIdPage

The user/profile will need access to the following Custom Setting Definitions:

  • SimpleImport Settings
  • Managed Import Settings

License Allocation [Premium, Free]

After deployment to production, a licenses must be allocated to each users.

This can be managed in Setup | Installed Packages | Manage Licenses next to SimpleImport.

API Enabled or Apex REST Services? [Premium Only]

For Managed Import, if there is the option to use the solution with API Enabled, then this is recommended. For some implementations, API Enabled is not preferred, such as community implementations. For these cases, Apex REST Services must be enabled on the profile as the fall back option.

Contact Us

If you have followed this article and are still experiencing issues with configured SimpleImport or Managed Import, reach out to support@provenworks.com where a member of the team will be happy to assist.

Back to the SimpleImport User Guide

How to: Provide access to our Address Verification Flow Component in a Digital Experience

Overview

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

  1. Salesforce Setup | navigate to CSP Trusted Sites
  2. Click Edit on https://addressvalidation.provenworks.com | Context "All"
  3. Click on Save.

Back to the Address Verification Flow Component installation walkthrough

How to: deploy Address Verification Flow Component to users in your organization

Overview

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.

 

Back to the Address Verification Flow Component installation walkthrough

Create a Contact with a Clean Address in a Salesforce Screen Flow

Introduction

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.

Contact us at support@provenworks.com

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!

[Calendly – AddressTools]

Address Verification Flow Component: Understanding the Parameters

What Does Each Parameter Do?

  • Additional Styles – This field is responsible for applying custom CSS themes to the component, a guide on how to use this can be found here.
  • Address Label – This field is responsible for changing the text in the Address header.
  • Allowed Countries – Allows a string of ISO-2 or ISO-3 values for countries to limit PowerSearch results to.
  • City Label – This field is responsible for changing the text in the City field label.
  • City Value – This field allows you to preset a value for the City field to be auto-filled before entering the address.
  • Country Label – This field is responsible for changing the text in the Country field label.
  • Country Value – This field allows you to preset a value for the Country field to be auto-filled before entering the address.
  • County Label – This field is responsible for changing the text in the County field label.
  • County Value – This field allows you to preset a value for the County field to be auto-filled before entering the address.
  • Inline Mode – Allows users to edit fields without having to toggle between a ‘read-only’ view and an ‘edit’ view.
  • Manual Button Label – This field is responsible for changing the text on the Manual button.
  • Postal Code Value – This field allows you to preset a value for the Postal Code field to be auto-filled before entering the address.
  • Read-only Mode – When set to {!$GlobalConstant.True}, this prevents the user from being able to input an address.
  • Return Company in Street – When set to {!$GlobalConstant.True}, this will display the company name in the street output.
  • Search Label – This field is responsible for changing the text in the Search field label.
  • State/Province Label – This field is responsible for changing the text in the Province field label.
  • State/Province Value – This field allows you to preset a value for the Province field to be auto-filled before entering the address.
  • Status Label – This field is responsible for changing the text in the Status label.
  • Status Value – This field allows you to preset a value for the Status field to be auto-filled before entering the address.
  • Street Label – This field is responsible for changing the text in the Street field label.
  • Street2 Label – This field is responsible for changing the text in the Street2 field label.
  • Street2 Value – This field allows you to preset a value for the Street2 field to be auto-filled before entering the address.
  • Top Priority Country – This field allows for a singular ISO-2 or ISO-3 country which is then used to prioritise results.
  • Use County – When set to {!$GlobalConstant.True}, this will display a county field for search results.
  • Use Second Street Line – A guide on how to enable Street2 can be found here
  • Use Status– When set to {!$GlobalConstant.True}, this will display the verification status of the search result.
  • Verify Button Label – This field is responsible for changing the text on the Verify button.

Address Verification Flow Component: Apply Custom CSS Using Additional Styles

Within the Address Verification Flow Component, you have the ability to edit all of the visual aspects allowing you to achieve a personalized final look.

How to Create a Custom Style Sheet

  • First, save and edit the code template which can be found below – ensure it is saved as a CSS file.
  • This template illustrates some of the basic changes that can be made, but any CSS functionality is supported.
.powersearch .form-element-label
{
color: Blue;
font-size: 15px;
}


.powersearch
{
font-size: 12px;
color: Green;
background: white;
}


powersearch .form-element-input,
powersearch .form-element-textarea,
powersearch .form-element-select
{
border: 1px solid Black;
}


.powersearch .form-element-button
{
color: Aquamarine;
}


.powersearch .form-element-input,
.powersearch .form-element-textarea,
.powersearch .form-element-select,
.powersearch .slds-input
{
border-color: DarkMagenta;
}


.powersearch .form-element-input:focus,
.powersearch .form-element-input:active,
.powersearch .form-element-textarea:focus,
.powersearch .form-element-textarea:active,
.powersearch .form-element-select:focus,
.powersearch .form-element-select:active,
.powersearch .slds-input:focus,
.powersearch .slds-input:active
{
border-color: Navy;
}


How to Upload the Custom Styling

  • Navigate to Salesforce Setup | Static Resources.
  • Create a new Static Resource, select Choose File and upload the CSS file.
  • After clicking Save, on the Record Page click View File

  • Copy the end of the URL from /resource onwards, for example: /resource/1686062712000/ExampleCSS
  • Navigate over to the flow that you would like to apply this styling to.
  • Open the Screen that you are editing and then select the Address Verification by ProvenWorks component that you have added.
  • Under Additional Styles paste the extract from the resource URL that you copied

 

Before vs After

Before applying the custom styling:





After applying the custom styling:

Back to the Address Verification Flow Component installation walkthrough

Address Verification Flow Component: Enable 2 Street Line Address

Prerequisites

  • 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.

Enable 2 Street Line Address

  • Navigate to your Salesforce Flow in Salesforce Setup
  • Click the Address Verification by ProvenWorks component that you previously setup.
  • Ensure that Use Second Street Line is set to {!$GlobalConstant.True}.

Once Street line 2 is enabled you can label it to your preference using the Street2 Label field.

Back to the Address Verification Flow Component installation walkthrough

How to: deploy AddressTools Free to users in your organization

Overview

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.


Back to the AddressTools Free installation walkthrough

AddressTools Free: Install a default country and enable QuickComplete Country

Installing a default country for all users

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.
  • Use the Save button.

 


Back to the AddressTools Free installation walkthrough

AddressTools Free: Understanding QuickComplete Country functionality

What is QuickComplete Country?

QuickComplete Country allows you to install a default country for each of your users. The trigger has the ability to auto-populate the country field if it is left null.

Trigger behaviour

When QuickComplete Country is enabled, it has the ability to automatically populate the country field with the default country value without any direct user interaction. This will operate when a change is made to any configured address fields when the country field is left null. If all address fields are left null or untouched, the default country will not be populated into the country field.

Back to the AddressTools Free installation walkthrough