1

2

Agenda

Overview of Salesforce Automation Hour Webinar series

Upcoming Webinars

Your Sponsor and Co-Hosts

Today’s Presenter: Jennifer Lee

Questions and Answers

3

Salesforce Automation Hour

Date/Time: Fridays, 3-4pm ET

November Webinars: 11/4/16 – Presenter: Doug Ayers 11/11/16 – Presenter: Benjamin Bolopue 11/18/16 – Presenters: Melissa VanDyke & Taylor Grimes

December Webinars: 12/9/16 – Presenter: Mike Gill 12/16/16 – Presenter: Meighan Brodkey

Got a cool process automation use case and solution to share?https://salesforceautomationhour.wordpress.com/contactus/

4

Logistics

All lines will be muted.

Please use the chat function to ask questions.

Continue the questions in the success community

The recording will be posted after the session.

Resources: Success Community: Salesforce Automation Hour Web site: http://SalesforceAutomationHour.wordpress.com

Our Sponsor

Concretio is a Salesforce trusted PDO and ISV partner, who are offering expert Salesforce implementation, custom development and support services to worldwide enterprises. Beyond usual Salesforce clicks and code, Concretio Team is expert in delivering sophisticated and gorgeous solutions/apps using Lightning, AngularJS, and Mobile SDK.

6

Your Co-Hosts

Jennifer W. LeeSalesforce Business Consultant,John Hancock

Salesforce MVPBlogger: Jenwlee.wordpress.comBWT #AwesomeAdmin Award RecipientTrailhead Addict – 170 Badges!Social Media Manager for WiT Diversity

Twitter: @jenwlee

8

Winter ‘17 Process Builder & Flow Yumminess

Build Reusable Processes!

View Your Process Types in One Place

Access Owner Fields From Process Builder

Show Flows in Two Column Screens (Beta)

Run Flows with Lightning Skin (Beta)

Add Flow Components to Lightning Pages (Beta)

9

Build Reusable Processes!

When would I invoke another process?

1. Implement simple nested if/then statements using invocable processes. Rather than build flow or write code, build the second level of logic into another process.

2. Modularize sections of your processes. Call it from multiple processes or from multiple action groups in the same process. Update those actions in one invocable process, all processes then use the updated actions.

10

Use Case #1: Automate Process for New and Updates to Existing Leads

11

The Solution for Use Case #1

12

Use Case #1: Automate Process for New and Updates to Existing Leads

13

The Improved Solution for Use Case #1

14

The Improved Solution for Use Case #1 – Master Process

15

The Improved Solution for Use Case #1 – Invoked Process

16

Use Case #2: Automate Process for New and Updates to Existing Accounts

17

The Solution for Use Case #2

18

Use Case #2: Automate Process for New and Updates to Existing Accounts

19

The Improved Solution for Use Case #2

20

The Improved Solution for Use Case #2 – Master Process

21

The Improved Solution for Use Case #2 – Invoked Process

22

View Your Process Types in One Place

23

Access Owner Fields From Process Builder

24

Show Flows in Two Column Screens (Beta)Choose from one- or two-column flow screens.

Enable feature under Process Automation Settings

Use the following flow URL syntax: /flow/flowName?flowLayout=twoColumn /flow/Case_Management?flowLayout=twoColumn /flow/User_Info?varUserFirst={!$User.FirstName}&varUserLast={!$User.LastName}&flowLayout=twoColumn

Note: Tabbing will go through all the fields in the left column and then all the fields in the right column. Can’t configure the fields to tab left-to-right.

25

Run Flows with Lightning Skin (Beta)

Choose whether to run your flows in Classic or Lightning runtime

26

Run Flows with Lightning Skin (Beta)

Which Runtime Experience Will My Users See?

Flows run from a Visualforce page: always use Classic runtime

Flows run from a Lightning page: always use Lightning runtime.

All other methods depend on whether Lightning runtime is enabled in your org

Enable feature under Process Automation Settings

27

Run Flow Components in Lightning Pages (Beta)

Run flows from a Lightning page Updating Versions of the Referenced Flow:

If you activate new versions of the flow and flow’s input variables change, the flow component can become invalid. Remove and add the component.

Input Variable not supported: Collection, sObject, sObject collection and Picklist or Multi-Select Picklist variables

The component supports only manually entered values for input variables.

Text input variables accept a maximum length of 4,000 characters.

Pass the record’s ID automatically as a variable at run time by using the field value “recordId.”

28

Use Case: Add Case Comments in Lightning Experience

Users need the ability to add case comments in Lightning Experience.

(Gap) Case comments cannot be created in Lightning.

Design Solutions:

Use case feed to add comments (requires Chatter)

Add case comments in Classic

Use Flow to collect the case comment and create casecommentrecord behind the scenes.

29

Embed Flows in Lightning Pages (Beta)

30

Embed Flows in Lightning Pages (Beta)

31

No More Talk, Let’s See it!

32

You’ve Got Questions?