Welcome back to the Salesforce Flow series!
In the previous post, we learned what Flow is and explored the different types of Flows available in Salesforce.

In this post, we’ll stop talking theory and start building something real.

We’ll create our first Record-Triggered Flow, step by step, using a simple and practical business scenario. No assumptions. No shortcuts. Just clean learning.

🎯 Our Scenario (Simple & Realistic)

Let’s say your business has this requirement:

“Whenever an Opportunity is marked as Closed Won, automatically create a follow-up Task for the Opportunity Owner.”

This is a very common real-world requirement and a perfect starting point for learning Flow.

🧠 What We Will Build in This Blog

By the end of this post, you’ll have a Flow that:

• Runs when an Opportunity is updated

• Checks if the Stage is Closed Won

• Automatically creates a Task for the Opportunity Owner

We will build this using:

• Record-Triggered Flow

• Decision Element

• Create Records element

  Subscribe now

🧠 Visual flow

Opportunity Updated
        ↓
Stage = Closed Won?
        ↓
      YES
        ↓
Create Follow-Up Task

🧩 Step 1: Create a New Flow

1. Go to Setup → Flows

2. Click New Flow

3. Select Record-Triggered Flow

4. Click Create

You are now inside the Flow Builder.

🧭 Step 2: Configure the Trigger

This is where you tell Salesforce when your Flow should run.

Configure Trigger Settings:

• Object: Opportunity

• Trigger the Flow When:

  • A record is created or updated

• Condition Requirements:

  • Stage Equals Closed Won

• When to Run the Flow:

  • Only when a record is updated to meet the condition requirements

• Optimize the Flow For:

  • Actions and Related Records

📌 Why this setting?
Because we want the Flow to run only once, when the Opportunity becomes Closed Won and we plan to create a related Task.

🔀 Step 3: Add a Decision Element (Optional but Recommended)

Even though we already set entry criteria, adding a Decision makes your Flow more readable and flexible.

Decision: “Is Opportunity Closed Won?”

Condition:

• Opportunity.StageName Equals Closed Won

This also helps if you want to reuse the Flow later with additional conditions.

🛠️ Step 4: Create a Task Record

Now we’ll add the real automation.

Add Element → Create Records

Label: Create Follow-Up Task

How to set record field values?
→ Manually

Set Field Values:

• Subject: Follow up on Closed Opportunity

• Assigned To Id: Opportunity Owner

• Related To Id: Opportunity Id

• Status: Not Started

• Priority: Normal

This task will now automatically appear for the Opportunity owner whenever the deal is closed.

🔄 Step 5: Connect the Flow

Your flow should now look like this:

Start (Opportunity Updated)
        ↓
Decision: Is Closed Won?
        ↓
Create Task

Clean. Simple. Powerful.

🧪 Step 6: Save & Test the Flow

1. Click Save

2. Flow Label - Opportunity Task Creation

3. Click Debug

4. Select an Opportunity

5. Change Stage to Closed Won

6. Run the Flow

7. Verify:

   • It goes through the correct path to create task

If everything looks good — Activate the Flow 🎉

🧠 What You Learned in This Blog

✔ How to create a Record-Triggered Flow
✔ How to use entry conditions
✔ How to use Decision elements
✔ How to create records automatically
✔ How real-world automation works

This is the foundation of almost every Salesforce automation.

🚀 What’s Coming Next

In the next blog, we’ll level up this same Flow by adding:

• Fast Field Updates vs Actions

• Using Get Records to fetch related data

• Handling multiple conditions properly

• Improving performance and readability

We’ll keep building on this same example so nothing feels disconnected.

💬 Final Note

If you’re learning Salesforce Flow, don’t rush it.
Mastering Flow is less about memorizing features and more about thinking logically.

In the next post, we’ll make this Flow smarter and more efficient.

👉 Stay tuned for Part 3: Optimizing Your First Flow
📌 Follow Salesforce Hacks for the full series.

Subscribe now

If you’re new to Flow, this blog is your starting point.

In this post, we’ll cover:

• What Salesforce Flow is

• The different types of Flows

• When to use each type

• How this blog series will build a real Flow step by step

This is Part 1 of a Flow learning series, designed to take you from absolute basics to real-world automation use cases.

What is Salesforce Flow?

Salesforce Flow is a declarative automation tool that allows you to build business logic using a visual, drag-and-drop interface, without writing code.

With Flow, you can:

• Automate record updates

• Create or delete related records

• Guide users with interactive screens

• Schedule actions to run later

• Replace complex Process Builder logic

In simple terms, Flow lets you tell Salesforce what to do, when to do it, and how to do it, all visually.

Salesforce is investing heavily in Flow, and it has become the recommended solution for almost all automation scenarios.

Why Learn Flow?

Learning Flow is no longer optional if you work with Salesforce.

Some key reasons:

• Workflow Rules and Process Builder are being retired

• Flow supports more complex logic than older tools

• It works for Admins, Consultants, and Developers

• Most real-world business requirements can be handled using Flow alone

Whether you’re preparing for certifications or working on production orgs, Flow is a core skill.

Types of Salesforce Flows

Salesforce offers multiple Flow types, each designed for specific scenarios. Understanding when to use which Flow is the first step toward mastering automation.

1. Record-Triggered Flow

A Record-Triggered Flow runs automatically when a record is:

• Created

• Updated

• Deleted

You don’t need user interaction for this Flow. It reacts to data changes in the system.

Common use cases:

• Update fields when a record is saved

• Create related records automatically

• Enforce business rules

• Send notifications after record updates

This is one of the most commonly used Flow types and often replaces Workflow Rules and Process Builder.

2. Scheduled-Triggered Flow

A Scheduled-Triggered Flow runs at a specific time and frequency, based on a record condition.

Instead of reacting immediately, this Flow checks records on a schedule, such as:

• Daily

• Weekly

• Monthly

Common use cases:

• Contract or subscription renewal reminders

• Data cleanup jobs

• Escalations based on time

• Follow-up emails

This Flow is ideal when automation depends on time, not user actions.

3. Screen Flow

A Screen Flow includes user-facing screens where users can enter or review data.

These Flows are interactive and are often launched from:

• Buttons

• Links

• Lightning pages

• Utility bars

Common use cases:

• Guided record creation

• Support or service request forms

• Step-by-step onboarding processes

• Custom wizards

Screen Flows are powerful because they combine automation with user input.

4. Auto-Launched Flow

An Auto-Launched Flow runs in the background without any user interface.

It is usually triggered by:

• Another Flow (Subflow)

• Apex code

• Process Builder (legacy use)

Common use cases:

• Reusable business logic

• Shared calculations

• Backend automation

Auto-Launched Flows help keep your automation modular and maintainable.

5. Platform Event–Triggered Flow (Optional Awareness)

A Platform Event–Triggered Flow runs when a platform event message is received.

This is commonly used in:

• System integrations

• Event-driven architectures

While powerful, this Flow type is typically used in advanced scenarios and won’t be the focus of this beginner series.

How This Flow Series Will Work

Instead of showing isolated examples, this blog series will follow one evolving business scenario.

Each new post will build on top of the Flow created in the previous article, just like real projects.

By the end of the series, you’ll have a complete, realistic Flow that includes:

• Record automation

• Decisions and conditions

• Loops and collections

• Scheduled actions

• Reusable subflows

• Error handling

This approach helps you understand not just how Flow elements work, but why and when to use them.

Upcoming Blog Posts in This Series

Here’s what we’ll cover step by step:

1. Salesforce Flow Basics (This Post)
   Understanding Flow types and when to use them

2. Creating Your First Record-Triggered Flow
   Entry conditions, before vs after save, and basic logic

3. Fast Field Updates vs Actions and Related Records
   Performance considerations and best practices

4. Using Decisions and Assignments Effectively
   Implementing business rules the right way

5. Working with Get Records, Create, Update, and Delete
   Handling data safely and efficiently

6. Loops and Collection Operations Explained
   Filters, sorting, and transforming data

7. Scheduled Paths and Scheduled Flows
   Time-based automation done correctly

8. Subflows and Reusable Logic
   Building clean, modular automation

9. Error Handling and Custom Errors in Flow
   Making Flows user-friendly and production-ready

10. Putting It All Together: A Complete Real-World Flow
    End-to-end automation using everything learned

What’s Next?

In the next blog post, we’ll start building our first Flow:

• A simple Record-Triggered Flow

• Clear entry criteria

• Basic automation logic

If you’re serious about mastering Salesforce automation, bookmark this series and follow along step by step.

Requirement

We need to ensure that whenever an account's phone number is updated, all contacts linked to that account have their phone numbers updated to match the new account phone number.

Steps to Create the Flow

Let's break down the steps to create this flow:

1. Create a Record-Triggered Flow

2. Configure Entry Conditions

3. Fetch Related Contacts

4. Loop Through Contacts

5. Update Contact Records

Step-by-Step Guide

1. Create a Record-Triggered Flow

First, we need to create a new flow that triggers when a record is updated.

• Navigate to Setup.

• In the Quick Find box, type Flows, and select Flows.

• Click New Flow.

• Select Record-Triggered Flow and click Create.

2. Configure Entry Conditions

Next, we need to specify the conditions that trigger this flow.

• In the Configure Start screen, select Object as Account.

• Set the Trigger to A record is updated.

• Under Entry Conditions, select Conditions are met.

• Add a condition: Phone Is Changed Equals True.

• Ensure the Condition Requirements are set to All Conditions Are Met (AND).

• Click Done.

3. Fetch Related Contacts

We now need to fetch all contacts associated with the account whose phone number was updated.

• Click the + icon and select Get Records.

• Label this element as Get Contacts.

• In the Object field, select Contact.

• Set the Filter Contact Records conditions to:

  • AccountId Equals {!$Record.Id}

• Store all records in a variable, and ensure Automatically store all fields is selected.

• Click Done.

4. Loop Through Contacts

To update each contact’s phone number, we’ll use a loop.

• Click the + icon and select Loop.

• Select the Collection Variable containing the contacts fetched by the previous element.

• Choose to Iterate Through the collection.

• Click Done.

Within this loop, we’ll set the contact phone number to the account phone number.

• Inside the loop, click the + icon and select Assignment.

• Label this element as Set Contact Phone Number.

• Assign the contact phone number to the account phone number.

• Create a collection and add the current loop record to the collection after assigning the phone number to the contact.

• Click Done.

5. Update Contact Records

Finally, we’ll update all contact records outside of the loop.

Click the + icon and select Update Records.

• Label this element as Update Contacts.

• Set the How to Find Records to Update to Use the IDs and all field values from a record or record collection.

• Select the collection variable containing the contacts to update.

• Click Done.

Subscribe now

Conclusion

Your flow should now be complete and look something like this:

1. Start (Triggered when an Account record is updated and the phone number has changed)

2. Get Contacts (Fetch all contacts related to the account)

3. Loop Through Contacts (Iterate through each contact)

4. Set Contact Phone Number (Assign the new phone number to each contact)

5. Add Contacts to Collection (Prepare contacts for bulk update)

6. Update Contacts (Update all contact records with the new phone number)

Activate your flow and test it by updating an account’s phone number. You should see the phone numbers of all associated contacts update automatically.

That’s it for today’s guide on updating records using Salesforce Flow. Stay tuned for more insights and tutorials in our Salesforce Flow series!

Share

The Requirement:

Our goal is straightforward: create a Contact record using a Screen Flow. Additionally, we'll add this flow into the Account lightning record page, ensuring users can effortlessly add contacts to associated accounts.

Step-by-Step Guide

Let's walk through the process:

1. Create a New Screen Flow: Navigate to Flows, click on "New Flow," and select "Screen Flow" as the flow type.

2. Design the Screen Layout: Add a screen action and drag relevant sections onto the flow canvas to display contact creation fields to users. In this case, we include fields like Name, Phone, and Email.

   

3. Configure Record Creation Component: Add the "Create Records" component to the flow. Specify the object (Contact) and map the values entered by the user from the previous screen component to the corresponding contact fields.

   

4. Mapping the Account: To associate the newly created contact with the account, create a resource with the text data type and mark it as "Available for input." This allows passing the Account ID from the lightning record page to the flow.

   

5. Save and Activate the Flow: Once the flow is designed and configured, save it and activate it for use.

6. Integrate with the Account Lightning Record Page: Edit the Account record page, drag the Flow component onto the desired location, select the checkbox “Pass record ID into this variable“ and save the page.

   

7. Test the Flow: Return to the Account record page, enter the required contact details in the flow, and proceed. Verify that the new contact is successfully created and associated with the Account.

By following these simple yet powerful steps, you can leverage Salesforce flows to streamline the process of creating records. Integrating flows directly into record pages enhances user experience and efficiency, empowering your team to accomplish tasks seamlessly within the Salesforce environment.

Stay tuned for more insightful tutorials and real-world use cases in our ongoing Salesforce Flow Series. Have questions or need further assistance? Feel free to reach out – we're here to help!

Subscribe now

Share

What are Flows and their Benefits?

Salesforce Flows are sequences of screens and/or actions that guide users through a business process or application. They can automate complex business processes, streamline data entry, and interact with users in a more engaging way than traditional workflows. Some key benefits of using Flows include:

• Automation: Flows automate repetitive tasks, reducing manual effort and increasing efficiency.

• Customization: They allow for highly customizable processes tailored to specific business needs.

• User Interaction: Flows can engage users with interactive screens and guided experiences.

• Data Manipulation: They enable manipulation and transformation of data within Salesforce.

• Integration: Flows can integrate with other Salesforce features and external systems.

Types of Flows

Salesforce offers several types of Flows, each serving different purposes. Here's a brief overview of the most common types:

1. Screen Flow

Screen Flows are user-guided flows where users interact with screens to input data or make selections. They are ideal for creating wizards, guided processes, or collecting user input.

2. Record-Triggered Flow

Record-Triggered Flows are automated processes triggered by changes to records in Salesforce. They allow for advanced automation based on record changes, such as updating related records or sending notifications.

3. Auto-Launched Flow

Auto-Launched Flows are flows that run in the background without user interaction. They are typically triggered by external events or scheduled to run at specific times.

4. Schedule-Triggered Flow

Schedule-Triggered Flows are flows that are scheduled to run at specific times or intervals. They are useful for batch processing tasks or recurring automation.

Building Your First Flow: A Personalized Greeting

Let's get hands-on! In this example, we'll create a Screen Flow that displays a personalized greeting message for users on the App homepage.

1. Create a Screen Flow: Head to Flow Builder and create a new Screen Flow.

2. Design Your Greeting Screen: Add a "Display Text" element to showcase your message.

3. Get Personal: Want to greet users by name? Use Flow Variables! Add a "Get User Information" element to retrieve the user's first name and store it in a variable. Then, incorporate the variable within your greeting message using dynamic text.

4. Save and Run: Save your Flow and test it out!

Bonus Tip: To display the Flow on your App homepage, navigate to the App Manager, edit your App, and add the Flow as a component.

Ready to Flow?

This is just the first step in your Salesforce Flow journey. Stay tuned for future articles where we'll delve deeper into different Flow types, explore advanced functionalities, and uncover real-world use cases to unlock the full potential of Flows in your Salesforce experience!

P.S. Check out the accompanying video for a visual walkthrough of building the personalized greeting Flow!

Share

Subscribe now

Steps to Implement Flow Repeater Component: Let's delve into the step-by-step process of incorporating the Flow Repeater component into your Salesforce workflows:

1. Create a New Screen Flow: Begin by creating a new screen flow in Salesforce. Screen flows are powerful tools that guide users through a series of screens to collect and manipulate data.

2. Add the Repeater Component Inside the Screen Component: Within the screen flow, add the Repeater component to the desired screen. This component acts as a container for repeating sets of fields, allowing users to input data for multiple records within a single screen.

3. Utilize Loop to Iterate Through Entries: Implement a loop within the flow to iterate through all the entries made by the user using the Repeater component. This loop ensures that each entry is processed effectively, enabling seamless data handling.

4. Utilize Assignment and Collection to Store Entries: Leverage assignment and collection elements within the flow to store all the entries made by the user. This step is crucial for maintaining data integrity and ensuring that no information is lost during the process.

5. Use the Create Element to Generate Related Records: Finally, utilize the create element within the flow to generate all the related records based on the entries provided by the user. This element enables the creation of new records in Salesforce, facilitating seamless data management.

You can view the YouTube video with all the steps to create the above flow.

Benefits of Flow Repeater Component: The Flow Repeater component offers several advantages for Salesforce users:

• Improved User Experience: By streamlining data entry, the Repeater component enhances the user experience, particularly in scenarios where users need to create multiple records with similar data.

• Increased Efficiency: Users can input data for multiple records at once, saving time and reducing the number of steps required to complete a process.

• Enhanced Code Readability: The Repeater component helps maintain code organization and readability by grouping related fields together, leading to more comprehensible and maintainable flows.

Limitations of Flow Repeater Component: While the Flow Repeater component introduces significant benefits, it's essential to consider its limitations:

• Beta Stage: As a beta feature, the Repeater component may have limited functionality and stability compared to fully released components. Users should exercise caution when implementing it in production environments.

• Supported Input Components: Not all standard input components are currently supported within the Repeater component. Users should verify compatibility with their specific use cases before implementation.

In conclusion, the Flow Repeater component represents a major advancement in Salesforce's commitment to enhancing user productivity and experience. By simplifying and accelerating the data entry process, this feature empowers organizations to achieve greater efficiency and effectiveness in their Salesforce workflows. As with any new feature, it's essential for users to explore its capabilities, consider its limitations, and evaluate its suitability for their unique business needs. With careful planning and implementation, the Flow Repeater component holds the potential to revolutionize data management processes within Salesforce environments.

Subscribe now

Share

• More flexibility: Flows are more flexible than Workflow Rules and Process Builder, allowing you to create more complex and dynamic processes.

• Better user experience: Flows can provide a better user experience by allowing you to interact with them through screen elements.

• More powerful features: Flows offer a wider range of features than Workflow Rules and Process Builder, such as decision elements, branching, and loops.

Benefits of Transitioning to Salesforce Flows

There are a number of benefits to transitioning to Salesforce Flows, including:

• Increased automation: Flows can help you automate more of your business processes, which can free up your time and resources for other tasks.

• Improved user experience: Flows can provide a better user experience for your customers and employees, by making it easier for them to interact with your Salesforce data.

• Enhanced scalability: Flows are more scalable than Workflow Rules and Process Builder, making them a better choice for organizations that need to automate large or complex processes.

Best Practices for Converting Workflow Rules and Process Builder to Salesforce Flows

Here are some best practices for converting Workflow Rules and Process Builder to Salesforce Flows:

1. Understand your current processes. Before you start converting your processes, it's important to understand how they work. This includes documenting the rules, criteria, and actions that are used in each process.

2. Define your objectives and requirements. What do you want to achieve by converting your processes to Flows? Once you know your objectives, you can start to plan the conversion.

3. Identify complex processes and limitations. Some processes may be more difficult to convert to Flows than others. Identify any potential limitations and develop strategies for working around them.

4. Start with simple conversions. It's a good idea to start with simple conversions when you're first getting started with Flows. This will help you learn the basics and build your confidence.

5. Implement decision elements. Decision elements can be used to replace criteria-based evaluations in Workflow Rules and Process Builder. This can make your processes more dynamic and adaptive.

6. Leverage screen elements for user interaction. Screen elements can be used to provide an interactive user experience in Salesforce Flows. This can make your processes more user-friendly and engaging.

7. Modularize your Flows. Modularizing your Flows can make them easier to maintain and update. It can also make them easier to reuse for different purposes.

8. Test thoroughly. It's important to test your Flows thoroughly before you put them into production. This will help you identify any errors or unexpected behavior.

9. Monitor and optimize. Once your Flows are in production, you should monitor their performance and collect user feedback. This will help you identify areas for improvement.

Transitioning to Salesforce Flows can be a complex process, but it can also be a rewarding one. By following the best practices outlined in this blog post, you can successfully convert your existing processes and create seamless, user-friendly automation processes using Salesforce Flows.

I hope this detailed blog post is helpful. Please let me know if you have any other questions.

Share

Scan Flow: Identifying Potential Issues and Optimizations

The Lightning Flow Scanner extension offers a "Scan Flow" command that thoroughly examines all the flows in your Salesforce org. This scan enables the identification of potential issues and optimization opportunities. By analyzing various aspects of your flows, the Lightning Flow Scanner helps streamline your development process and improve overall performance.

Fix Flows: This command helps to apply the available fixes automatically

"Fix Flows" command of the Lightning Flow Scanner extension provides a convenient and automated way to apply the available fixes to your flows. It helps streamline the optimization and refactoring process, ensuring that your flows adhere to best practices and perform at their best.

Flow Rules: Comprehensive Overview and Documentation

In addition to its scanning capabilities, the Lightning Flow Scanner provides a "Flow Rules" command. This command offers an overview of all the available rules, their relevant documentation, and even the source

We can configure this extension to look for these items:

1. DML Statements in a Loop:

The Lightning Flow Scanner scrutinizes your flows to identify any DML (Data Manipulation Language) statements executed within loops. Executing DML statements, such as inserts or updates, inside loops can lead to performance issues, inefficient resource usage, and potential governor limit exceptions. The tool flags such instances, allowing you to refactor your flows for optimal execution.

2. Duplicate DML Operations:

Another important aspect the Lightning Flow Scanner evaluates is the presence of duplicate DML operations within your flows. Duplicate DML operations can lead to unnecessary database calls and result in inefficient data processing. By identifying these duplications, the tool helps you eliminate redundant operations, improving the efficiency and performance of your flows.

3. Hardcoded IDs:

Hardcoding IDs in flows can make them less flexible and harder to maintain. The Lightning Flow Scanner searches for instances where IDs are hardcoded and provides suggestions to replace them with dynamic variables or merge fields. This approach makes your flows more adaptable and future-proof, ensuring that they can be easily deployed across different environments without requiring manual modifications.

4. Missing Flow Description:

Maintaining proper documentation is essential for any development project. The Lightning Flow Scanner examines your flows to identify any missing or incomplete flow descriptions. It reminds you to provide comprehensive descriptions for your flows, improving the overall clarity and maintainability of your Salesforce processes.

5. Missing Error Handlers:

Error handling is crucial in any application, and flows are no exception. The Lightning Flow Scanner scans your flows for missing error handlers. It points out any areas where error handling mechanisms, such as fault connectors or subflows, are absent. By addressing these gaps, you ensure that your flows gracefully handle exceptions and provide a better user experience.

6. Missing Null Handlers:

Null values can cause unexpected behavior and errors within flows. The Lightning Flow Scanner detects instances where null handling mechanisms are missing. It helps you identify areas where null checks or default value assignments should be included, enabling you to handle null values effectively and prevent potential flow failures.

7. Unconnected Elements:

Unused or unconnected elements within flows can clutter your design and make them harder to understand. The Lightning Flow Scanner identifies any unconnected elements, such as screens, decisions, or assignments, that are not part of the flow's execution path. This feature assists in decluttering and simplifying your flows, enhancing their readability and maintainability.

8. Unused Variables:

Over time, flows may accumulate unused variables, impacting their performance and clarity. The Lightning Flow Scanner scans your flows to detect any variables that are declared but remain unused. By highlighting these variables, the tool helps you clean up your flow's workspace, removing unnecessary clutter and ensuring optimal execution.

The developer of this remarkable extension is Ruben Halman.. If you have any suggestions or questions, please feel free to reach out to him.

Share

Subscribe now

Requirements: To create our mortgage monthly payment calculator app, we will need the following user inputs:

1. Loan Amount: The total amount of the mortgage loan.

2. Term Years: The number of years for the mortgage term.

3. Months: This field should auto-populate based on the Term Years field.

4. Interest: The annual interest rate for the mortgage.

5. Monthly Payment: This field should automatically display the calculated monthly payment.

Step 1: Create a Screen Flow with Reactive Screen Components To start building our app, we'll create a screen flow using Salesforce's Flow Builder. Open the Flow Builder and add reactive screen components such as input fields, formulas, and variables to capture and manipulate the data. Design the flow to guide the user through the mortgage calculation process.

Step 2: Create a New Lightning App Next, let's create a new Lightning App that will serve as the container for our mortgage calculator. In the Salesforce Setup, navigate to "App Manager" and click on "New Lightning App." Customize the app's branding, navigation, and add any desired features to enhance the user experience.

Step 3: Create a New Lightning Record Page and Add the Screen Flow To integrate our screen flow into the Lightning App, we'll create a new Lightning record page. In the Salesforce Setup, go to "Lightning App Builder" and create a new record page. Drag and drop the screen flow component onto the page layout, positioning it appropriately for a seamless user experience.

Step 4: Assign the Lightning Page to the App Once the Lightning record page is ready, assign it to the Lightning App we created earlier. In the Salesforce Setup, navigate to "App Manager," select the app, and edit its properties. Set the newly created record page as the default page for the app, ensuring that users are presented with the mortgage calculator upon launching the app.

Step 5: Activate and Test the App Before making the app available to users, activate it to ensure that all the components, pages, and flows are functional and accessible. Go to the App Manager, select the app, and click on "Manage Profiles" to assign appropriate user profiles that should have access to the app.

Once activated, log in as a user with the assigned profile, navigate to the App Launcher, and launch the new mortgage calculator app. Test the app thoroughly by entering different loan amounts, term years, and interest rates, and verify that the monthly payment field updates correctly based on the calculations performed by the screen flow.

Let me know if you have any questions. I will be happy to help.

1. General availability of Choice Lookup component: The Choice Lookup component is now generally available, making it easier to create flows that allow users to select from a list of choices.

   • For example, you could use the Choice Lookup component to create a flow that allows users to select a color of the product to purchase.

2. Add a search bar to Data Table: You can now add a search bar to the Data Table component, making it easier to find the data you need.

   1. For example, you could add a search bar to the Data Table component to make it easier to find a customer record.

3. Reactive Screen Components support Formulas: Reactive Screen Components now support Formulas, making it easier to create dynamic and interactive flows.

   1. For example, you could use Reactive Screen Components to create a flow that allows users to customize their experience.

4. Send Email Core Action is Improved: The Send Email Core Action in Salesforce Flow has been improved in the Summer '23 release. It can now use email templates (Lightning Email Templates are supported as well), and it can log the email on the specified records' activity timelines. To use these new features, you will need to specify the Recipient ID, Related Record ID, and Template ID when setting up the Send Email action. These values are essential for populating the merge fields of the template.

   Here are some additional details about the new features:

   • Email Templates: You can now use lightning email templates when sending emails from Flow. This makes it easy to create consistent and professional-looking emails.

   • Log email on Send: The email will now be logged on the specified records' activity timelines. This makes it easy to track email communication with your customers and prospects.

   • Recipient ID: The Recipient ID is the ID of the user or contact who will receive the email.

   • Related Record ID: The Related Record ID is the ID of the record that is associated with the email.

   • Email Template ID: The Template ID is the ID of the lightning email template that you want to use.

     

5. Changes on the user interface: There are some changes on the user interface of the flow builder, making it easier to use.

   Old look New look

Subscribe now

Share

Leave a comment