Redirect users after form submission

After a user submits a web form instance, your application should direct their browser to an appropriate page to inform the user that their information was successfully submitted.

The mechanism for doing so depends on which of these options your application uses to render or deliver web form instances:

• Docusign JS
• Redirection to the Docusign platform
• Remote delivery

Form submission when rendering with Docusign JS

If your application uses the Docusign JS client SDK to render web form instances in an embedded iframe, you should implement listeners to detect events that indicate when a form submitter has finished their tasks. When the relevant event is triggered, your application can route the user to another page in your web application. See Form and envelope events for details about the events your application should use to trigger a redirect.

Form submission after a redirect to the Docusign platform

If your web application redirects users’ browsers to the Docusign platform for the display of web form instances, page display options after form submission depend on the type of web form configuration that is used to generate web form instances. See the next sections for details.

Instances generated from template-based configurations with embedded signing

In this scenario, web form instances are generated from a template-based web form configuration, and the configuration’s Initiate signing session from email setting is not enabled. This means that the envelope generated on web form instance submission is displayed in an embedded signing view within your web application. To redirect users’ browsers after envelope completion, your application can supply a returnUrl in the Instances:createInstance API request or an equivalent SDK method call that creates a web form instance. If you do not supply a returnUrl, the web form configuration thank you page is displayed after users complete envelopes.

Instances generated from template-based configurations with remote signing

In this scenario, web form instances are generated from a template-based web form configuration, and the configuration’s Initiate signing session from email setting is enabled. After submitting a web form instance, a user accesses the envelope on the Docusign platform via an emailed link (a process known as remote signing).The user is not routed elsewhere after signing, unless the web form template is associated with a brand that specifies a post-signing destination. See Destination URLs for Post-Signing Navigation for more information.

Instances generated from standalone configurations

For web form instances generated from standalone web form configurations, form instance submission does not generate an envelope. After form submission, Docusign displays the thank you page defined in the web form configuration. In the current release, there is no option to redirect users to another URL.

Redirects for remote web form instances

Redirects after submission for remote web form instances are supported through the branding feature. A redirect works only if the web form template or instance is associated with a brand, and that brand has a post-signing URL configured. A brand associated with a web form template will be applied by default to all web form instances created from that template. A brand supplied in an Instances:createInstance request overrides a brand associated with a web form template. Without a brand that includes a post-signing URL, a remote web form instance will redirect to a static, Docusign-branded page.

To configure a post-signing URL in a brand:

1. In your Docusign account, select Admin, then from the left nav, choose Brands.
2. Create a new brand; or select the brand you want to apply and choose Edit from the brand’s kebab menu; then, under Advanced Configuration, choose Destination URLs.
3. In the Signing Completed field, add the destination URL to which you want users routed after they complete the remote web form instance and envelope.

When the brand is applied to a web form template or instance, the Signing Completed URL from the brand’s configuration determines the redirect destination. See Apply custom branding for more information about how to associate a web form template or instance with a brand.

Next steps

• See Web form instance processing for an overview of the interaction between a user, a Web Forms API integration, and the Docusign platform.
• Review the process to deliver remote web form instances via email.
• See the options for rendering embedded web form instances.