This is a memo from the Flow product team. Some customers have noted that, for some screen components, the behavior of the help text button recently changed from “hover to see help” to “click to see help”. Here’s some background behind that change. Originally, all Flow screen components supported formatting, embedded images, and embedded links […]
About Alex Edelstein
This author has yet to write their bio.Meanwhile lets just say that we are proud Alex Edelstein contributed a whooping 236 entries.
Entries by Alex Edelstein
This video shows an actual orchestration created by Orchestrator product manager Abhishek Sharma in collaboration with pilot Orchestrator customer Eigensonne: In this demo, you can see Orchestrator’s new beta features, including autolaunched flow support and go-to connectors for routing to a previous stage. Learn more about Orchestrator.
Salesforce is currently piloting a feature called Reactive Screens that allows builders to pipe the output from one screen component to the input of another screen component on the same screen. Each time the source component changes its output, the target component dynamically updates and refreshes. To explore the possibilities of this, we created a […]
The world of configuring the right access to Flows is rich and evolving. This post on Custom Settings is a noteworthy addition to the canon: Check it out!
Great new in-depth video on this new Flow feature:
The Omnichannel team has been doing some leading-edge work exposing their capabilities as Flow Actions. Here’s a great new video: Check it out!
This request came in: I have a customer trying to implement limiting re-offers, but wants to have differing time periods based on whether a user accepts or rejects the offer. Specifically, a recommendation should appear after 6 months if the recommendation is rejected, and 4 months if the offer is accepted. This canbe done with […]
Check it Out!
Check it out:
Another nice overview: