-
Notifications
You must be signed in to change notification settings - Fork 972
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 Anywhere] Add confirmation dialog on closing flyout for Create & Associate flows with unsaved changes #4331
Comments
@KrooshalUX could you help us to check this change? |
@xeniatup can you assign this to the appropriate team member working on the feature? |
I believe that we should have a mechanism built into flyouts to better support for this since there can be many uses to where the use can fill out info in a flyout and submit the info. @KrooshalUX What are your thoughts on this as I think its should be a core functionality and not specific to Feature Anywhere. Then once the mechanism is built, the feature anywhere can be updated to utilize that flyout mechanism. |
@lezzago We are considering this change for OUI Flyout, but to unblock and deliver the correct experience for the Anywhere project, I would like to keep that scope separately. |
Is your feature request related to a problem? Please describe.
Feature Anywhere uses
OuiFlyout
for a variety of experiences inluding "Create/Associate" flows.Unsaved changes can be lost when flyout is closed.
Describe the solution you'd like
For the Feature Anywhere losing user's progress during Create or Associate flows is not ideal.
If the user has unsaved changes within the "Add alerting monitor", "Add anomaly detector", or "Set up alerts" flyouts and interacts with "Cancel" button in the flyout footer , flyout header "X" (close) or any clicks on the application header, present the user with a confirmation modal.
"Navigate away? Any unsaved progress will be lost." CTAs: "Navigate away" (primary), "Cancel" (secondary).
The text was updated successfully, but these errors were encountered: