The old version of Load Web Page used an event-based architecture that doesn’t work in all Salesforce environment.
Here’s a new version that should work everywhere: Install
Provide it with a url that has the “http://” in front of it.
Users can start flows and then pause them, and those same flows can be made to appear on the user’s Contact record where an agent can resume and complete the flow.
This requires and relies on the Guided Action List’s ability to find and display all paused flows associated with a record.
The Community user must be a signed in Salesforce user. They can’t be a Guest User.
Flow provides a mechanism that allows individual flows to be linked to records. This means that a flow about a Contact can be linked to a particular Contact via that Contact’s Id. Or a flow could be linked to an Asset or a custom object record. The main benefit of doing this is that when the record page is displayed for that record, if the record page has a Guided Action List component, it will display all the linked flows that are 1) In Progress or 2) Paused. And in the case of flows that are Paused, the user looking at the record page can resume the flow.
In order for a Flow started in Community Cloud to be resumable by an agent in Service Cloud, have the Flow populate the Flow Global Variable $Flow.CurrentRecord must be assigned the value of the current UserId.
Tip: The Contact Id of the currently logged-in Community user is the same as their UserId.
Flow provides access to the Global Variable $User and $User.Id will return the currently logged-in user’s Id. Assign this value to the recordId resource that you created:
When the Guided Action List is on a record page, it queries to see if there are any Flows in progress or paused that are linked to the current recordId, and it does this by checking for the presence of a value in a resource called recordId. So, you will need to be on the Contact page corresponding to the user in order to see their paused flows.
A final note: The Guided Action List component is only available in the Lightning Experience so you’ll need to be in Lightning to use this process.
There’s a new blog post on Salesforce’s official blog channel covering the use of the official, bundled-with-Flow Display Image screen component. Check it out.
There’s also the more powerful, less polished Image screen component that continues to be available on this community site. The original post on that.
Here’s a post we did on overriding the Footer buttons with a custom image.
There are scenarios where you need to know the distance between two specific cities and use it in your flows. Now you can easily do it using this new flow action. Grab an unmanaged package here, install it to you Salesforce organization and add it to your flow. Alternatively, you can grab the source code from GitHub and push to your org.
Internally this action utilizes Google Maps API so you will need to get developer key. You can request one here. After you got the key and installed the package, go to Setup -> Custom Metadata Types -> Google API Key (click ‘Manage Records‘ next to it). There will be just one record of this type: open it and paste your developer key into Key field.
Configuring Google developer key
The configuration is pretty straightforward: give it two cities (optionally with country names for disambiguity) and use the output distance measured in miles or kilometers.
Input values configuration
Output values configuration
If everything is fine parameter Is Success will contain True value. Otherwise, it becomes False, and Error Message will contain detailed description of the error (e.g. source or destination were not found or there are no routes between them). The distance (both in miles and in kilometers) are rounded up to 3 digits.
Example of the message constructed from the output parameters
Source Location and Destination Location output parameters are the source and destination input parameters converted to a universal form City, State, Country (e.g. Los Angeles, CA, USA)
Platform Events and Flows are a perfect match, but to get them to work with each other, you need to go through Process Builder and deal with several interesting wrinkles. Learn More.
Please note: this is the unofficialsf.com blog, and this post is as unofficial as they come. The following technique is offered without warranty or support.
The Spring ’19 release of Flow Builder has some gaps in functionality — such as copy and paste — that some people have found necessary to be efficient when building flows. While the Salesforce teams are working on filling in the gaps, it is possible (in Spring ’19) to re-enable Cloud Flow Designer in the Process Automation Settings by deselecting the “Disable access to Cloud Flow Designer” option. When this option is deselected, flow versions that were saved in Cloud Flow Designer are opened Cloud Flow Designer, and flow versions that were saved in Flow Builder are opened in Flow Builder.
But what if you’ve made — and saved — a bunch of changes to your flow in Flow Builder, and only then you decide you want to go back to Cloud Flow Designer? Well, the engine that runs your flows is the same for both versions: although the user interface for building the flow has changed, the metadata created by Flow Builder is pretty much the same as the metadata created by Cloud Flow Designer. There’s nothing in theory to prevent a flow version that was saved in one tool from being opened in the other, except that there isn’t a means to do it in the user interface.
The following technique allows you to move a Flow Builder flow version back to Cloud Flow Designer. Again, this is not supported by Salesforce: you’re going to want to test your flow carefully after you move it back to Cloud Flow Designer. But if you’ve done a lot of work on your flow in Flow Builder already and you really feel like you need to go back to Cloud Flow Designer, and reverting to a previous version isn’t an option, this solution may work for you.
At this point, test your flow and make sure that everything is still working as expected. I verified that this worked for my flow by saving the Cloud Flow Designer version as a separate flow, adding both flows to a package, exporting it in Workbench, and doing a diff on the files: the only difference in the metadata was the name and an additional processMetadataValues element in the Flow Builder flow indicating that it was created using Flow Builder. You don’t have to test it my way. But you should still do some tests before continuing to enhance the flow. If you find it’s not working the way you expect, you can still return to your previous version.
You can now continue working on the flow in Cloud Flow Designer. You can also switch back to Lightning.
Note that in July 2019, Chrome, Firefox and other browsers will start to make it more difficult to enable the Flash plugin that is required to use Cloud Flow Designer, as the browsers prepare for Adobe’s end of life for Flash. If you’re comfortable staying in Flow Builder now, you should. But if it’s really not working for you right now, I hope this will help until Summer ’19 rolls out.
Englhard Consulting has published a strong set of new actions and components. Check it out at https://englhardconsulting.com/flow-and-lightning-components-package/
Flow Builder has a brand new user interface that is similar to Lightning App Builder and Process Builder, so if you’re familiar with those tools you’ll feel right at home here. Clean lines and intuitive shapes make it easy to navigate around your flows, and the streamlined toolbox makes it easier to find the element or resource you’re looking for. On top of that, Flow Builder is built with Salesforce’s latest front-end technologies for fast performance – say goodbye to kludgy old Flash!
If you’re an old-school Flownatic, you might have noticed that some things have been renamed or moved around in Flow Builder. For example, the sObject data type is now a Record data type; and static, local and quick actions can all now be found under the Core Action element. As part of the streamlined toolbox, we replaced the Fast Lookup and Record Lookup elements with Get Records, and the other Data elements have received a similar treatment. For a full list of differences, see the Flow Builder vs. Cloud Flow Designer document in Salesforce Help.
We know that undo/redo, copy and paste, and the ability to find elements and resources in the canvas are important to you. We’re working hard on these features and expect to release them in Summer ’19. (As always, please make purchasing decisions based on current functionality and not this forward-looking statement!) We just ran out of time to get features into Spring ’19 and decided it was better to release Flow Builder with all the goodness it does have, than to wait another release.
Starting with Spring ’19, Flow Builder is the default experience when creating new flows and opening existing flows. If you need to use Cloud Flow Designer – perhaps because a feature you need isn’t yet available in Flow Builder – you can re-enable it: in Setup, go to the Process Automation Settings page and deselect the Disable access to Cloud Flow Designer option. With this deselected, flow versions that were saved in Cloud Flow Designer will open in Cloud Flow Designer, and versions that were saved in Flow Builder will open in Flow Builder.
If you have a flow that you saved in Flow Builder and you decide you really need to go back to Cloud Flow Designer, there’s an unofficial solution for that too: see Converting a Flow Builder Flow Version Back to Cloud Flow Designer.
To pan the canvas, you can press and hold down the Space key, then click anywhere in the canvas and drag.
We’re working on marquee selection (clicking and dragging to select multiple elements) for a near-term release. Until then, to select multiple elements on the canvas, press and hold down the Shift key, then click on each element you want to add to the selection. Then click on any selected element to move the entire selection.
To turn a variable of any data type into a collection variable, select the Allow multiple values (collection) checkbox next to the Data Type field.
We added the ability to use Lightning components in flows in Winter ’19, and actually included a number of out-of-the-box components then, like Dependent Picklists, Phone, Email, and Name – but since they were hidden under Extensions in Cloud Flow Designer, you might have missed them. Flow Builder elevates these components to first-class screen components, and with Spring ’19 we have two new components: Address and Display Image.
Remember, when you’re using Lightning components with input fields in them (like Name) you’ll need to specify a variable for the field in the Store Output Values section in the component properties in order to use the field’s value elsewhere in the flow. (This is different from the way screen components like Text work, where the screen component can be used directly as a resource.)
All of the Trailhead modules and projects that previously referred to Cloud Flow Designer have been rewritten with instructions on how to use Flow Builder. If you’ve previously completed these modules and projects, maybe you’d like a refresher! Otherwise, hold tight until March – brand new flow content will be coming your way soon.
All the Trailhead content related to flows is now up to date with the latest on Flow Builder. In addition, Alex Edelstein ‘s Get Started with the New Flow Builder post on the Salesforce Admins blog has two hours of video tutorial content to help both new and old school flow users get up to speed. From sending an email to building a screen to working with multiple records, these tutorials have you covered!
A small galleryJanuary 24, 2013 - 6:20 pm
Hi Alex - With Guided Actions, can you "Jump" to different...April 16, 2019 - 11:33 am by Keith Sadler
Is it possible to have a child control a grand child? My...April 16, 2019 - 5:54 am by bradedgerly
Thanks for the feedback, Liron. A lookup component is on...March 21, 2019 - 7:04 am by Shannon Hale