Kosta's account

Hello Haris, thank you very much for the update. I will follow your example. Regards, Kosta.

Hello Haris, thank you very much for the suggestion. The code you provide:

eslClient.getPackageService().archive(packageId);

worked fine. What we had was:

documentPackage.setStatus(PackageStatus.ARCHIVED);
eslClient.updatePackage(packageId, documentPackage);

Just to show how we managed to create "our" - "hidden" signature, please check code below:

SignatureBuilder signerSignature = SignatureBuilder.signatureFor(signer.getEmail()).withSize(0, 0);
documentBuilder.withSignature(signerSignature);

And we are able to sign it using:

eslClient.signDocuments(packageId, EslResource.generateIdFromString(email));

where: EslResource.generateIdFromString(email) is our custom code which we use to generate unique Signer ID based on the Signer email. Thank you very much for your quick help, one more time :)

Hello Haris, Thank you very much fore the update. I think it would be handy if we could have some sort of PackageDocument pre-validation before we call eslClient Create Package. For example:

try {
   eslClient.validatePackageDocument();
} catch (EslException e) {
   //ECHO there was problem with Package set up!!!
   System.out.println(e.getMessage());
}

In the mean time I will check the provided URL . Regards, Kosta.

Thank you very much for the suggestion Haris, I created the request as suggested. Validate PackageDocument before Package Create or Create&Send

Hello Haris, could you please check the raised enhancement suggestion that I did (link in my previous post) and check if this has been checked or not? It's being more than a week since I created it and there were no comments on this. Thank you in advance. Kosta.