A form is closed with information on what an end-user should do next.

srtalbot commented 2 years ago

User story: As a program administrator I need to let people know that a form is no longer active with error messaging So that when they navigate to the form they have the context they need to know it is closed

Story context Example of the issue experienced by the Red Pine team, who were using forms to screen research participants.

Finding from testing of the response UI

This need mainly affects forms where the entry path (that is, how people find the form) is an email or basically isn't a link to the form that we can take down.

Even in the case when an external page links to the form and we can remove it, it may be the case that an end-user has saved the form URL and will return to the form to complete it. The likelihood of this scenario increases as we start to allow saving form data (a known feature that we'll get to at some point)

The error message needs some form-specific content on it

Acceptance criteria

[x] Allow form builders to provide form-specific context and information when a form is closed.
[x] Provide guidance on what to include (like, a link back to the webpage for the department, or someone to contact, or a new form they've published.)
[x] Allow clients to set a time and date in the future when it closes
[x] Provide a banner on the form that let's end-users know that a date and time to close has been set.
[x] Error page provides equal service in French and English.
[x] Error page works on Chrome, Firefox, Edge, Safari, and Opera.
[x] H1 provides the main context and a screen reader doesn't have to tab or move to it
[ ] manual accessibility testing meet WCAG 2.1 AA requirements.

srtalbot commented 2 years ago

Could take about a week and a half to complete the card.

craigzour commented 2 years ago

Do we think we will need such feature (marking a form as closed) in the future? Thinking this would probably be the best approach if we want to do something clean. If not then we can think of a different solution but it will probably end up being a "hacky" one. Something like adding a property to the JSON template to explicitly say that this form is not available.

jeberhardt commented 2 years ago

This could be handled in a similar way that the "endPage" content is handled. If the content is there, then the form is closed, and that content could be displayed.

samsadasivan commented 1 year ago

Form is closed

This is the page that will be displayed when a user deletes a form. This page would appear when someone archives or "unpublishes" their form in the future.

This screen exits under the "Delete a published form" flow ![image.png](https://images.zenhubusercontent.com/611408c194b5030c28d18261/5ac22278-145c-4998-89df-404c664f21d9)

patheard commented 2 months ago

One of the action items that could fit in is around how we could notify a user that the form they currently have loaded in their browser can no longer be submitted:

Display “Closed form” message when a lookup for a form ID is retrieved and the form is marked for deletion.

This could also be a scheduled check that occurs when a form is loaded in a browser to alert the user sooner. Use Google Analytics to determine the length of time people will sit on a form.

We will need research to determine messaging to the user (perhaps falls into the form owner’s responsibility bucket and the custom Close Form message should be used).

connorscarolyns commented 1 month ago

Designs exist for this, they should be reviewed against the new context: https://www.figma.com/design/SBkP2G0bV4jwoghIvlZ1zg/v2.-Download-and-confirm-responses?node-id=3131-70222&t=ON16jdF7baAhwQfE-4

srtalbot commented 1 month ago

Feedback from a client:

"I think it would be really helpful if a notification was sent when a form is closed – this would help avoid accidental closure."

timarney commented 1 month ago

@samsadasivan is the figma above the one to use for this?

timarney commented 1 month ago

@thiessenp-cds

Please break out a todo list on the dev side i.e.

[ ] Review Figma designs
[ ] Update DB schema to handle close message
[ ] Update server callbacks to handle updating DB
[ ] Update front facing form
[ ] Update settings page etc..
[ ] Add end to end test
[ ] ++

This will make it easier to discuss progress in stand-up but give us a better sense of how long the feature will take.

samsadasivan commented 1 month ago

PROPOSAL: Very similar to the designs @connorscarolyns already proposed. I added some pieces for the extra scenarios considered around notifications and banners.

Notes:

You can open and close via the toggle.
Ability to set a date and add a custom message is available whether the form is open or closed
You can set a bilingual message using the same editors we have for the Translation page.
You can set a date through month/day/year
You can set a timezone and time in 24 hours
User presses "Save" submit the action
A email notification will be sent out to all the owners of the form that [user email] has closed a form.

samsadasivan commented 1 month ago

TRANSLATION VIEW

The editors will reflect the same view you see in settings, to provide a holistic view for content translation

samsadasivan commented 1 month ago

Form closed automatically via set date > user re-opens via toggle

Toggle closes with an info-alert to let users know when the form closed
Users can toggle the form back open and set a new date
Email notification let form owners the form has been opened again

samsadasivan commented 1 month ago

Content design, cc: @anikbrazeau

timarney commented 1 month ago

Going to propose we tackle this in a few iterations:

Update 1 - Adding the custom description message (using existing toggle) -> ship

Update 2 - Add email functionality to notify form owners a form has been closed (using existing toggle) -> ship

Update 3 - Custom closing date + the rest of the functionality -> ship

This will keep the PRs small
Make the iterations easier to test
Ship sooner building up the feature as we go.

cc: @Abi-Nada @srtalbot @samsadasivan @thiessenp-cds thoughts?

samsadasivan commented 1 month ago

Love it - thank you @timarney !

samsadasivan commented 1 month ago

One outlier - I am going to look into this morning: Banner for the form output that a form will be closing. Just checking with DS

anikbrazeau commented 1 month ago

Some content considerations

cc: @samsadasivan

Consider displaying when the form was closed to end users trying to fill out the form (ex: Form closed October 9, 2024 at 11:53 am ET)
Consider providing guidance to clients that they should customize the message with "why" it closed and "where to go" or "what to expect next" (ex: Let people know why the form is now closed, whether it will reopen, and/or give them a next step.)
Consider updating the email notification text to be bilingual (perhaps even include when it was closed if it's not instantly sent):
- EN: [user name] closed the form: [EN form title].
- FR: [user name] a fermé le formulaire : [FR form title].
In tandem with this change, might we also want a notification when a published form is opened or when it is deleted?
Consider clarifying the timezone, is it ET or wherever the user is or however the system is set?
For the date part, consider "Schedule the form's closing time" + Error: "Must a future date and time"
In French, for this can we do [Date] [Month] [Year] as the fieldset, the order is different from English format for a plain language date (ex: September 12, 2024 = 12 septembre 2024)