Account


Earned badges

Achievement: Latest Unlocked

Topic Started

Topics
Hello, I am running into an issue when attempting to remove a partially signed document from within a transaction.
Hello, I am looking through the Java SDK for a way to programmatically lock a signer, I've attempted to use the PackageService.updateSigner() method but found that it won't update the locked flag on
Hello, We're currently running into an issue when the sender of a in person package also needs to sign a document within that package.
Hello, I'm looking for a way to unlock a sender through the Java SDK.
Hello, Hopefully a quick question, but I'm attempting to use the DownloadedFile class (com.silanis.esl.sdk.io.DownloadedFile) when downloading signer attachment files using the line:
DownloadedF

Replies Created

0 votes
Hi Haris, Sorry about the name/description confusion we've been using the terms interchangeably when talking about the issue. As for the length of the String, that example code is using the actual piece of text "description" and is not a placeholder for a longer piece of text, I've also just tried with a single character to be sure and the issue still occurs. For the Placeholder("customId", "customId"); example, that was just included to show that using the placeholder constructor with both parameters will only seem to work when both of the parameters are identical. Is this an eSignLive issue?

0 votes
Hi Haris, I think if found the underlying issue, it looks like there's a bug in the LayoutService applyLayout code. It seems that when applying the layout to the document, the method looks to be trying to match the name of the placeholder specified in the layout to the ID of the placeholder specified in the SignerBuilder.replacing method of the end package. Here's some sample code showing this in action. Notice the two different placeholders, one for the layout and one for the signer of the end package, while they have different ids and names the second placeholder's id is the same as the first placeholder's name. After running the code, even though the ids and names of the placeholders are different, the signature created in the layout is successfully applied to the end package and can be signed successfully. Also notice that if you use either placeholder in both locations, the layout can no longer be applied. Please take a look at this and run the sample code provided to see if you can confirm this as a bug in eSignLive
    //ID of the package signer placeholder must match the name of layout placeholder
    Placeholder layoutPlaceholder = new Placeholder("anyId", "mustMatch"); 
    Placeholder packageSignerPlaceholder = new Placeholder("mustMatch", "anyName"); 

    // Create Layout to apply to the package   
    DocumentPackage eslLayoutPackage = PackageBuilder.newPackageNamed("layoutPackage")
      .withDocument(
        DocumentBuilder.newDocumentWithName("layoutDocumentName")
          .withId("layoutDocumentId")
          .fromStream(layoutStream, DocumentType.WORD)
          .withSignature(SignatureBuilder.signatureFor(layoutPlaceholder).onPage(0).atPosition(150, 150))
        .build()
      )
      .withSigner(
        SignerBuilder.newSignerPlaceholder(layoutPlaceholder).build()
      )
    .build();

    PackageId layoutPackageId = eslClient.createPackage(eslLayoutPackage);
    eslLayoutPackage.setId(layoutPackageId);
    String eslLayoutId = eslClient.getLayoutService().createLayout(eslLayoutPackage);
    eslLayoutPackage.setId(new PackageId(eslLayoutId));

    // Create Package
    DocumentPackage eslPackage = PackageBuilder.newPackageNamed("packageName")
      .withSigner( SignerBuilder.newSignerWithEmail("[email protected]")
        .withFirstName("First")
        .withLastName("Last")
        .replacing(packageSignerPlaceholder)
      )
      .withDocument(DocumentBuilder.newDocumentWithName("packageDocumentName")
        .withId("packageDocumentId")
        .fromStream(documentStream, DocumentType.WORD)
      )
    .build();
    
    PackageId eslPackageId = eslClient.createPackage(eslPackage);
    eslPackage.setId(eslPackageId);

    eslClient.getLayoutService().applyLayout(eslPackage.getId(), "packageDocumentId", eslLayoutId);
Thanks, Mitch

Subscriptions

Topics Replies Freshness Views Users
Hello, I am running into an issue when attempting to remove a partially signed document from within a transaction.
12 6 years 11 months ago 64
Profile picture for user harishaidary
Profile picture for user mwilliams
Hello, I am looking through the Java SDK for a way to programmatically lock a signer, I've attempted to use the PackageService.updateSigner() method but found that it won't update the locked flag on
10 6 years 7 months ago 78
Profile picture for user harishaidary
Hello, We're currently running into an issue when the sender of a in person package also needs to sign a document within that package.
1 7 years 1 month ago 35
Profile picture for user harishaidary
Hello, I'm looking for a way to unlock a sender through the Java SDK.
3 7 years 2 months ago 48
Profile picture for user harishaidary
Hello, Hopefully a quick question, but I'm attempting to use the DownloadedFile class (com.silanis.esl.sdk.io.DownloadedFile) when downloading signer attachment files using the line:
DownloadedF
1 7 years 5 months ago 7
Profile picture for user harishaidary

Code Share

This user has not submitted any code shares.

Subscriptions Release Notes

This user is not subscribed to any release notes.