Andy in the Cloud

From BBC Basic to Force.com and beyond…

Adding Clicks not Code Extensibility to your Apex with Lightning Flow

4 Comments

Building solutions on the Lightning Platform is a highly collaborative process, due to its unique ability to allow Trailblazers in a team to operate in no code, low code and/or code environments. Lightning Flow is a Salesforce native tool for no code automation and Apex is the native programming language of the platform — the code!

A flow author is able to create no-code solutions using the Cloud Flow Designer tool that can query and manipulate records, post Chatter posts, manage approvals, and even make external callouts. Conversely using Salesforce DX, the Apex developer can, of course, do all these things and more! This blog post presents a way in which two Trailblazers (Meaning a flow author and an Apex developer) can consider options that allow them to share the work in both building and maintaining a solution.

Often a flow is considered the start of a process — typically and traditionally a UI wizard or more latterly, something that is triggered when a record is updated (via Process Builder). We also know that via invocable methods, flows and processes can call Apex. What you might not know is that the reverse is also true! Just because you have decided to build a process via Apex, you can still leverage flows within that Apex code. Such flows are known as autolaunched flows, as they have no UI.

Blog_Graphic_01_v01-02_abpx5x.png

I am honored to have this blog hosted on the Salesforce Blog site.  To continue reading the rest of this blog head on over to Salesforce.com blog post here.

 

4 thoughts on “Adding Clicks not Code Extensibility to your Apex with Lightning Flow

  1. Pingback: Adding Clicks not Code Extensibility to your Apex with Lightning Flow — Andy in the Cloud – SutoCom Solutions

  2. I left a message here a few days ago and have not received a reply. My Declarative Rollup Summary app in Salesforce is not working and Salesforce is not able to help and has sent me to this website. The Error is
    Error:
    Salesforce Metadata API connection failure, click the link below to configure.
    Would love to get a response.

  3. I decided to give Process Builder yet another chance to become a centerpiece of the logic and ran into the following issues:
    1) I created an invocable method to lock the records that accepts list of string as input, but Process Builder fails when I submit RecordId as Apex Variable for the method – how do I suppose to create a list in the Process Builder to bulkify it?
    2) In your FilterAccounts Flow example SomeRecords is SObject Variable – shouldn’t it be SObject Collection Variable to go thru a loop? How does Flow bulkification work?
    3) In my Flow (called from Process Builder) I set Stage Completion dates values on Stage change, but I also have to erase date values if Stage is downgraded. Assigning blank value to the date field does nothing, as well as assigning a date constant or variable with an empty default values – how it can be done in a Flow?

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s