Author: zeusexam

Criteria definition This is the process of matching criteria to make the Process Builder execute the actions group that has been defined for that criteria. Let’s see how we can do this. To add the criteria, click on + Add Criteria: Criteria definition Criteria are defined by the following three things, as shown in the…

Defining action groups So far, we’ve seen how we can configure a Process Builder so that it’s triggered by conditions on the fields of its triggering record. This is the IF part of the tool. Now, we want to talk about the THEN part, that is, the actions that the automation should execute in response…

Creating records Select an object type and manually define the mapping for its fields: Record creation action Mandatory fields appear automatically on the form. You can use the current record’s related object to set field values. Updating records In workflows, we used to create field update actions to update record fields and the parent’s fields…

Email alerts Like workflows, with approvals and entitlements, you can send emails using Email Alerts actions. This is shown in the following screenshot: Email alert action Simply select an email alert that’s already on the system (remember that your organization can send 1,000 email alerts per standard Salesforce license (up to 2,000,000 in total)). Submitting…

Custom notifications Custom notifications are a great introduction to the summer 2019 release of Salesforce. Here, you can define custom notifications that can be sent to users via mobile or desktop. To define a custom notification, go to Setup | Notification Builder | Notification Types and click the New button, as shown in the following…

Final considerations for building with a Process Builder Before closing this chapter, let’s look at the things we need to take into consideration when building automation using a Process Builder. The first suggestion is to use one automation tool for each object because it becomes very difficult to predict when actions will take place if…

Lightning Flows Lightning flows collect data and perform actions in your Salesforce organization or external system. Their configuration requires point-and click -interactions; no code is required. In this chapter, we will look at screen flows, which collect data from agents or customers (for example, tutorials or wizards), and autolaunched flows, which automatically execute data logic…

Building a flow Let’s build a simple screen flow so that we can gather contact and account data from the user’s interactions by using the Cloud Flow Designer (this is the new version of the old Flow Builder app and was introduced in Spring 2019). This is shown in the following screenshot: Cloud Flow Designer…

But why do you need to do this? You may want to get the component’s initial values from the previous elements, which may have stored another kind of data. In our scenario, we are doing this so that we can go from the input screen to the verification screen and back without losing the data…

Create a new screen element called account details with the following components: The following screenshot shows the screen element’s account details: Account details for the screen element Have you noticed that none of the components have the Set Output Values attribute section? This is because these are simple components that do not convey complex logic….