Add a way to configure public access links for multiple submissions

Open
#868 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
68/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
typescript
Domain
frontend

Research direction

Start by tracing the public access link submission-completion flow and the handling of the single-submission setting. Verify that when single submission is disabled, the completed form offers a “Fill out again” action and reloads for another response without requiring login or a manual refresh.

Written by the indexing model from the issue text.

Description

needs discussion
Description

When a public access link has single submission set to "no", after submitting the Web Form, the user should see the "Fill out again" prompt and be able to submit another response.


Checklist
  • Does it need UI/UX design?
    • Yes. Describe the UI/UX requirements or attach a Figma link in the "Design" section.
    • No
  • Does it need API design?
    • Yes. Specify the endpoints, methods, or data structures needed.
    • No
  • Does it need design around state flow?
    • Yes. Outline the state flow requirements.
    • No
  • Does it need a test plan?
    • Yes. Add the test plan as a comment in this task or attach the document.
    • No

User Stories
  • As a respondent using a public access link,
    I want to be offered "Fill out again" after I submit,
    so that I can enter another response without logging in or manually refreshing the page.

  • As a data collector filling out several follow-up forms on a keyboard,
    I want the form to reload for a new submission after each send,
    so that I can complete many entries in a row without extra steps.

Dominant language
TypeScript
Stars
38
Forks
24
PR merge metrics
No merged PRs in 30d

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from getodk/web-forms

All issues in getodk/web-forms

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.