Lightning_FlowScreen support#71
Open
JeroenSfdc wants to merge 2 commits intoSalesforceLabs:masterfrom
Open
Conversation
Author
|
@victorgz any chance you feel this PR could be a reasonable enhancement? |
This file contains hidden or 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
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.
This will support Lightning_FlowScreen as target. See issue #66
Description
datasourceattributes as these are not supported today by Flow.Motivation and Context
#66
Flow is a very relevant target to show Charts.
How Has This Been Tested?
Ceated a demo Flow.
Screenshots (if appropriate):
Types of changes
This can break for package upgrades, as there is a bug with updating an pre-existing targets, when a Lightning_FlowScreen is being added. GUS Work Item: W-9032710
Checklist: