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

[CAL-5200] Prevent duplicate submissions in Routing Form. #19481

Open
hariombalhara opened this issue Feb 24, 2025 · 0 comments
Open

[CAL-5200] Prevent duplicate submissions in Routing Form. #19481

hariombalhara opened this issue Feb 24, 2025 · 0 comments
Assignees
Labels
routing-forms area: routing forms, routing, forms

Comments

@hariombalhara
Copy link
Member

hariombalhara commented Feb 24, 2025

Things to think about:

  • How does one determine if it is exact duplicate from the same person?
    • Can we assume that if email field is there, then only we implement this. Otherwise, it could be that same reponse could be from some other person?
  • For how long should we consider a duplicate a duplicate?
    • If a person submits the exact same response after a month, would it still be considered a duplicate?
  • What should happen if the duplicate is submitted?
    • Should we error? - Easiest
    • Should we route to the booking success page if corresponding booking has been submitted already? Makes the most sense.
      • We could show some toast e.g. that mentions that you have been taken to already submitted booking's page.
    • What if the route's action was to redirect to an external page or show custom message?
      • I think it just makes sense to repeat the redirect or show custom message again.

From SyncLinear.com | CAL-5200

@hariombalhara hariombalhara self-assigned this Feb 24, 2025
@dosubot dosubot bot added the routing-forms area: routing forms, routing, forms label Feb 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
routing-forms area: routing forms, routing, forms
Projects
None yet
Development

No branches or pull requests

1 participant