URL Redirect cases not working

Hey Ryan, For #1, there is a slight issue with the curly brackets that's causing your issue. This should work:

"settings": {
    "ceremony": {
      "hidePackageOwnerInPerson": true,
      "optOutButton": false,
      "layout": {
        "brandingBar": {
          "logo": {
            "src": "http://www.mortgagelaw.com/images/logo-medium.png",
            "link": ""
          }
        }
      },
      "events": {
        "complete": {
          "dialog": true,
          "redirect": ""
        }
      },
    
    "handOver": {
      "title": "You will now be redirected to GOOGLE!",
      "href": "https://www.google.com",
      "text": "Continue to exit!"
    }
    }
  }

For #2, there isn't a way to specify a different handover or just a handover for a particular signer, however, we do have our JavaScript event notifier, which it sounds like you might be able to use since you're embedding in an iFrame. Take a look at this: https://www.esignlive.com/blog/esignlive-event-notifier This would allow you to track signer completion in the embedded ceremony and redirect on your own.

mwilliams - For issue 1, what I pasted was only a small snippet of the code I'm using. All brackets are there, just not displayed in the code above. ha. This does not actually work as the user isn't redirected once the dialog pops up. For issue 2, I'll look into the JavaScript event notifier.

On #1, it definitely works. I tried it with what you had and got the same experience that you described. Then, switched them so that handOver was inside the ceremony object and it then worked fine. It wasn't a case of missing brackets. If you notice, I removed the closing curly bracket under "events" that closed off the "ceremony" object before the "handOver" object. I moved the comma up to behind the "events" block, then, added the removed curly bracket down below the "handOver" block to close the "ceremony" block in the proper place. Where you close it, "handOver" is part of "settings" and isn't recognized. You can test this in Postman by creating a package in the OSS UI, grabbing the Transaction ID from the URL, and then passing a PUT request to https://sandbox.esignlive.com/api/packages/{packageID} with Authorization: Basic {APIKEY} and Content-Type: application/json headers and a body that contains the JSON from each of our posts inside a set of curly brackets '{}'. If you're unable to test this out, please send me the larger JSON to [email protected]. I'll make the change in it and send back to you. On #2, let me know if you run into any issues. :)

mwilliams - Thanks for clarifying that one as I didn't notice. That was exactly my problem and once I moved it into the ceremony object, it worked. I hate to ask but what is the difference between the HandOver object and the Complete object in the events object? They both have a redirect. What I did notice is that when I have multiple signers, including a notary, once a signer has finished, it will then redirect them to that new site, regardless of the fact that there are other signers. Is there a way to only get a redirect at the end of the total package and not after each signer?

I believe the redirect on the complete object is a placeholder for when auto-redirect is completed as a feature. As of right now, I don't think it does anything. As for allowing the redirect only after the last signer, this isn't currently available. This feature is typically only used for remote, integrated solutions, but I can see how this would be an issue if embedding an in-person ceremony into an application. The only things I can request, at this time, are to file an Enhancement Request with support and to look at using the JS event notifier I mentioned above. This would allow you to remove the handover URL and simply handle the redirect on your own.

mwilliams - Thanks for the information. I am leaning more towards the JS Event Notifier at this point as it looks more like something that we will be leveraging.

Great! Let us know if you have any questions on that!

Hello, I am trying to redirect back to my application after the user defines the signature regions and assigns signers to the document. But the system leaves me in the page: https://sandbox.esignlive.com/designer_sent Without allowing me to return to the application. Please help. Here is my JSON object:

{
	"roles": [
		{
			"id": "1",
			"signers": [
				{
					"firstName": "Victor",
					"lastName": "Gonzalez",
					"company": "VGO",
					"email": "[email protected]"
				}
			]
		}
	],
	"documents": [
		{
			"content": "file content",
			"name": "test_V1.pdf",
			"signatureFields": [
				{
					"page": -1,
					"x": 260,
					"y": 612,
					"signerIndex": 0,
					"patternName": null,
					"label": null
				}
			]
		}
	],
	"settings": {
		"ceremony": {
			"hidePackageOwnerInPerson": false,
			"optOutButton": false,
			"layout": {
				"brandingBar": {
					"logo": {
						"src": "",
						"link": ""
					}
				}
			},
			"events": {
				"complete": {
					"dialog": true,
					"redirect": ""
				}
			},
			"handOver": {
				"title": "You will be redirected to Google.",
				"href": "https://www.google.com",
				"text": "Continue to Exit"
			}
		}
	}
}

Hello Vgo, If I understand it correctly, what you mentioned: "after the user defines the signature regions and assigns signers to the document" refers to the Designer Page, where there are no redirect options/configuration yet. Most of the integrators choose below two workarounds to facilitate their workflow: (1) embed the designer into an iFrame, and add a redirect button outside the iFrame area. (Refer to this blog) (2)put the designer into a modal window, and add an "X" edit button at the top right. (Refer to this blog) I have two blogs demonstrate to you the above two workarounds. Kindly have a check with them! Duo

Thank you Duo! will check it out!