Process Automation Showdown Session 1
0 likes139 views
The three competitors presented solutions for automating common business processes using Process Builder and Visual Workflow (Flow). Jennifer demonstrated automatically displaying additional contact details using a Visual Workflow. Mike showed calculating case totals on Accounts using a Flow triggered by Process Builder. Amanda automated contract creation from opportunities using Process Builder. Michael proposed tracking case status changes over time without code using custom objects, Flow, and Process Builder.
Process Automation Showdown Session 1
- 1. Process Automation Showdown Session #1 aedelstein@salesforce.com, @alexed1 Alex Edelstein, Sr. Director Product Management – Process Automation
- 2. Forward-Looking Statements Statement under the Private Securities Litigation Reform Act of 1995: This presentation may contain forward-looking statements that involve risks, uncertainties, and assumptions. If any such uncertainties materialize or if any of the assumptions proves incorrect, the results of salesforce.com, inc. could differ materially from the results expressed or implied by the forward- looking statements we make. All statements other than statements of historical fact could be deemed forward-looking, including any projections of product or service availability, subscriber growth, earnings, revenues, or other financial items and any statements regarding strategies or plans of management for future operations, statements of belief, any statements concerning new, planned, or upgraded services or technology developments and customer contracts or use of our services. The risks and uncertainties referred to above include – but are not limited to – risks associated with developing and delivering new functionality for our service, new products and services, our new business model, our past operating losses, possible fluctuations in our operating results and rate of growth, interruptions or delays in our Web hosting, breach of our security measures, the outcome of any litigation, risks associated with completed and any possible mergers and acquisitions, the immature market in which we operate, our relatively limited operating history, our ability to expand, retain, and motivate our employees and manage our growth, new releases of our service and successful customer deployment, our limited history reselling non-salesforce.com products, and utilization and selling to larger enterprise customers. Further information on potential factors that could affect the financial results of salesforce.com, inc. is included in our annual report on Form 10-K for the most recent fiscal year and in our quarterly report on Form 10-Q for the most recent fiscal quarter. These documents and others containing important disclosures are available on the SEC Filings section of the Investor Information section of our Web site. Any unreleased services or features referenced in this or other presentations, press releases or public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make the purchase decisions based upon features that are currently available. Salesforce.com, inc. assumes no obligation and does not intend to update these forward-looking statements.
- 3. Lightning Flow Two great ways to automate your processes Easy to Use and Surprisingly Versatile Process Builder Visual Flow Our powerful and extensible workflow environment
- 4. Watch, Learn, and VOTE! Who will win? It’s up to you!
- 5. First Competitor: Jennifer W. Lee Salesforce Business Consultant @jenwlee
- 6. Meet Jennifer W. Lee Salesforce Business Consultant, John Hancock Salesforce MVP, Summer ’16-’17 Blogger: Jenwlee.wordpress.com Automation Hour Co-Host (AutomationHour.com) Trailhead Addict – 310 Badges (full count a/o Oct Otter Release) Presenter: Dreamforce ‘16-17, Boston and NYC World Tours, Southeast Dreamin’ 17, Salesforce User Groups Social Media Manager for WiT Diversity Twitter: @jenwlee
- 7. Use Case: Highlight Additional Contact Details Business Requirements • Agent/rep needs to quickly/easily locate contact information, such as if the contact • Is a premier client (i.e. account attribute), • Is the primary contact (i.e. related contact), • Has open cases (w/count), and • Has open opportunities (w/count) For the purposes of this demo, I will focus on solution that addresses the requirement to display the open cases (w/count).
- 8. The Solution: Visual Workflow
- 9. The Solution: Visual Workflow Ingredients • Create a Flow that does the following: • Fast Lookup open cases • Decision if any open cases were found • Loop: • Record Lookup Case Number and Case Subject • Perform Assignment – add screen info and increment case count • Decision for screen to display (Has Cases or No Cases) • Screen shows additional contact info • Add flow component to Contact Lightning page via App Builder
- 10. The Demo
- 11. Next Competitor: Mike Gill Technical Architect @agentgill
- 12. Meet Mike Gill Technical Architect with 10K Advisors Salesforce MVP Winter 15’ Blogger at Salesforceweek.ly Co-Leader London Admin User Group Dreamforce Presenter 2015 & 2016 Co-presenter for Release Readiness Webinar on the Success Community Trailhead Ranger – 100+ Badges Twitter: @agentgill
- 13. Use Case: Case Summary Calculator Business Requirement • Display the Total Number of Closed & Open Cases against an Account • Let’s create a Roll-up Summary field… • Hold on… I cannot create a Roll-Up Summary field • Why – Standard Roll-up fields are only available when the object relationship is Master-Detail • What are our options: • Create & use a report • Use an App… something like Declarative Lookup Roll-Up Summaries (dlrs) or the Roll-up Helper App • Write some Apex… Code is cheating! • Or we create our own using Process Builder & Flow (the ultimate classic example)
- 14. The Solution: Flow with the help of Process Builder Ingredients • First we create some Custom Fields field on the Account object to store Total Closed Cases and Total Open Cases • Next we create our Flow will handle the summarization & calculate our Totals • Lookup all Cases for a given Account • Loop over each Case and determine if case is Open or Closed • Count the number of Cases for each • Update the Account with the Totals • Lastly we use Process Builder on the Case to auto-launch our Flow • Pass in our Account Id to kick start the calculation process
- 15. The Demo
- 16. Next Competitor: Amanda Matczynski Operations Supervisor @agmatczynski
- 17. Meet Amanda Matczynski Operations Supervisor, Wolf & Company, P.C. Certified Salesforce Administrator Co-Leader Boston User Group Trailhead Ranger – 100+ Badges 2017 Boston World Tour Awesome Admin Twitter: @agmatczynski
- 18. Business Requirements • Create contract when an opportunity is closed won • Relate original opportunity to contract • Relate opportunity products to contract • Submit contract for approval Use Case: Auto-Create Contract
- 19. The Solution: Process Builder Ingredients • Field setup • Create/Enable necessary lookup fields on Contract, Opportunity, and Opportunity Products objects • Create Contract Approval Process • Process Builder on the Opportunity object when record is created or edited and Stage is Closed Won • Create Contract and store Opportunity on the Contract Object • Update Opportunity Products with new Contract ID • 2nd Process Builder on the Contract object when record is created • Update Opportunity with new Contract ID. • Submit Contract for approval • Update Contract status to “In Approval Process”
- 20. The Demo
- 21. Next Competitor: Michael L Barnes Director, Salesforce.com Administration michael.barnes@golfchannel.com @BarnesMichaelL
- 22. Meet Michael L Barnes Director, Salesforce.com Administration, GolfNow Salesforce Admin since 2010 Degrees in Electrical Engineering (Georgia Tech) and MBA (University of Florida) Certified Administrator (‘13), Advanced Administrator (‘15) and Platform App Builder (‘16) Presenter: Dreamforce ‘14, Salesforce Chatter Recognition, Dreamforce ‘15, Salesforce Partner Community, Dreamforce ‘17 Flow & Process Builder Best Practices Active contributor to the Success Community Twitter: @BarnesMichaelL
- 23. Use Case: Case Status Tracker How much time do cases spend in any particular status? • Case History has the data, but calculations are a challenge • Need to better understand Support Process to eliminate gaps How many times are cases bouncing back to a status? • Same problems here, counting records and grouping statuses can be difficult • Managers need to know what is delaying case closings • With a solution, we meet our SLAs!
- 24. Problem Solved with Process Automation Tools you need • Custom Object • Master-Detail Relationship field • Picklist Field • Two (2) Numeric Fields • Two (2) Formula Fields • Case Object • Roll-up Summary Field • Two (2) Formula Fields • Custom Text Field • Flow • Process Builder • Workflow with Field Update • NO CODE NEEDED Case Time Tracker
- 25. Demo
- 26. One More Thing…
- 27. Bonus Use Case: Flow as a Survey Tool bit.ly/showdownvote1
- 28. And the winner is…
Editor's Notes
- #4: We took our process infrastructure and hooked it into the Lightning You can use components to create dynamic, rich experiences. What goes into a flow? Decisions Based on user input or record context, the flow will change directions. 3rd Party Events Kickoff flows with a platform event, or call an API to move a decision forward Screens Design the screen within flow builder Process Components Like a path component, file upload, video player - into the flow. What goes into a flow? Platform Events Publish and subscribe to events and built into the flow Rich Dynamic UX via Lightning Components within Flows Add Lightning components into a flow Flow Components Packaged processes that can be added to apps and communities, combine code with declarative building Global Flows Create processes that sit outside of a record, and can be used to create records Embedded Flows Embed flows into a record, and they will inherit the record information Packaged Flows / “App” Can be added to apps and communities, combine code with declarative building Flow Builder Built a complete flow that you can embed into a Apps, Communities, or 3rd party sites. Platform Event: Subscribe or Publish External Service: API which lets you make an outbound API callout Decisoin: Based on users input or record context, the flow will change directions. If you load up the verified flow, you can say “look at the custoemr record,” if they have, you can offer something.