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

LWC Wizard: Shouldn't enable the Activate & Save button if a trigger is still needed #1448

Open
aheber opened this issue Apr 7, 2024 · 0 comments
Assignees

Comments

@aheber
Copy link
Contributor

aheber commented Apr 7, 2024

Is your feature request related to a problem? Please describe.
The new LWC wizard allows you to attempt to activate a rollup if he trigger is not yet available but would be required by the rollup (Realtime OR Scheduled). Attempting to deploy the trigger at that time will cause a validation error to display.

Describe the solution you'd like
The button should not display until the trigger is recognized as being deployed to the org, ensuring the validation will pass.

I believe the LWC Wizard already has a method to handle when the Save and Active button should be enabled, you should be able to add more logic there to check the trigger state, which the LWC should already have stored in it's variabled, or at least retrievable. Look around at how we make the state check for the path configuration build.

Additional context
The button shouldn't have this requirement for Developer and Process Builder modes.

(Not the displayed mode values are different in the LWC Wizard but the record values are still the same.

@octatau octatau self-assigned this Apr 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants