marlon | Posts: 18

Handover URL

0 votes
I am also finding it difficult to set the correct href. When I use the example 'www.google.com' when the button is clicked it has a query string attached. When I use a my own url urlencoded spaces are inserted or it redirects to esignLive's sandbox url and comes back with no transaction found. What am I doing wrong? I can open another post as it isn't fully related to Automatic redirect but what flag do I need to set to not show the dialog on complete. The one that says "Thank you for using eSignLive. You have completed signing all the documents required in the eSignPackage. What next?" Thanks, Marlon

harishaidary | Posts: 1812

Reply to: Handover URL

0 votes
Hey Greg, I think it might be due to the number sign in your handover url. Try changing it to http://localhost:12015/form/test/handover Let me know if this works.

ghutchinson | Posts: 4

Reply to: Handover URL

0 votes
The # sign is part of the out-of-the-box implementation of Angular. Normally we don't get rid of it.

harishaidary | Posts: 1812

Reply to: Handover URL

0 votes
Ah I see. Doing some research, it appears that the hashtag is used for non-HTML5. To get around it, you will need to use
$locationProvider.html5Mode(true)
To tell Angular that you are using an HTML5 browser. Your handover URL will then be "http://localhost:12015/form/handover" and you should be able to see the correct invoked url. More info about it here: http://stackoverflow.com/questions/14319967/angularjs-routing-without-the-hash

ghutchinson | Posts: 4

Reply to: Handover URL

0 votes
So how come when I decline the signing the url is correct: http://localhost:12015/form/#/handover/1234567890/003456718?package=MLjALzciU7u5iS9tfABfjtK5R38%3D&signer=Signer1&[email protected]&status=PACKAGE_DECLINE and yet when I confirm the signing the url is incorrect: http://localhost:12015/form/?email=greg.hutchinson%40fcc-fac.ca&package=DWinZ-IHroRdI7ybVzkW_ANXnw8%3D&signer=Signer1&status=SIGNER_COMPLETE#/handover/1234567890/003456718 It seems to me that the problem resides on the server side?!?!

harishaidary | Posts: 1812

Reply to: Handover URL

0 votes
I did a quick test on my side and set my handover url as "http://localhost:12015/form/#/handover". When I declined the package, I got redirected to:
http://localhost:12015/form/#/handover?package=9n8nezgnoRDyKHsGgzHo0KV5z40%3D&signer=contractor&email=price9872%40gmail.com&status=PACKAGE_DECLINE
And when I completed signing a package, I got redirected to:
http://localhost:12015/form/#/handover?package=H2YrMiYNFEaEv9zn_BaTCcJ6nEQ%3D&signer=contractor&email=price9872%40gmail.com&status=SIGNER_COMPLETE
It seems like eSignLive is redirecting to the correct url on my end (not using angular) so therefore I don't think the problem resides on the server side.

mwilliams | Posts: 957

Reply to: Handover URL

0 votes
Hey Marlon, I went ahead and moved this post to a new topic. For removing the dialog, you can either turn it off on your account by contacting support. Or you can turn it off on a transaction-by-transaction basis. See the events area of the payload in the following guide: Signing ceremony customization for the URL, are you putting "http://www.google.com" or just "www.google.com"?

marlon | Posts: 18

Reply to: Handover URL

0 votes
Thanks. Both, it seems with 'http' the %20 characters get inserted. Otherwise errors come up without http.

mwilliams | Posts: 957

Reply to: Handover URL

0 votes
Hey Marlon, Sorry for the delay. Can you post the payload you're passing and let me know what you're seeing for the handover URL? I'll do a little testing.

marlon | Posts: 18

Reply to: Handover URL

0 votes
Hi Michael, It is me who needs to apologise. The reason was because I was incorrectly formatting my JSON. Thanks for your help. Marlon

Hello! Looks like you're enjoying the discussion, but haven't signed up for an account.

When you create an account, we remember exactly what you've read, so you always come right back where you left off