Reply to: Callback endpoint while creating eSignLive package using Java SDK
Thursday, February 1, 2018 at 06:52am
0
votes
Hi Sudipta,
What would be the reason for this? Callback notifications are on an account level and if you change the endpoint for every package, then you run the risk of missing a big chunk of them.
Reply to: Callback endpoint while creating eSignLive package using Java SDK
Thursday, February 1, 2018 at 07:19am
0
votes
We wanted to set the callback at package level so that we can setup custom query parameter (say, ) which will be unique for a package. We need this parameter (id) to be appended to the callback url so that we can uniquely identify the package in the response. We do not save the packageid in our DB. So, only way we can identify a package in callback is by the unique value of the parameter appended to callback url.
We are using the following code to generate the package. We are expecting PackageBuilder to provide us a way to set the callback url while creating the package.
Document document = new Document();
document.addSignatures(signs);
document.setContent(DatatypeConverter.parseBase64Binary();
document.setName("TestDocument");
document.setFileName("TestDocument.pdf");
DocumentPackageSettings settings = DocumentPackageSettingsBuilder
.newDocumentPackageSettings()
.hideOwnerInPersonDropDown()
.withoutDocumentToolbarDownloadButton()
.withoutDialogOnComplete()
.withoutCaptureText()
.withDecline()
.withoutInPerson()
.withoutOptOut()
.withoutOptOutOther()
.withoutWatermark()
.withoutDialogOnComplete()
.withoutLanguageDropDown()
.withCeremonyLayoutSettings(CeremonyLayoutSettingsBuilder.newCeremonyLayoutSettings()
.withoutNavigator()
.withoutGlobalNavigation()
.withoutBreadCrumbs()
.withoutSessionBar()
.withoutTitle()
.withoutIFrame()
.withoutGlobalConfirmButton()
.withoutGlobalDownloadButton()
.withoutGlobalSaveAsLayoutButton()
.withLogoSource(null))
.build();
PackageBuilder packageBuilder = newPackageNamed("uSign Transaction " + format.format(new Date()))
.withSigner(newSignerWithEmail(email)
.withCustomId(uSignId.toString())
.withFirstName(signerFirstName)
.withLastName(signerLastName));
final DocumentPackage documentPackage = packageBuilder.withDocument(document).withSettings
(settings).build();
Reply to: Callback endpoint while creating eSignLive package using Java SDK
Thursday, February 1, 2018 at 07:25am
1
votes
The callback notification feature is on an account level. That cannot be changed. However, what you can do is store the parameter in the package as attributes. Hence, when you receive the callback notification, you simply use the package id returned by esignlive to retrieve the package attribute and match it with your application. Here's a guide on how to add package attributes: https://developer.esignlive.com/guides/feature-guides/package-attributes/
Reply to: Callback endpoint while creating eSignLive package using Java SDK
Thursday, February 1, 2018 at 06:52amReply to: Callback endpoint while creating eSignLive package using Java SDK
Thursday, February 1, 2018 at 07:19amReply to: Callback endpoint while creating eSignLive package using Java SDK
Thursday, February 1, 2018 at 07:25amReply to: Callback endpoint while creating eSignLive package using Java SDK
Thursday, February 1, 2018 at 07:31amReply to: Callback endpoint while creating eSignLive package using Java SDK
Thursday, February 1, 2018 at 07:40amReply to: Callback endpoint while creating eSignLive package using Java SDK
Thursday, February 1, 2018 at 07:47am