It's refreshing to hear someone say the truth about learning and the process of getting there. It's encouraging. Thank you for sharing your perspective and the demo.
Good video. In case you were wondering, the GUID is the ID related to the flow interview for when an auto-launched (or screen) flow executes. Useful if you want to query the FlowInterviewLog record and find information such as how long it took to run, or if the auto-launched flow is paused perhaps in a delay and you need to stop the flow from continuing, then the flow interview can be deleted.
Thanks for this, it was really helpful ❤ and I also had kind of same scenario. I didn’t use 2 auto launched flows. Everything worked out in single flow itself based on input and output variables.
@@paduarte In your case, you would still need two separate autolaunch flows (as you've done). That's because the user must make a decision and select one of (possibly) many opportunities to create a quote. A single autolaunched flow cannot pause to accept user input (like a screen flow). Instead, if you just wanted a table of related opportunities and a table of related quotes, then this could be done with just one autolaunch flow (since it wouldn't require additional user input).
@@neilhohmann10 So if you have an action button on a screen that "creates" a record based on user input, how would you create a new auto launch flow that would "update" the record created if the user changes the information on the screen? Like how would you get the recordid from the created record and use it in the update records?
More specifically, here’s the use case: As a user, I want to look up and select multiple Accounts and view the associated Opportunities per the selection in the data table on the same screen component
Am I able to call a screen flow? What I want is to create a quote record but I need some input from an user, thats why I need to call a screen flow. Is that possible?
Great use case. You can't launch a screen flow from a action button, unfortunately. I think you'd need to create a screen flow and launch if via a quick action, then within the screen flow you can have an action button that triggers a autolaunch flow - similar to the video.
Hey 👋🏻 Can you walk us through your use case in more detail? Are you trying to use a Action Button within a Screen Flow that just creates a new record? What would this new record be related to? You might be able to skip the 'get Opportunity' step in the video but it depends on your use case
Can it be used to create records or add contacts to existing accounts records? Like using existing global actions or existing buttons /actions,create record/new record?
Great question. Short answer, yes! Because the Action Button launches a separate flow, you can do a lot of different things. Using the example in the video, I created Quote records. The full capabilities on this functionality, however, will be discovered after full release and official documentation becomes available.
It's refreshing to hear someone say the truth about learning and the process of getting there. It's encouraging. Thank you for sharing your perspective and the demo.
Full transparency video. Thanks so much for your feedback! 🫶
Good video. In case you were wondering, the GUID is the ID related to the flow interview for when an auto-launched (or screen) flow executes. Useful if you want to query the FlowInterviewLog record and find information such as how long it took to run, or if the auto-launched flow is paused perhaps in a delay and you need to stop the flow from continuing, then the flow interview can be deleted.
This is SUPER helpful! Really appreciate the info. 💪🏻
Thanks for this, it was really helpful ❤ and I also had kind of same scenario. I didn’t use 2 auto launched flows. Everything worked out in single flow itself based on input and output variables.
So, you put get record and create record elements in the same flow, correct?
Oh really? That's interesting. I need to try again and see if I can get it all under one flow
@@paduarte In your case, you would still need two separate autolaunch flows (as you've done). That's because the user must make a decision and select one of (possibly) many opportunities to create a quote. A single autolaunched flow cannot pause to accept user input (like a screen flow). Instead, if you just wanted a table of related opportunities and a table of related quotes, then this could be done with just one autolaunch flow (since it wouldn't require additional user input).
@@neilhohmann10 So if you have an action button on a screen that "creates" a record based on user input, how would you create a new auto launch flow that would "update" the record created if the user changes the information on the screen? Like how would you get the recordid from the created record and use it in the update records?
Super helpful video!! Can the action item fetch multiple opportunities from a multi select account lookup?
More specifically, here’s the use case:
As a user, I want to look up and select multiple Accounts and view the associated Opportunities per the selection in the data table on the same screen component
Am I able to call a screen flow? What I want is to create a quote record but I need some input from an user, thats why I need to call a screen flow. Is that possible?
Great use case.
You can't launch a screen flow from a action button, unfortunately.
I think you'd need to create a screen flow and launch if via a quick action, then within the screen flow you can have an action button that triggers a autolaunch flow - similar to the video.
I am just trying to create a brand new record without getting any previous records for custom object, how would I use the recordId in input values?
Hey 👋🏻
Can you walk us through your use case in more detail?
Are you trying to use a Action Button within a Screen Flow that just creates a new record? What would this new record be related to?
You might be able to skip the 'get Opportunity' step in the video but it depends on your use case
Can it be used to create records or add contacts to existing accounts records? Like using existing global actions or existing buttons /actions,create record/new record?
Great question. Short answer, yes!
Because the Action Button launches a separate flow, you can do a lot of different things. Using the example in the video, I created Quote records.
The full capabilities on this functionality, however, will be discovered after full release and official documentation becomes available.
GUID means Globally Unique Identifier, or in this case, the flow interview ID. GUID is a more universal term.
Thanks for the explanation. The Flow Interview ID makes sense here, which is easier to remember :)
beautifully explained!
Hey 👋🏻
Thanks for taking the time to give your feedback!
Wow, I'm trying this out ASAP
Please do! Let me know how you find it 👍🏻
Can it print for instance the data from a data table
It essentially laucnhes a flow, so it works within the limitations of that.
thanks for putting this together!
Glad you liked it! 👋🏻
Very Nice Video!
Glad you found it helpful! Thank you for your feedback 🙌🏻
GUID = global unique ID. the flow's ID