Forms
Table of contents

Ending screen

Easily configure the ending screen of your form, which is displayed right after the user clicks the submission button. Set the thank you message and perform operations in the user's browser by simply referencing variables from the form and the flows connected to it.

The ending screen consists of four modules that are executed, from top to bottom, in the same order in which they are shown in the drop-downs. None of them are mandatory, so you can activate or deactivate the ones you need by clicking on the ON/OFF button.

Thank you block

Set here the thank you message that will be displayed after form submission. Just write the message here or use HTML to layout it, add links, images, etc. 

Include variables from the form using the {{fields.fieldId}} syntax or by clicking on the plus button to get the proper variable from the autocomplete menu. 

You can also reference variables from the flow with the {{state.variableId}} syntax or by clicking on the plus button after a submission of the form.

For example, this option will be useful for you if you need to show a different message based on  user responses and the conditional logic defined in the flows.

To configure this, include a ‘Store state variable’ action in each branch of the flow, set a variable 'message' variable on them and write the text that will be displayed in each case.

Just remember that you need to include this action in the flow and define in it the variables that you want to reference in the form or the ending screen.

User session

Initialize a user session with the identity provider configured in the flows linked to the form.

To log the user in, just select the identity provider from the selector and reference the token variable from the flow using the {{state.variableId}} syntax. It will be automatically exchanged for a session token from the selected identity provider.

Remember to include a ‘Store state variable’ action in the flow to set this variable by referencing the token from the outputs of the previous ‘Issue a token’ action.

JavaScript callback

Run custom JS scripts before redirecting the user. You can use this field, for example, to add the SDK for identity providers whose native integrations are not yet available in the editor or to track in your analytics tool that the submission has been successful.

Note that you can set both synchronous and asynchronous actions in this field. In the event that the asynchronous request takes too long, the redirection will be automatically executed.

To prevent the callback from not being finished if this happens, return a promise in the script to make the process wait for it to be executed before the redirection.

Redirection

Set the URL to which the user will be redirected when logging in. 

Set the variable in a ‘Store state variable action’ of the flow and reference it here using the {{state.variableId}} syntax or get it from the autocomplete menu by clicking on the plus button after an execution of the flow.

Another option is to input the URL and the token variable in this field, after defining it in the flow action. For example, https://www.arengu.com/{{state.token}}.

Once it is configured to your needs, publish the changes, click on the 'Preview' button and test it.