Lightning Component input and output behavior in Salesforce Flows

When using lightning components in flows, the behavior of input and output variables can be really strange when navigating backward through the process. Should the component remember its default value or if the value has mutated, should it use the new value?
I've struggled with this a couple times on client work.

While not perfect, Alex Edelstein shares some tricks to getting it to behave the way you want. UnofficialSF

You'll only receive email when Scott McClung publishes a new post

More fromĀ Scott McClung