Spring'19 is here! - Customization

In this post, I am highlighting major customization features released in Spring'19

Customizations

Einstein Next Best Action: Use Strategies to Recommend Actions and Offers (Generally Available)

Display the right recommendations, at the right moment, to the right people with Einstein Next Best Action. Integrate business rules, predictive models, and data—both inside and outside of Salesforce—to create unique strategies for all your use cases. Maybe you have offers, like discounts and upgrades, that are only relevant under specific conditions. Perhaps service agents have multiple ways to assist customers, and you want to guide the agent to the best action. Consider using Einstein Next Best Action.

Build an Action Strategy to Produce Recommended Actions and Offers

Use Strategy Builder to create a stream of actions and offers that you can display on Lightning record pages and Community pages. Strategy Builder is a point-and-click automation tool for creating strategies for Einstein Next Best Action. With Strategy Builder, you can sort, filter, and prioritize your recommendations.

Build Flows More Intuitively with Flow Builder

Your flow-building experience just got a whole lot better! Salesforce replaced Cloud Flow Designer with a much faster tool: Flow Builder. It streamlines flow building and maintenance with a simplified user interface.

With Flow Builder, Salesforce streamlined the toolbox, so it’s easier to choose the right element or resource for your flow. For example, Salesforce consolidated the data elements and how you create variables. No more keeping track of whether to use a Fast Create or Record Create, or which type of variable you need. Salesforce also renamed some elements and resources to be more intuitive. For example, the sObject data type is now called “Record.”

Respond to Salesforce Errors with Processes or Flows

Processes and flows now support standard platform events that the Salesforce Platform provides for you. Both Batch Apex Platform Event (BatchApexErrorEvent) and Platform Status Alert Event (PlatformStatusAlertEvent) capture information about errors in Salesforce. Just like with custom platform events, you can start a process or resume a flow when event messages are received for these standard platform events. Previously, the only platform events that processes and flows supported were custom ones.

Display an Image and Capture Address Information More Easily in Your Flows

Two new screen components improve your flows. Use the Display Image component to insert images in flow screens. Use the Address component to display a complete address form that’s customized to your settings

Fine-Tune Your Data Privacy Tracking with New Objects

Track data privacy preferences in more a granular way using new objects: Contact Point Type Consent, Data Use Purpose, and Data Use Legal Basis. For example, you can indicate that a customer allows contact via email but not through phone calls and mail. You can also set up categories to specify the purpose for which contact is legitimate, such as billing. And you can specify the legal basis for contacting someone against their wishes.

Create Custom Big Objects from Setup

A big object stores and manages a massive amount of data natively on the Salesforce platform. You can archive data from other objects or bring massive datasets from outside systems into a big object to get a full view of your customers. Big objects provide consistent performance, whether you have 1 million records, 100 million, or even 1 billion. Previously, creating a big object required using Metadata API. But now, if you aren’t comfortable using the API, you can create a big object in Setup, define its fields, and build the index that defines how the big object is queried.

From Setup, enter Big Objects in the Quick Find box, then select Big Objects. Click New, and the wizard guides you through the steps.

Create Objects from Spreadsheets

Now with a few clicks, you can create a custom object by importing its fields and field data from a Google sheet, a Quip spreadsheet, an .xls file, or a .csv file. Not only can you create an object and its fields quickly, but when you’re done, all its data is there, too.

Check a Field’s References Before You Edit It (Beta)

Create an Identity-First Login Page with My Domain Login Discovery

Configure My Domain with Login Discovery to simplify the login process for users. This login process is sometimes called interview-based or identity-first login. Instead of requiring users to login with a username and password, My Domain Login Discovery page prompts them to enter a unique identifier such as an email address or phone number. Then users are prompted to authenticate based on the identifier they supply. If they’re configured for SSO, they don’t even have to choose. My Domain Login Discovery sends them directly to the identity provider (IdP) login page to authenticate.

Create Your Own Verify Page for Community Sign-Ups

When users sign up for your community with an email address or phone number, Salesforce sends them a verification code and generates the Verify page. The Verify page is where users confirm their identity. Previously, you could brand the page with your logo, colors, and background, but you couldn’t change the form, which comes from Salesforce. Now you can replace the Salesforce Verify page with your own page that you create using Visualforce and a couple of Apex methods

To know more about it, go to this link.

Send Asynchronous Email Verifications

The new Salesforce Identity asynchronous email feature lets users verify their email address at any time. You send users a verification link in an email message. Users can verify their email address by clicking the link when it’s convenient. No need to stop what they’re doing. You can also customize the email message so that users recognize your brand.

Example

System.UserManagement.sendAsyncEmailConfirmation('005RM000001a0Ox', '00XRM000000hxnG', '0DBRM000000015i', '/s/contactsupport');

Get More Security with a Refreshed Password Blacklist

We refreshed the password blacklist to give your org added security. For example, users can no longer use the string “1234567” to log in to your org.