The component can be dropped into a flow screen in a place of your choice. It is designed to use the same variable names as the standard Address component provided by Salesforce allowing you to quickly “hot-swap” your existing address component with the Address Verification component.
Navigate to Flows in Salesforce Setup.
Double click an existing Screen Flow to edit, or add a New Flow and select Screen Flow under Frequently Used to create a new one.
Select an existing Screen element from the flow, or add an element to your flow and select Screen to open the New Screen editor.
Search for Address in the Component search.
Drag the Address Verification by ProvenWorks component into the flow screen.
Fill in the desired parameters to meet your requirements.
When you’re done, save your flow and you’re ready to go!
We’re excited to announce that PhoneTools 2.0 (Spring ‘22 Release) has arrived!
PhoneTools lets you screen your numbers against the TPS and CTPS databases, keeping you compliant with UK data privacy laws – all within Salesforce! With the much-anticipated addition of flow functionality and brand new support documentation, let’s take a closer look.
Screen your numbers in a Salesforce flow
Let’s quickly recap PhoneTools so far. PhoneTools already allows you to schedule automated nightly record screening, specifically records that have not yet been screened or have their Next Screen Due Date in the past.
Whilst practical, this leaves a window of time after the record is inserted/updated where the numbers won’t be screened until the next nightly batch job or manual user interaction.
That’s where flows come in to fill the gap.
PhoneTools 2.0 can be used within the powerful process automation tool that is Salesforce flow. What does this look like in practice? This means that you can now queue an immediate TPS and CTPS screening job to get the numbers’ screening statuses in seconds*!
With the flow, PhoneTools will queue a screening job automatically so there’s no need to wait for a nightly screening job. Equally important, is that you no longer need to rely on the user to manually click ‘Screen Phone Numbers’. Crucially, this means you can remove responsibility from your users and automate the process… what a business win!
How can you use your flow? Our best practice recommendation is to queue your screening jobs on insert and update to make sure your org has a shorter period of time holding data without a valid screening status. The outcome? Streamline your sales team’s operations and let them focus on what they do best, selling!
Does this replace my existing method of screening numbers?
This flow functionality is designed to be an additional method to screen numbers on top of what you already have configured. The nightly batch job is key for picking up those records when they’re overdue and the ‘Screen Phone Numbers’ button is helpful for re-opening old prospects. The flow functionality is designed to minimize the gap between inserting new data and providing a status as soon as possible without user interaction.
By the end of the guide, you’ll have your own flow configured and ready to screen those inserted and updated numbers. With the flow, you’re good to go!
So you’ve just deployed a new trigger or flow and you want to push your org’s existing records through it. This can often be referred to as a “Mass Touch” or “Mass Update”. There are many different ways that this can be achieved, some involving exporting data using third-party tools, but here’s one approach that can be done completely within Salesforce, and with no code!
Create a new “Mass Touch” field
We’ll start the process by adding a new field on the object we want to fire the trigger on. This field will be used to update the record without touching its existing data.
Go to Salesforce Setup.
Select Object Manager.
Locate the object you want to execute a mass touch for and select it.
Go to Fields & Relationships.
Select New.
Data Type: Number.
Press Next.
Field Label: Mass Touch
Length: 1
Decimal Places: 0
Field Name: MassTouch
Help Text: This field should only be used to invoke an update on the record and should not be populated by user entry.
Press Next.
Only provide visibility to your profile (or the profile of the user completing this process).
Press Next.
Uncheck Add Field to prevent the field from being added to the page layout.
Select Save.
Your object now has a new field that can be updated without impacting existing business data.
Creating a scheduled flow
We now need to create a flow that’s going to look at all the records on the object and update the Mass Touch field just created. We’re going to do this using a Scheduled Flow as this will allow us to set a time for the process to fire. If your object has a lot of existing records it may be preferable to run this process out of hours.
Go to Salesforce Setup.
Search for Flows in the left navigation and select Flows.
Select New Flow.
Choose Schedule-Trigger Flow and select Create.
Select Set Schedule.
Choose a Start Date and Start Time that work for your org.
Set Frequency as Once.
Select Done.
There is no requirement to specify an object in the start element so leave this empty.
The start element in the flow is now configured. Let’s follow that up and add an Update Records element.
Press the + icon to open the Add Element view.
Scroll down to Data and select Update Records.
Label: Update Records
API Name: UpdateRecords
Description: Set the records' Mass Touch field to a new value.
How to Find Records to Update and Set Their Values: Specify conditions to identify records, and set fields individually.
Under Update Record of This Object Type, search and select the Object you want to perform the mass touch on.
Under Filter Object Records, you can add conditions to only mass touch a selection of records, or have this set to “None” which will update all. We’ll use None for this example.
Under Set Field Values for the Object Records, choose the Mass Touch (MassTouch__c) field.
Value: 1. (If you’re running the mass touch on this object again in the future you can change this value to 2, or 3 and keep cycling the number for each mass touch you want to complete, it just needs to change from its previous value).
Select Done.
With the flow configured, we now need to save it and name it.
Select Save from the top right.
Provide a Name and Description for the flow so that you will be able to identify it in the future should you wish to run it again.
Validation rule management
Before running a mass touch job on the object we need to consider validation rules. Flows do not have an elegant way to bypass validation rules so keep an eye out for any flow errors when the job runs. An email will be sent to your own user account’s email address containing the errors faced during the flow allowing you to manually correct the conflicting errors (see image below).
If there are some common offending validation rules consider disabling them temporarily to complete this task but remember to re-enable them when you’re done!
Run the flow
The flow is now fully configured and ready to be activated. Use the Activate button in the top right to enable the flow. The mass touch operation will begin when the scheduled time configured in the Start element is met.
If you don’t want to wait for the scheduled time you can run the flow immediately by selecting Debug. Make sure that you uncheck “Run flow in rollback mode” to ensure that the mass touch’s changes persist after the flow has been executed.
Remember, check your emails after the flow has run to review any errors as the update can roll back multiple records even if a single record fails.
Summary
We hope that you have found this article to be helpful for your organization and just a reminder to be vigilant when running mass update operations in a production environment, where possible backup your data first.
If you’d like to find out more about what ProvenWorks do, check out our homepage.
Automated phone screening functionality covered so far in this installation walkthrough will screen records nightly that have not yet been screened or have their Next Screen Due Date in the past. Whilst practical, this leaves a space of time between the record being inserted/updated where the numbers won’t be screened until the next nightly batch job or user interaction.
That’s where flows come in to fill the gap.
Create a flow to screen the record
Go to Salesforce Setup | Flow.
Select New Flow.
Choose Record-Triggered Flow.
Search and select the object that you are configuring the process for.
Set Trigger the Flow When to A record is created or updated.
Select Done.
The flow will now be ready to start adding elements to.
Select the Decision Logic and drag it under the Start element.
Label: Is NULL or Overdue
API Name: IsNULLorOverdue
Under New Outcome:
Label: True
Outcome API Name: True
Condition Requirements to Execute Outcome: Any Condition Is Met (OR)
Resource: {!$Record.pw_pss__NextPhoneScreenDue__c}Note: this field will be the Next Screen Due Date field which may be custom dependant on your configuration.
The decision element will now be shown in the flow and needs connecting to the start element.
Select and hold the connecter point on the Start block and drag it to the Decision element. This will create a connection between the two elements.
Now we need to add the Phone Screening element to the flow.
Select the Action Interaction and drag it under the Decision element.
In Action, search for Phone Screening and select the suggested item.
Label: Screen Phone Numbers
API Name: ScreenPhoneNumbers
ID of Record to Screen: {!$Record.Id}
Select Done.
The Screen Phone Numbers element will now be shown in the flow and needs connecting to the Decision element where the outcome is True.
Select and hold the connecter point on the Decision block and drag it to the Screen Phone Numbers element.
A modal will appear with an Outcome option. Choose True.
Select Done.
The flow is now configured and ready to Save and Activate. Repeat this process for each object that needs the functionality enabling for.
Summary of the functionality
When inserting or updating a configured record in Salesforce, this flow will now queue a task to screen the record immediately. This functionality relies on Salesforce Future Methods. Due to this dependency the results may not always appear visible immediately after record insert or update and the page may need to be refreshed before the statuses update. It is still advised to rely on the automated batch job to pick up all overdue records on its nightly run.
We know that when it comes to tasks like importing, every second counts.
That’s why we’ve released a service update for SimpleImport (20220118). Based on our customers’ usage, we found that loading speeds during the import workflow could be improved, so we’ve improved them.
Small changes influenced by your real-world usage mean big improvements. So let’s take a look at what’s changed.
A faster SimpleImport
What have we updated and what does this mean?
Scenario 1:
Loading object metadata can be costly. We may only be talking seconds, but seconds add up. That’s why we only want to load the object metadata you want to work with when it’s needed.
The solution:
SimpleImport usage revealed that users rarely wanted to import to the first object in the picklist.
As a result we removed the auto-selection of the first object displayed during object selection.
The result:
Users no longer have to wait for the first object’s metadata to load before selecting the object they actually want to import into!
Just have one object available? Don’t worry, we’ll auto-select this one for you – it’s the only option after all!
Scenario 2:
Auto-mapping fields took too long. Having to wait for this process to finish before being able to interact was just inconvenient. We strive to remove as much waiting time as possible because that’s just not productive.
The solution:
We’ve significantly optimized the auto-field mapping process to minimise the loading time on the mapping page.
The result:
The waiting time scales depending on how many fields are in the file.
We know this waiting is as a result of SimpleImport offering a helping hand, but now the hand is much, much faster!
How do I access SimpleImport Spring ’22?
Great question! This is a service update so you will automatically have access to the new workflow if you are already using SimpleImport.
If you get stuck or have any questions, feel free to contact our Support team who are more than happy to help you: support@provenworks.com.
SimpleImport
Importing files is so vital for so many organizations. It’s good news that Simplelmport makes this job as effortless as possible. Learn more and book a demo.
We are writing to confirm that no ProvenWorks solutions are affected by the Apache Log4j2 vulnerability. We do not utilize the impacted libraries for any of our packages.
To confirm, Apache Log4j does not impact any ProvenWorks solutions.
As part of our security processes and systems, we are monitoring the ongoing situation and evaluating any potential risk.
We will keep you updated with any additional information that we deem relevant to report upon in relation to ProvenWorks solutions, as it becomes available. If you have any additional questions you can reach out to us at support@provenworks.com.
We’ve now created a formula field containing the containing the conditions for screening a record, and we should also now have our phone fields configured in the Fields to Screen settings.
To add the formula field to a Field to Screen setting:
Go to App Launcher | PhoneTools Administration.
Navigate to the Configuration tab.
Select Edit next to one of the Fields to Screen rows where the formula should be applied.
Search and select the formula under Formula Field.
Press Save.
When the setting has been saved, the formula value will be updated for any configured phone field on the same object that is enabled for screening.
The time has arrived! We’re so excited to share with you the SimpleImport Winter ‘22 (20211129) Release!
With an optimized workflow, updated error messages, a nifty feature addition and a new summary page, there’s plenty to cover so let’s get started.
1. Define your Import Type
Firstly… ambiguous toggles are gone from the mapping page! SimpleImport now has a dedicated page for defining your Import Type; choose between an Insert, Update or Upsert. A new quick-to-adopt Matching Conditions query builder finds existing records when you are configuring an Update or Upsert job.
2. A mapping page, just for mapping fields!
Thanks to the dedicated Import Type page we’ve just seen, the mapping page now focuses on its key objective – mapping fields! It’s simpler than ever to map your spreadsheet columns to Salesforce fields, and the field finder has been revamped to be faster and more accurate than before.
3. Harness the power of Constant values
Are you importing products and want them all to be active? Or inserting new US accounts? Introducing Constant values. Don’t waste time duplicating data in your spreadsheet; tackle it directly on the mapping page. Hit Add Constant, map the value, and away you go!
4. Clearer error messages
Sometimes errors happen and we’ve been working hard to make our messaging as clear as possible so that you can identify the issues and work on solving them. Perhaps something is misconfigured, or required fields are missing? SimpleImport will let you know!
5. Review your import settings
Importing can be stressful so we’ve introduced a new summary page to provide an overview of the import job you’re about to submit. See your object selections, matching conditions, mapped fields and review the job estimation all in one place. Sound good? Well you can save the mapping here for future use!
6. Load and save mappings where it matters
Load mappings at the beginning of your journey, and save new ones at the end. With the import process now spread out over a couple of steps, loading a mapping at the earliest point allows you to blitz through your import task. Save a new mapping at the end of the process ensures you’ve followed all the required steps to set up your mapping how you need it.
How do I access SimpleImport Winter ’22?
Great question! This is a service update so you will automatically have access to the new workflow if you are already using SimpleImport Premium.
Anything else?
There are some additional tweaks and changes including removing the requirement to create a custom setting when configuring the ManagedImport Lightning Component. All old mappings will still work as expected. To accompany these changes, we’ve overhauled our documentation to make the transition and future adoption of the solution better than ever.
If you get stuck or have any questions, feel free to contact our Support team who are more than happy to help you: support@provenworks.com.
SimpleImport
Importing files is so vital for so many organizations. It’s good news that Simplelmport makes this job as effortless as possible. Learn more and book a demo.
PowerSearch functionality by default will search in over 245 countries up to the premise-level. Whilst powerful, this can lead to the results being diluted, especially if you know you are only working within specific countries, or have one country that you primarily work within.
To combat this, AddressTools has three settings to improve the results and customize them to your requirements.
Available Countries in PowerSearch – PowerSearch address verification will only return address results from the listed countries. All available countries will be searched if this setting is left empty. You have the ability to choose up to 80 countries.
Priority Country in PowerSearch – PowerSearch address verification will prioritize displaying results from this country.
Show Country Filter in PowerSearch – Provides a filter list to the left of the PowerSearch search bar, allowing the user to limit the search to a specific country. This can be used in combination with Available Countries in PowerSearch to provide a limited list of countries that the user can choose from.
To access these settings:
Go to App Launcher | AddressTools Administration.
Select Settings from the sidebar.
Click the pencil next to any of the settings.
In Available Countries in PowerSearch, type and select the countries that your business will be verifying addresses in.
If your organization has a country that you’d like to prioritize in the search results, select this country from the Priority Country in PowerSearch picklist.
If you would like to provide an interactive filter to the PowerSearch bar to let users search by country, check the Show Country Filter in PowerSearch.
Click Save.
Note: these three setting will only impact PowerSearch address verification. Automated address verification relies on the country value entered in an existing address.
Batch address verification alerts
Batch address verification runs behind the scenes. This can be a fantastic option to automate address verification in your organization, however errors can happen! For example when a record is verified, an update will be pushed to the record when a result has been found. If, for whatever reason, this record cannot be updated, you need to know the operation has failed!
To ensure alerts are provided in the event of an error, a dedicated email address can be added to the AddressTools settings. By default the email address of the installing user will be populated in this field but you may wish to change this.
Go to App Launcher | AddressTools Administration.
Select Settings from the sidebar.
Click the pencil next to Batch Verification Alert Email Address.
Enter the email address to send the alerts to.
Click Save.
Note: your organization may be required to change the Access to Send Email organization setting to All email. This is located in Setup | Email | Deliverability.
To provide the best experiences, we use technologies like cookies to store and/or access device information. Consenting to these technologies will allow us to process data such as browsing behavior or unique IDs on this site. Not consenting or withdrawing consent, may adversely affect certain features and functions.
Functional
Always active
The technical storage or access is strictly necessary for the legitimate purpose of enabling the use of a specific service explicitly requested by the subscriber or user, or for the sole purpose of carrying out the transmission of a communication over an electronic communications network.
Preferences
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
Statistics
The technical storage or access that is used exclusively for statistical purposes.The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
Marketing
The technical storage or access is required to create user profiles to send advertising, or to track the user on a website or across several websites for similar marketing purposes.
