Taking Flow to the Next Level with Just Enough Code
0 likes724 views
The document discusses enhancing Salesforce flow capabilities through coding with Visualforce and Apex, detailing how to customize flow pages and handle attachments. It outlines risks associated with forward-looking statements related to Salesforce's products and services, emphasizing that unreleased features may not be delivered on time. Additionally, it provides technical examples and links to GitHub repositories for implementation guidance.
Taking Flow to the Next Level with Just Enough Code
- 1. Taking Flow to the Next Level with Just Enough Code Mary Pustejovsky Solution Architect, Heller Consulting @mpusto Robert Strunk Senior Developer, Coastal Cloud @sf_tidbits
- 2. Safe harbor 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. Safe Harbor
- 5. Examples: How do you style the Flow page? How do you pass in lots of variables? What if I want someone to add an attachment? How do you determine where the Flow ends? Visualforce and Apex to the rescue! Flow is POWERFUL but has limits Can’t I just do everything in Flow?
- 6. All Dressed Up with Some Place to Go Altering the Flow appearance and starting with a specific record
- 7. Embed in VF page and open up possibilities! Visualforce Example
- 8. How it renders Visualforce Example
- 9. Upload Attachments from a Flow How to allow users to upload an attachment within a Flow GitHub Repo : http://bit.ly/1N3gOyZ
- 10. Create your controller and initialize your Flow.Interview member Create your Controller http://bit.ly/1N3gOyZ
- 11. Add variable to hold attachment parentId Create your Controller http://bit.ly/1N3gOyZ
- 12. Add variable to hold the attachment Create your Controller http://bit.ly/1N3gOyZ
- 13. Add method to perform upload Create your Controller http://bit.ly/1N3gOyZ
- 14. Set the controller attribute to your Apex controller Create your Visualforce Page Add your <flow:interview> tag http://bit.ly/1N3gOyZ
- 15. Add a conditionally rendered outputPanel that holds the file upload markup Create your Visualforce Page http://bit.ly/1N3gOyZ
- 16. Finish Locations with Apex How to send the user to a newly created record from a Flow
- 17. Change where the flow ends instead of starting again What is a Finish Location?
- 18. Add a finish location attribute Set a relative URL for a page Setting a Finish Location – Starting Small
- 19. Create your own controller for added logic --Finds the record ID and sets the page location Setting a Finish Location – Thinking Bigger
- 20. Add the Flow Getting the ID of the record Use the ID to get the URL Break up the pieces
- 21. Add the controller Update the finish location Update the Page
- 22. Thank you