Skip to main content

What I wanted:

I need to use both Remote Signing & Embedded Signing in a single DocuSign template (Single Signer). My goal is to redirect the user to a custom page once they complete the signing process, whether they sign through the flow page or via the email link I send for the signature in DocuSign.

What I've already tried:

  • I have tried implementing both BrandId (for remote signing) and ClientUserId (for embedded signing) in the same template.

  • This approach is working fine for embedded signing, but I am facing issues with remote signing:

    • The exception is thrown when using remote signing, and the user is not redirected to the custom page after signing.

What I know:

  • Signing Completed URLs can be set in In-session Landing Pages.

  • In-session Landing Pages are an account-level setting, and these settings apply to all templates in the account.

The Problem:

  • I want to redirect users to a custom page after signing, but In-session Landing Pages work at the account level, meaning they impact all templates.

  • Is it possible to have In-session Landing Pages at the template level to achieve this?

  • If not, what alternatives are available to redirect users to my custom page for both remote and embedded signing specifically for this template?

Additional Information:

  • I have also tried using the following reference link, but this solution did not work.

Expected Outcome:

  • A solution that allows both remote and embedded signers to be redirected to my custom page after completing the signing process for a specific template.

@Keval This should be possible following the steps shown on the below post by Inbar. 
https://stackoverflow.com/questions/78355400/redirect-to-specific-url-after-remote-signing-docusign-enveloppe

It sounds like you might already be trying this approach and mentioned “The exception is thrown when using remote signing”
Can you provide more input on what the exception you’re seeing is? 


@Koll.Klienstuber The solution you suggested is applicable when you wanted to use remote signing only. but I wanted to use both remote & embedded signing both in the single template.


Reply