Flow

Flow Local Actions Using Lightning Components

By Raj Vakati December 2, 2018 Flow, Lightning 0 Comments

Flow Local Actions Using Lightning Components allow you to execute client-side logic in your flow, build or modify custom Lightning components to use as local actions in flows. For example, get data from third-party systems without going through the Salesforce server, or open a URL in another browser tab. Once you configure the Lightning component’s markup, client-side controller, and design resource, it appears in the Cloud Flow Designer as a Local Action element. In this example, the input screen on the flow will take a country name and from there invoke the local action and return the country information from the web service.

How to add Flow Local Actions

Add the lightning:availableForFlowActions interface to a Lightning component to make it available as a flow action. When a component is executed as a flow action, the flow calls the invoke method in the client-side controller. Flows that include Lightning components are supported only in Lightning runtime. Lightning components that implement lightning:availableForFlowActions are available as Local Action elements in the Cloud Flow Designer. When a component is executed as a flow local action, the flow calls the invoke method in the client-side controller. To run the code asynchronously in your client-side controller, such as when you’re making an XML HTTP request (XHR), return a Promise. When the method finishes or the Promise is fulfilled, control is returned back to the flow.

Flow Action Component

Here is the simple component that we will be used as flow action.

<aura:component implements="lightning:availableForFlowActions" access="global">
    <aura:attribute name="countryName" type="String" default="USA" access="global" />
    <aura:attribute name="response" type="String" default="USA" access="global" />
</aura:component>

1

2

3

4

<aura:component implements="lightning:availableForFlowActions" access="global">

<aura:attribute name="countryName" type="String" default="USA" access="global" />

<aura:attribute name="response" type="String" default="USA" access="global" />

</aura:component>

Controller

({
    invoke : function(component, event, helper) {
        var cancelToken = event.getParam("arguments").cancelToken;
        return new Promise(function(resolve, reject) {
            var xhttp = new XMLHttpRequest();
            xhttp.onreadystatechange = $A.getCallback(function() {
                if (this.readyState === 4) { 
                    if (this.status >= 200 && this.status < 300) {
                        var response = JSON.parse(xhttp.responseText);
                        console.log('response'+response);
                        component.set("v.response", JSON.stringify(response));
                        resolve();
                    } else {
                        var errorText = "";
                        if (this.status === 0) {
                            errorText = 'Request has been terminated\nPossible causes: the network is offline, Origin is not allowed by Access-Control-Allow-Origin, the page is being unloaded, etc.';
                        } else {
                            errorText = this.statusText;
                        }
                        reject(errorText);
                    }
                }
            });
            var countryName = component.get("v.countryName");
            xhttp.open("GET", "https://restcountries.eu/rest/v2/name/"+countryName, true);
            xhttp.send(null);
            cancelToken.promise.then(function(error) {
                xhttp.abort();
                reject(error);
            });
        });
    }
})

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

({

invoke : function(component, event, helper) {

var cancelToken = event.getParam("arguments").cancelToken;

return new Promise(function(resolve, reject) {

var xhttp = new XMLHttpRequest();

xhttp.onreadystatechange = $A.getCallback(function() {

if (this.readyState === 4) {

if (this.status >= 200 && this.status < 300) {

var response = JSON.parse(xhttp.responseText);

console.log('response'+response);

component.set("v.response", JSON.stringify(response));

resolve();

} else {

var errorText = "";

if (this.status === 0) {

errorText = 'Request has been terminated\nPossible causes: the network is offline, Origin is not allowed by Access-Control-Allow-Origin, the page is being unloaded, etc.';

} else {

errorText = this.statusText;

}

reject(errorText);

}

});

var countryName = component.get("v.countryName");

xhttp.open("GET", "https://restcountries.eu/rest/v2/name/"+countryName, true);

xhttp.send(null);

cancelToken.promise.then(function(error) {

xhttp.abort();

reject(error);

});

}

})

When a component is executed as a flow local action, the flow calls the invoke method in the client-side controller. To run the code asynchronously in your client-side controller, such as when you’re making an XML HTTP request (XHR), return a Promise. When the method finishes or the Promise is fulfilled, control is returned back to the flow. When a Promise is resolved, the next element in the flow is executed. When a Promise is rejected or hits the timeout, the flow takes the Local Action element’s fault connector and sets $Flow.FaultMessage to the error message. By default, the error message is “An error occurred when the elementName element tried to execute the c:FlowAction component.” To customize the error message in $Flow.FaultMessage, return it as a new Error object in the reject() call. When a Promise is fulfilled, the next element in the flow is executed. When a Promise is rejected or times out, the flow takes the Local Action element’s fault connector and sets $Flow.FaultMessage to the error message. By default, the error message is “An error occurred when the flow tried to execute the c:FlowAction component.”. To customize the error message, return it as an error in the reject() call.

Configure the designer

To make an attribute’s value customizable in the Cloud Flow Designer, add it to the component’s design resource. That way, flow admins can pass values between that attribute and the flow when they configure the Local Action element. That way, flow admins can pass values between that attribute and the flow when they configure the corresponding Local Action element.

<design:component>
    <design:attribute name="countryName" label="String"  />
    <design:attribute name="response" label="String"  />
</design:component>

1

2

3

4

<design:component>

<design:attribute name="countryName" label="String" />

<design:attribute name="response" label="String" />

</design:component>

Invoke Action from the Flow

Now go to the cloud flow designer and create a new screen element to enter the country name

Add the Flow locale actions into the screen and configure the input params as shown below.

Create a screen element to show the output response as shown below.

Final screen flow looks like below

Testing

Synchronous Code

the example code we have seen so far is Asynchronous Code where we will get the promise and here is the synchronous version of the controller.js

({
    invoke : function(component, event, helper) {
        var cancelToken = event.getParam("arguments").cancelToken;
        var xhttp = new XMLHttpRequest();
        var countryName = component.get("v.countryName");
        xhttp.open("GET", "https://restcountries.eu/rest/v2/name/"+countryName, false);
        xhttp.send(null);
        if (xhttp.status === 200) {
            component.set("v.response", JSON.stringify(xhttp.responseText));
        }
        
    },
    
})

1

2

3

4

5

6

7

8

9

10

11

12

13

14

({

invoke : function(component, event, helper) {

var cancelToken = event.getParam("arguments").cancelToken;

var xhttp = new XMLHttpRequest();

var countryName = component.get("v.countryName");

xhttp.open("GET", "https://restcountries.eu/rest/v2/name/"+countryName, false);

xhttp.send(null);

if (xhttp.status === 200) {

component.set("v.response", JSON.stringify(xhttp.responseText));

}

},

})

Usage Of lightning:availableForFlowScreens

By Raj Vakati December 2, 2018 Flow, Lightning 0 Comments

Salesforce flow is one of the most powerful business automation tools that will be used to build the application with drag and drop. Now we will see how to use the lightning component available for the flow screens. Make your custom Lightning components available to flow screens in the Cloud Flow Designer by implementing the lightning:availableForFlowScreens interface. In the Cloud Flow Designer, flow screen components appear as options for Lightning component screen fields. In this example, I will get the current conversion rates from the external API and will display on the flow by using component.

Apex class

public class FlowGetExchangeRates {
    
    @AuraEnabled
    public static ConversionRates getConversionRates(String source , String target){
        ConversionRates cr = new ConversionRates() ;
        Http http = new Http();
        HttpRequest request = new HttpRequest();
        request.setEndpoint('http://apilayer.net/api/live?access_key=456fab5d3bee967f81169416e234387e&currencies='+target+'&source='+source+'&format=1');
        request.setMethod('GET');
        System.debug('response'+request);
        HttpResponse response = http.send(request);
        if (response.getStatusCode() == 200) {
            Map<String, Object> results = (Map<String, Object>) JSON.deserializeUntyped(response.getBody());
            System.debug('results'+results);
            Map<String , Object> qts = (Map<String , Object>) results.get('quotes');
            for(String s : qts.keySet() ){
                System.debug('s'+s);
                if(s=='USDEUR'){
                    cr.USDEUR =  String.valueOf((Object)qts.get(s));
                }
                if(s=='USDGBP'){
                    cr.USDGBP =  String.valueOf((Object)qts.get(s));
                }
                if(s=='USDCAD'){
                    cr.USDCAD =  String.valueOf((Object)qts.get(s));
                }
                if(s=='USDPLN'){
                    cr.USDPLN =  String.valueOf((Object)qts.get(s));
                }
            }
        }
        return cr ; 
        
    }
    
    
    public class ConversionRates{
        @AuraEnabled
        public String USDEUR{get;set;}
        @AuraEnabled
        public String USDGBP{get;set;}
        @AuraEnabled
        public String USDCAD{get;set;}
        @AuraEnabled
        public String USDPLN{get;set;}
        
        
    }
    
}

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

public class FlowGetExchangeRates {

@AuraEnabled

public static ConversionRates getConversionRates(String source , String target){

ConversionRates cr = new ConversionRates() ;

Http http = new Http();

HttpRequest request = new HttpRequest();

request.setEndpoint('http://apilayer.net/api/live?access_key=456fab5d3bee967f81169416e234387e&currencies='+target+'&source='+source+'&format=1');

request.setMethod('GET');

System.debug('response'+request);

HttpResponse response = http.send(request);

if (response.getStatusCode() == 200) {

Map<String, Object> results = (Map<String, Object>) JSON.deserializeUntyped(response.getBody());

System.debug('results'+results);

Map<String , Object> qts = (Map<String , Object>) results.get('quotes');

for(String s : qts.keySet() ){

System.debug('s'+s);

if(s=='USDEUR'){

cr.USDEUR = String.valueOf((Object)qts.get(s));

}

if(s=='USDGBP'){

cr.USDGBP = String.valueOf((Object)qts.get(s));

}

if(s=='USDCAD'){

cr.USDCAD = String.valueOf((Object)qts.get(s));

}

if(s=='USDPLN'){

cr.USDPLN = String.valueOf((Object)qts.get(s));

}

return cr ;

}

public class ConversionRates{

@AuraEnabled

public String USDEUR{get;set;}

@AuraEnabled

public String USDGBP{get;set;}

@AuraEnabled

public String USDCAD{get;set;}

@AuraEnabled

public String USDPLN{get;set;}

}

The above class is covert the exchange rates based on the source currency specified. Make sure you added the Rest API URI to remove site settings.

Lightning component

<aura:component implements="lightning:availableForFlowScreens" access="global" Controller="FlowGetExchangeRates">
    <aura:attribute name="sourcecurrencies" type="String" access="global" default="USD"/>
    <aura:attribute name="targetcurrencies" type="String" access="global" default="EUR,GBP,CAD,PLN" />
    <aura:attribute name="resVal" type="FlowGetExchangeRates.ConversionRates" access="global"  />
    <aura:handler name="init" value="{!this}" action="{!c.doInit}"/>
    
    <table class="slds-table slds-table_cell-buffer slds-table_bordered slds-table_striped">
        <tr>
            <th>USD</th>
            <th>Conveted Val</th>
        </tr>
        <tr>
            <td>EUR</td>
            <td>{!v.resVal.USDEUR}</td>
        </tr>
        <tr>
            <td>GBP</td>
            <td>{!v.resVal.USDGBP}</td>
        </tr>
        <tr>
            <td>CAD</td>
            <td>{!v.resVal.USDCAD}</td>
        </tr>
        <tr>
            <td>PLN</td>
            <td>{!v.resVal.USDPLN}</td>
        </tr>
    </table>
    
    
</aura:component>

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

<aura:component implements="lightning:availableForFlowScreens" access="global" Controller="FlowGetExchangeRates">

<aura:attribute name="sourcecurrencies" type="String" access="global" default="USD"/>

<aura:attribute name="targetcurrencies" type="String" access="global" default="EUR,GBP,CAD,PLN" />

<aura:attribute name="resVal" type="FlowGetExchangeRates.ConversionRates" access="global" />

<aura:handler name="init" value="{!this}" action="{!c.doInit}"/>

<tr>

<th>Conveted Val</th>

</tr>

<tr>

<td>{!v.resVal.USDEUR}</td>

</tr>

<tr>

<td>{!v.resVal.USDGBP}</td>

</tr>

<tr>

<td>{!v.resVal.USDCAD}</td>

</tr>

<tr>

<td>{!v.resVal.USDPLN}</td>

</tr>

</table>

</aura:component>

({
    doInit : function(component, event, helper) {
        var action=  component.get('c.getConversionRates'); 
        action.setParams({"source":component.get("v.sourcecurrencies") , "target":component.get("v.targetcurrencies")})
        action.setCallback(this,function(response){
            var state=response.getState();
            if(state=='SUCCESS')
            {
                component.set('v.resVal',response.getReturnValue()); 
            }
        });
        $A.enqueueAction(action);
    }
})

1

2

3

4

5

6

7

8

9

10

11

12

13

14

({

doInit : function(component, event, helper) {

var action= component.get('c.getConversionRates');

action.setParams({"source":component.get("v.sourcecurrencies") , "target":component.get("v.targetcurrencies")})

action.setCallback(this,function(response){

var state=response.getState();

if(state=='SUCCESS')

{

component.set('v.resVal',response.getReturnValue());

}

});

$A.enqueueAction(action);

}

})

To make an attribute’s value customizable in the Cloud Flow Designer, add it to the component’s design resource. That way, flow admins can pass values between that attribute and the flow when they configure the Local Action element. That way, flow admins can pass values between that attribute and the flow when they configure the screen field. Here is the designer for component

<design:component>
    <design:attribute name="sourcecurrencies" label="sourcecurrencies"  default="USD"/>
    <design:attribute name="targetcurrencies" label="targetcurrencies"  default="EUR,GBP,CAD,PLN" />
</design:component>

1

2

3

4

<design:component>

<design:attribute name="sourcecurrencies" label="sourcecurrencies" default="USD"/>

<design:attribute name="targetcurrencies" label="targetcurrencies" default="EUR,GBP,CAD,PLN" />

</design:component>

A design resource describes the design-time behavior of a Lightning component information that visual tools need to allow adding the component to a page or app. Adding this resource is similar to adding it for the Lightning App Builder. When admins reference this component in a flow, they can pass data between the flow and the Lightning component. Use the Inputs tab to set an attribute using values from the flow. Use the Outputs tab to store an attribute’s value in a flow variable

Use Component in flow

Now we will use the above lightning component in flow designer. Go to salesforce flow builder and create a new flow. Drag and Drop the screen element to flow designer and configure the flow screen as shown below. the flow contains the two input text element that will accept the source and target currencies.

Drag and drop another screen element into the designer and configure flow to receive the input values from the first screen element as shown below.

Click save. Connect the two flow screen elements as shown below. Set the first screen as a starting element

Testing

Now go to the flow and enter the source and target currencies as shown below

Click Next and you will see the result from the Lightning component as shown below.

Custom Navigation Model for Flow Screens with Lightning Component

By Raj Vakati April 2, 2018 Flow, Lightning 0 Comments

In this blog, I am going to explain how to use the custom lightning component button that is used to control the navigation of flow.By default, users navigate a flow by clicking standard buttons at the bottom of each screen. The lightning:availableForFlowScreens interface provides two attributes to help you fully customize your screen’s navigation. To figure out which navigation actions are available for the screen, loop through the availableActions attribute. To programmatically trigger one of those actions, call the navigateFlow action from your JavaScript controller.

Flow Navigation Actions

The availableActions attribute lists the valid navigation actions for that screen NEXT, BACK, PAUSE, RESUME, FINISH are the possible actions. A screen’s available actions are determined by:

Where in the flow the screen is. For example, Previous isn’t supported on the first screen in a flow, Finish is supported for only the last screen in a flow, and you can never have both Next and Finish.
Whether the flow creator opted to hide any of the actions in the screen’s Navigation Actions controls. For example, if Allow Pause is de-selected, the Pause action isn’t included in availableActions.

Component

Here is the lightning component

<aura:component implements="lightning:availableForFlowScreens" access="global" >
    <!-- Get the script text from the flow -->    
    <aura:attribute name="scriptText" type="String" required="true" />
    <!-- Pass the value of the selected option back to the flow -->
    <aura:attribute name="value" type="String" />
    <aura:attribute name="action" type="String" />
    <div class="script-container">
        Navigation Action :   {!v.value}
    </div>
    <!-- Buttons for the agent to click, according to the customer’s response -->
    <div class="slds-p-top_large slds-p-bottom_large">
        <p><lightning:formattedText value="Customer Response" 
                                    class="slds-text-body_small" /></p>
        <lightning:buttongroup >
            <lightning:button label="Previous" aura:id="previousId" 
                              variant="neutral" onclick="{!c.handleChange}"/>
            <lightning:button label="Next" aura:id="nextId" 
                              variant="neutral" onclick="{!c.handleChange}"/>
            <lightning:button label="Finish" aura:id="finishId" 
                              variant="neutral" onclick="{!c.handleChange}"/>
            
        </lightning:buttongroup>
    </div>
</aura:component>

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

<aura:component implements="lightning:availableForFlowScreens" access="global" >

<aura:attribute name="scriptText" type="String" required="true" />

<aura:attribute name="value" type="String" />

<aura:attribute name="action" type="String" />

Navigation Action : {!v.value}

</div>

<p><lightning:formattedText value="Customer Response"

class="slds-text-body_small" /></p>

<lightning:buttongroup >

<lightning:button label="Previous" aura:id="previousId"

variant="neutral" onclick="{!c.handleChange}"/>

<lightning:button label="Next" aura:id="nextId"

variant="neutral" onclick="{!c.handleChange}"/>

<lightning:button label="Finish" aura:id="finishId"

variant="neutral" onclick="{!c.handleChange}"/>

</lightning:buttongroup>

</div>

</aura:component>

({
    handleChange : function(component, event, helper) {
        // When an option is selected, navigate to the next screen
        var response = event.getSource().getLocalId();
        component.set("v.value", response);
        var navigate = component.get("v.navigateFlow");
        console.log('navigate'+navigate)
        if(response=='previousId'){
            navigate("BACK");
        }
        if(response=='nextId'){
            navigate("NEXT");
        }
        if(response=='finishId'){
            navigate("FINISH");
        }  
    }
})

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

({

handleChange : function(component, event, helper) {

// When an option is selected, navigate to the next screen

var response = event.getSource().getLocalId();

component.set("v.value", response);

var navigate = component.get("v.navigateFlow");

console.log('navigate'+navigate)

if(response=='previousId'){

navigate("BACK");

}

if(response=='nextId'){

navigate("NEXT");

}

if(response=='finishId'){

navigate("FINISH");

}

})

<design:component>
    <design:attribute name="scriptText" label="Script Text" 
                      description="What the agent should say to the customer" />
    <design:attribute name="action" label="Navigation Action" 
                      description="" />
        
</design:component>

1

2

3

4

5

6

7

<design:component>

<design:attribute name="scriptText" label="Script Text"

description="What the agent should say to the customer" />

<design:attribute name="action" label="Navigation Action"

description="" />

</design:component>

Here the simple flow that I created for testing

You can see below the image that shows how the lightning component interacts with flow navigation.

Once you click the next button on the component it will take to the next action i.e Finish.

Dynamically Update a Flow Screen with a Lightning Component

By Raj Vakati April 2, 2018 Flow, Lightning 0 Comments

In this post, I am going to explain how to dynamically update the flow screen with the lightning component. To conditionally display a field on your screen, build a Lightning component that uses aura: if to check when parts of the component should appear. This component displays a custom script component and a group of radio buttons. The component gets the user feedback based on user-selected yes or no options.

If the user selects the Yes radio button, the component displays form for the user get in touch details

If the user selects the Yes radio button, the component displays thanks message.

Here is the lightning component

<aura:component access="global" implements="lightning:availableForFlowScreens">
    
    <aura:attribute name="radioOptions" type="List" default="[
                                                             {'label': 'Yes', 'value': 'false'},
                                                             {'label': 'No', 'value': 'true'} ]"/>
    <aura:attribute name="radioValue" type="Boolean" default="true"/>
    <div class="survey-container">
        <div class="slds-card__header slds-grid slds-p-bottom_small slds-m-bottom_none">
            <div class="slds-media slds-media_center slds-has-flexi-truncate" >
                <div class="slds-media__figure slds-align-top">
                    <h2><lightning:icon iconName="utility:quotation_marks"
                                        title="Get in touch Details" /></h2>
                </div>
                <div class="slds-media__body">
                    <ui:outputRichText class="script" value="{!'Would you like to Get in touch with Sales?'}"/>
                </div>
            </div>
        </div>
    </div>
    
    <div class="slds-p-top_medium slds-p-bottom_medium">
        <lightning:radioGroup aura:id="rbg_correct" name="rbg_correct"
                              label="Would you like to take survey?"
                              options="{! v.radioOptions }" value="{! v.radioValue }" />
        <aura:if isTrue="{!v.radioValue}">
            <div class="slds-media__body">
                <ui:outputRichText class="script" value="{!'Thanks for your Time'}"/>
            </div>
        </aura:if>
        
        <aura:if isTrue="{!v.radioValue}">
            <aura:set attribute="else">
                <lightning:input label="Name" name="Name" class="slds-p-top_small" />
                <lightning:input type="tel"  label="Phone" class="slds-p-top_small"/>
                <lightning:input type="date" label="Birthday" name="date" class="slds-p-top_small"/>
                <lightning:input type="email" label="Email" name="email" value="abc@domain.com" class="slds-p-top_small"/>
            </aura:set>
            
        </aura:if>
        
    </div>
    
    
</aura:component>

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

<aura:component access="global" implements="lightning:availableForFlowScreens">

<aura:attribute name="radioOptions" type="List" default="[

{'label': 'Yes', 'value': 'false'},

{'label': 'No', 'value': 'true'} ]"/>

<aura:attribute name="radioValue" type="Boolean" default="true"/>

<h2><lightning:icon iconName="utility:quotation_marks"

title="Get in touch Details" /></h2>

</div>

<ui:outputRichText class="script" value="{!'Would you like to Get in touch with Sales?'}"/>

</div>

<lightning:radioGroup aura:id="rbg_correct" name="rbg_correct"

label="Would you like to take survey?"

options="{! v.radioOptions }" value="{! v.radioValue }" />

<aura:if isTrue="{!v.radioValue}">

<ui:outputRichText class="script" value="{!'Thanks for your Time'}"/>

</div>

</aura:if>

<aura:if isTrue="{!v.radioValue}">

<aura:set attribute="else">

<lightning:input label="Name" name="Name" class="slds-p-top_small" />

<lightning:input type="tel" label="Phone" class="slds-p-top_small"/>

<lightning:input type="date" label="Birthday" name="date" class="slds-p-top_small"/>

<lightning:input type="email" label="Email" name="email" value="abc@domain.com" class="slds-p-top_small"/>

</aura:set>

</aura:if>

</div>

</aura:component>

Here is the flow which created for this example

Below image shows how to invoke the lightning component in flow designer.

Using Lightning Component In Flows

By Raj Vakati April 2, 2018 Flow, Lightning 0 Comments

Introduction :

In this post, I am going to show how to use the lightning component in the flow. the example I am taking hers is search contact based on user inputs like the user will enter contact information and once the form is submitted from the flow, we will fetch the flow input and passing it the lightning component to get the contacts. To use a custom Lightning component in flow screens, configure the component and it is designed to the resource so that they’re compatible with the Cloud Flow Designer.

Apex Class

public class ContactsListController {
    @AuraEnabled
    public static List<contact> getContacts(String firstName,String lastName ,String email ,String phone) {
        List<contact> results = Database.query(
            'Select Id, FirstName, LastName, Title, Email,MobilePhone FROM contact where FirstName =\''+firstName +'\' OR LastName =\''+lastName+'\' OR Email=\''+email+'\' OR MobilePhone =\''+phone+'\'');
        return results;  
    }
    
}

1

2

3

4

5

6

7

8

9

public class ContactsListController {

@AuraEnabled

public static List<contact> getContacts(String firstName,String lastName ,String email ,String phone) {

List<contact> results = Database.query(

'Select Id, FirstName, LastName, Title, Email,MobilePhone FROM contact where FirstName =\''+firstName +'\' OR LastName =\''+lastName+'\' OR Email=\''+email+'\' OR MobilePhone =\''+phone+'\'');

return results;

}

Lightning Component

The below is the lightning component which we will use in cloud flow designer. This component will collect the input values from the flow and pass it the controller to fetch the contacts

<aura:component implements="lightning:availableForFlowScreens" access="global" controller="ContactsListController">
    <aura:attribute name="firstName" type="String" default="" access="global" />
    <aura:attribute name="lastName" type="String" default="" access="global" />
    <aura:attribute name="email" type="String" default="" access="global" />
    <aura:attribute name="phone" type="String" default="" access="global" />
    <aura:attribute name="rows" type="Contact[]" default="" access="global" />
    <aura:handler name="init" value="{!this}" action="{!c.init}" />
    <table class="slds-table slds-table--bordered slds-table--striped">
        <thead>
            <tr>
                <th scope="col"><span class="slds-truncate">FirstName</span></th>
                <th scope="col"><span class="slds-truncate">Last Name</span></th>
            </tr>
        </thead>
        <tbody>
            <aura:iteration items="{!v.rows}" var="row">
                <tr>
                    <td>{!row.FirstName}</td>
                    <td>{!row.LastName}</td>
                </tr>
            </aura:iteration>
        </tbody>
    </table>
    
    
</aura:component>

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

<aura:component implements="lightning:availableForFlowScreens" access="global" controller="ContactsListController">

<aura:attribute name="firstName" type="String" default="" access="global" />

<aura:attribute name="lastName" type="String" default="" access="global" />

<aura:attribute name="email" type="String" default="" access="global" />

<aura:attribute name="phone" type="String" default="" access="global" />

<aura:attribute name="rows" type="Contact[]" default="" access="global" />

<aura:handler name="init" value="{!this}" action="{!c.init}" />

<thead>

<tr>

<th scope="col"><span class="slds-truncate">FirstName</span></th>

</tr>

</thead>

<tbody>

<aura:iteration items="{!v.rows}" var="row">

<tr>

<td>{!row.FirstName}</td>

<td>{!row.LastName}</td>

</tr>

</aura:iteration>

</tbody>

</table>

</aura:component>

({
    init : function(component, event, helper) {
        var action = component.get("c.getContacts");
        action.setParams({
            firstName : component.get('v.firstName') ,
            lastName : component.get('v.lastName') ,
            email : component.get('v.email') ,
            phone : component.get('v.phone') 
        });
        
        action.setCallback(this, function(a) {
            if (a.getState() === "SUCCESS") {
                component.set("v.rows",a.getReturnValue()); 
            } else if (a.getState() === "ERROR") {
                $A.log("Errors", a.getError());
            }
        });
        
        $A.enqueueAction(action); 
    },
    
    
})

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

({

init : function(component, event, helper) {

var action = component.get("c.getContacts");

action.setParams({

firstName : component.get('v.firstName') ,

lastName : component.get('v.lastName') ,

email : component.get('v.email') ,

phone : component.get('v.phone')

});

action.setCallback(this, function(a) {

if (a.getState() === "SUCCESS") {

component.set("v.rows",a.getReturnValue());

} else if (a.getState() === "ERROR") {

$A.log("Errors", a.getError());

}

});

$A.enqueueAction(action);

},

})

design.resource

<design:component >
    <design:attribute name="firstName" label="firstName" />
    <design:attribute name="lastName" label="lastName" />
    <design:attribute name="email" label="email" />
    <design:attribute name="phone" label="phone" />
    
</design:component>

1

2

3

4

5

6

7

<design:component >

<design:attribute name="firstName" label="firstName" />

<design:attribute name="lastName" label="lastName" />

<design:attribute name="email" label="email" />

<design:attribute name="phone" label="phone" />

</design:component>

Flow

Now create a simple flow as shown below. I create a flow with multiple screens but you can create a single screen. Evey screen is having only one text field line first name, last name, email, and phone. The final is screen is the place where I am invoking the lightning component.

The below image shows how to call the lightning components from the flow designer. Use Lightning Component Extension

configuree the input and output variable as shown below

Add it the Lightning Record page. Now you can see your flow as shown below.

You can able to search the contacts from the flow screen as shown below after entering the first name, last name, and email and phone.

Category: Flow

Flow Local Actions Using Lightning Components

How to add Flow Local Actions

Flow Action Component

Configure the designer

Invoke Action from the Flow

Testing

Synchronous Code

Like this:

Usage Of lightning:availableForFlowScreens

Use Component in flow

Testing

Like this:

Custom Navigation Model for Flow Screens with Lightning Component

Flow Navigation Actions

Component

Flow

Like this:

Dynamically Update a Flow Screen with a Lightning Component

Like this:

Using Lightning Component In Flows

Introduction :

Apex Class

Lightning Component

Flow

Like this:

February 2019
M	T	W	T	F	S	S
« Jan
				1	2	3
4	5	6	7	8	9	10
11	12	13	14	15	16	17
18	19	20	21	22	23	24
25	26	27	28

Category: Flow

How to add Flow Local Actions

Flow Action Component

Configure the designer

Invoke Action from the Flow

Testing

Synchronous Code

Share this:

Like this:

Use Component in flow

Testing

Share this:

Like this:

Flow Navigation Actions

Component

Flow

Share this:

Like this:

Share this:

Like this:

Introduction :

Apex Class

Lightning Component

Flow

Share this:

Like this: