Submission notification behavior

The Submission notification behavior can be used in a form so that app user responses are sent to recipients in real time via email.

App user feedback, requests or reports can therefore be communicated directly to the relevant persons, such as help desk staff or a bookings office, for immediate action.

Important: Please note that the Submission notification and Reset after submit behaviors cannot be used at the same time on the same form, as this would cause the behaviors to not work correctly.

Use case example: Event feedback surveys shared with event team

The submission notifications behavior can for example be used to share an event feedback form with the event team.

Follow the below steps to use the submission notification behavior in a feedback form.

1. Go to the feedback form that you wish to configure, and open the form display template:
   
2. In the Behaviors section, go to the Available new behaviors list and add the Submission notification behavior to the page.
3. Now select the Submission notification behavior. On the panel to the right, add the event team's email address(es), as well as the email body (i.e.the text that will be included as the heading of the email).
   
   Here you can use metadata to ensure that the form is adapted to the app user who you are collecting and sharing the feedback for, by using the {{activatedPerson.fname}} metadata instead of the standard {{fname}} metadata (more information on this below at the end of this article).
4. Click Save to finish configuring the behavior.

Submitted form responses will now be sent directly to the configured recipients. 

Note: This approach can be used for any other types of form that app users fill in, in order to share their input directly with third parties via email. Examples could be an incident report, a booking form, a questionnaire, etc.
Please note that the app user's device needs to be online for the email to be sent. If a form is submitted while the device is offline, the email will only be sent once the device is back online.

Received email

The email received for the above example will look like this:

The email template that is used to send these email notifications is the following:

This email template can be edited based on your needs.

Please be aware that in this specific template, if you include the first name of the user by adding a merge tag for first name or by typing {{fname}}, the merge tag or metadata will only work when sending the email manually from Backstage manually. If an app user actually submits the form, the merge tag or metadata will not be replaced correctly with the attendee’s data.

For things to work correctly, instead of {{fname}} you will need to use the {{activatedPerson.fname}} metadata in the email template or in the Email body field of the Submission notification component in the form:

This approach is applicable for any User merge tag or metadata that you want to add to this specific template. You will always need to edit the merge tag or metadata by adding “activatedPerson” to the start of it (the same as explained above).

Editing the merge tag or metadata by adding “activatedPerson” to the start of it will make sure that the metadata or merge tags work properly in the received email when an app user submits the form. However, please be aware that these edited metadata or merge tags will not work as intended if the email is sent manually from Backstage.