Dreamforce 24 - Turn any Invocable Action into a Reactive Screen Component
I hope you were able to attend one of our sessions on how to use Invocable Actions reactively on a Flow Screen. Here is the link to all of the resources mentioned in the presentation.
https://docs.google.com/document/d/1EbWqUEs_2LvqqJ6hNeG7c_JSSX1vZAtWHkYfhAF-DwE/edit?usp=sharing
@Flow Reactive Screen Components (GA) @* Salesforce Administrators * @* Salesforce Developers * @* Salesforce Platform * #Flow #Screen Flow #Salesforce Developer #Apex #LWC #LWC Components #Dreamforce #Dreamforce2024 #Theater Sessions @Eric Smith @Adam White
I didn't attend DF24 so missed the session.
Looking through the presentation, slide 13 mentions using global for "max reliability". This isn't a good way of explaining why you might use global. Do you have a good reason for doing this? After all, this is only needed for cross-namespace-boundary use in general.
I'm also interested in why you stringify in the oldReactiveValue instead of using Object.assign or a spread operator based approach (slide 17) and exactly why you need this. I'm guessing it relates to handling previous/next navigation state in some way?