support prior return values #3565
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@yippie Thanks for the contribution! I was honestly surprised we didn't have this already; it's a good addition. Could you add a new test to validate the change? Let me know if I can provide guidance on our testing strategies. |
|
Thanks for the contribution! Before we can merge this, we need @yippie to sign the Salesforce Inc. Contributor License Agreement. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Using prior values in options is wonderful. The "when" clause in flows, however, is not so much as it is VERY limited what you can base it off of.
To make things much more powerful with minimal work, I have extended the prior value syntax support into when clause of the flow runner.