This article explains how to use Salesforce Screen Flow to open a record in a console sub-tab. By creating a text template that includes the record’s ID and using a display text component, users can click a link that opens the record within the console rather than a new browser tab. Two key steps are involved: (1) creating the text template with the record ID, and (2) displaying the template in the flow using the “Display Text” component.
Category: Flow
This articles leverages a lightning web component to export the data from Salesforce screen flow. The LWC inputs a collection variable and convert it into a CSV file. Moreover, you also have options to select an sObject and fields to be exported into the CSV file.
This class can be used in flows to send emails programmatically without needing predefined email alerts.
It allows customization of email content, recipients, and attachments on the fly. The Apex class is designed to send emails from Salesforce without the need for an Email Alert.
This article shows, how to preview an email in a screen flow with actual merge fields populated before sending it out to a customer, ensuring all details are correct. By using an Apex invocable action that returns email body with all the merge fields populated and in the screen flow show text using display text component and HTML body using an LWC.
This article provides a workaround for an issue encountered with the BR() function in Salesforce flow formulas. Instead of generating a line break, the BR() function outputs the br tag.
This article provides step-by-step instructions to help you set up an automation using Change Data Capture, Flow and Apex trigger to update the lead Owner, when a lead is assigned to a Specific cadence. The apex trigger listens for new events on the ActionCadenceTrackerChangeEvent object, and when a Lead is targeted by a specific cadence (‘my test cadence’), it triggers a Flow to update the lead owner with the cadence assignee.
This article walks you through creating a validation rule using a record trigger flow instead of using apex code for complex business requirements. Sometimes we have requirements that can not be accomplished using standard validation rules. So you can use this approach instead of developing before insert apex trigger.
This articles covers a business requirement that before an opportunity is marked as closed won, the opportunity must have at least one contact role.
Recently I was working on Salesforce – Asana integration project using Asana API in apex. It works fine by creating asana tasks, sub-tasks, etc. using normal API requests. But when it comes to uploading files as attachments to Asana consuming API, I was stuck. Because it requires the file data to be encoded in some special format with the multipart/form-data.
When you update a multi-picklist field’s value using flow, the existing values are lost. This article walks you through updating the multi-select picklist field’s value using flow without losing existing values.
A solution to upload files from the same screen from where you get the record information from the end user.
DESCRIPTION: You want to record the data for the visitors that visit the Salesforce record pages. We can easily achieve this using screen flow with a few simple steps. SOLUTION: Create a custom object “Record Visitor” with the following fields. Object Name (text) Record Id (text) User (Lookup to user…
Deactivate an account record if it has no “Closed Won” Opportunity for 180 days or no opportunity created in 180 days.
Send the most recent Quote PDF attached to the email alert using Salesforce Flow