This repository has been archived by the owner on Feb 4, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 8
Forms component #37
Comments
tomjanssens
pushed a commit
that referenced
this issue
Apr 30, 2015
tomjanssens
pushed a commit
that referenced
this issue
Apr 30, 2015
tomjanssens
pushed a commit
that referenced
this issue
Apr 30, 2015
tomjanssens
pushed a commit
that referenced
this issue
May 4, 2015
tomjanssens
pushed a commit
that referenced
this issue
May 4, 2015
tomjanssens
pushed a commit
that referenced
this issue
May 4, 2015
tomjanssens
pushed a commit
that referenced
this issue
May 4, 2015
tomjanssens
pushed a commit
that referenced
this issue
May 4, 2015
tomjanssens
pushed a commit
that referenced
this issue
May 5, 2015
tomjanssens
pushed a commit
that referenced
this issue
Jan 7, 2016
stevenrombauts
pushed a commit
that referenced
this issue
Jan 7, 2016
stevenrombauts
pushed a commit
that referenced
this issue
Jan 7, 2016
stevenrombauts
pushed a commit
that referenced
this issue
Jan 7, 2016
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Initial development of a Forms component, the form should be emailed to the zone and requester and stored as a fail save.
An ID should be generated and provided to the user as a fail save if he does not receive his email.
Store data in one JSON-fied column since searching the data is not required, and this allows to create different forms easily.
Requested by
Why we are not using CAPTCHAs: https://www.gov.uk/service-manual/user-centred-design/resources/captcha.html
http:https://www.dobt.co/screendoor/
The text was updated successfully, but these errors were encountered: