divakar-loganathan

Signature Block appearing on top left of 1st page of doc for multipage doc

0 votes
Hi Team / Duo, Greetings for the day. I'm facing an issue, I have form that gets generated in my system (and the number of pages is dynamic based on the inputs) So there are cases where the PDF has multiple pages (template is same PDF with multiple occurrences with different data, say for eg: if you have 100 items in input, the pdf might have 5 pages with 20 items in each page, so the template is same and repeats.) Now in multiple occurrences, I want the signature block to be available in all the pages of the PDF, I have attached the code snippet where I add signatures(I tried pasting it here but the blog doesn't allow me to save with code in the post) But the issue I'm facing is in this case, the signature block is appearing on top left side of the first page in the document (and all the 5 signatures for the 5 pages are being overlapped in the same position (please find the image attached) As you see, the sysout's statements show that the signature are in correct pages (Please find the attached imaged for eclipse console output) Kindly shed some light on this issue. Thank you very much in advance.

Reply to: Signature Block appearing on top left of 1st page of doc for multipage doc

0 votes
Hi Logan, I saw that you were using same PDF form name for multiple occurrences, I believe this is why OneSpan Sign system can only recognize the last occurrence's location and all five signatures are overlapped together. It doesn't explain why it displayed at left-top corner, but still, is it possible for your pdf generator to have different PDF form names? If that's the case, I've created some sample code in another thread, which I believe is very similar to yours:
	public static void main(String[] args) {
		final String API_KEY = "your_api_key";
		final String API_URL = "https://sandbox.esignlive.com/api";

		EslClient eslClient = new EslClient(API_KEY, API_URL);

		 PackageBuilder packageBuilder = PackageBuilder.newPackageNamed("Example Package " + System.currentTimeMillis())
				.withSigner(SignerBuilder.newSignerWithEmail("[email protected]").withFirstName("John")
						.withLastName("Smith")
						);
		
		
		Document document = DocumentBuilder.newDocumentWithName("document 1")
		.fromFile("your_file_path")
		.enableExtraction()
		.build();
		
		List signatureList = new ArrayList();
		signatureList.add(SignatureBuilder.signatureFor("[email protected]").withName("ExecutedBy_p1")
				.withPositionExtracted().build());
		signatureList.add(SignatureBuilder.signatureFor("[email protected]").withName("ExecutedBy_p2")
				.withPositionExtracted().build());
		signatureList.add(SignatureBuilder.signatureFor("[email protected]").withName("ExecutedBy_p3")
				.withPositionExtracted().build());
		signatureList.add(SignatureBuilder.signatureFor("[email protected]").withName("ExecutedBy_p4")
				.withPositionExtracted().build());
		signatureList.add(SignatureBuilder.signatureFor("[email protected]").withName("ExecutedBy_p5")
				.withPositionExtracted().build());
		
		document.addSignatures(signatureList);
		packageBuilder.withDocument(document);

		PackageId createPackageOneStep = eslClient.createPackage(packageBuilder.build());
		System.out.println(createPackageOneStep);

	}
Kindly have a try and tell me if this is what you expected. Duo

Duo Liang OneSpan Evangelism and Partner Integrations Developer


Attachments

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