Once a user’s data has been collected and the user has confirmed that the data is correct, urls representing the required output of the data and any uploaded files are sent to the submitter api
In order to send a copy to the user, there must be an email address to send to:
- If a value has been defined in the service configuration for
emailInputNameUser
, the value entered for the control with that name is used as the user’s email address - Otherwise, if a control named
email
exists, the value for that is used
- Email message
/api/submitter/email/user
- PDF output
/api/submitter/pdf/default/:submissionId.pdf
In order to send the data to the service team, there must be an email address to send to. This address is set through the Publisher as a config param SERVICE_OUTPUT_EMAIL
- Email message
/api/submitter/email/team
- PDF output
/api/submitter/pdf/default/:submissionId.pdf
- CSV (TODO)
It is possible to get raw JSON for a submission from the Runner application. Currently this is forwarded onto adapters to make external API calls. In order to use this, two config params are required. SERVICE_OUTPUT_JSON_ENDPOINT
and SERVICE_OUTPUT_JSON_KEY
.
The endpoint to which this JSON will be forwarded.
A JWE key used for encrypting the data. This key has to be exactly 16 bytes.
- API endpoint
/api/submitter/json/default/:submissionId.json
In future, it will be possible to define alternative outputs
TODO: output specification
The Submitter is an app that provides an API and workers for dealing with a form’s submissions.