Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FEATURE] Require a Selection #3

Open
roanbear opened this issue Mar 29, 2023 · 0 comments
Open

[FEATURE] Require a Selection #3

roanbear opened this issue Mar 29, 2023 · 0 comments

Comments

@roanbear
Copy link
Collaborator

roanbear commented Mar 29, 2023

Right now the LWC is aware of the number of records selected and can present them to a variable that the flow can read.
image
The flow needs to validate that records have been selected.

Ideally there could be a setting requiring at least a single field selection so that the flow doesn't have to handle the validation.

  • Have a setting requiring a minimum selection (defaults to 1)
  • Setting a maximum number of records (defaults to 0)
@roanbear roanbear changed the title Require a Selection [FEATURE] Require a Selection Sep 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant