Skip to main content
Mitratech Success Center

Client Support Center

Need help? Click a product group below to select your application and get access to knowledge articles, webinars, training content, and release notes or to contact our support team.

Authorized users - log in to create a ticket, view tickets status and check your success plan details.

 

TAP 1.15.7 Release Notes

  1. Last updated
  2. Save as PDF

Bug Fixes

Issue: Contract Signature block in incorrect place on contract when sending to TAP and signer, Long Form issue
Tracking Code: TAPSUP-7345
Case Number: 2023-0829-7964832
Reported Version: 1.14.3.0

Workaround
None

Pre-Requisites
Access to TAP Prod

Steps to Reproduce

  1. Import the workflow.
  2. Publish and save the workflow.
  3. Preview the workflow.
  4. Within the form, use the attached upload option to submit the relevant file.
  5. Submit the workflow.
  6. The signature document will be loaded within the page.
  7. Scroll down to the end of the document. 
  8. Your Signature block for signing is visible.
  9. Sign the document.

Expected Results of Steps
After e-signing the document, the signature should be placed within the signature field.

Actual Results of Steps
Once the receiver signs the contract, the signature appears on the last page and overlaps on the texts.

Root Cause Analysis
In the earlier iText versions, page numbers for signature blocks were automatically assigned. However, starting with iText 7, it became necessary to explicitly define both the page numbers and their corresponding positions. Failure to do so would result in all signatures being placed at the bottom of the page, rather than their designated locations.

This change in behavior was not documented in iText's official documentation, and we only became aware of it while testing with lengthy form documents provided by the client. 

Impacted Areas
E-signature integration and Document generation - Long forms are impacted. The document signing process was temporarily halted within the workflow, consequently leading to the workflow's unavailability for a few weeks.

Tested Areas

  1. Multi-page document, when we have signatures on the first, middle pages and last pages
  2. Acro form PDF with TAP sign, Adobe Sign, and DocuSign
  3. Basic testing around Document Builder and Document Field
  4. Subsequent stages approvals
  5. Signature form fields
  6. 4 types of contract forms - 2 long forms and 2 short forms
  7. Import form from PDF

Known Issues

Issue: TAPSign -> Signature blocks are not coming when document has listbox or dropdown acro fields with no values [used to work earlier in 1.14 before itextsharp upgrade]
Tracking Code: TAPSUP-7363
Case Number: N/A
Reported Version: 1.15.7

Pre-Requisites
Attached document and access to TAP as admin

Steps to Reproduce

  1. Create a new workflow.
  2. Select the import form from pdf and use the attached file.
  3. Verify that the position of form fields after the import is not the same as sb0402 where the 1.14 code is deployed.
  4. Some signature tags have special characters and spaces so fix them.
  5. Go to the workflow tab, add 2 stages with 1st stage with show form access, and connect with a relationship.
  6. On relationship, enable TAPSign support with a document.
  7. Publish and save the workflow.
  8. Preview the workflow.
  9. Enter dummy test data in all fields except the Signer field
  10. Submit stage and observe the document generated for signature and compare it with sb0402 where 1.14 code is deployed and we can see for few form fields that data is not merged in the document. 
  11. The signature blocks are not visible and we can see the barcode which was not visible in the sb0402 old code.

Expected Results of Steps
Signature blocks should be visible.

Actual Results of Steps
Signature blocks are not visible.

Workaround
If a user has a PDF document containing fields like dropdown lists or list boxes, it's essential to ensure that these fields are pre-populated with options to prevent encountering these problems. We will further investigate this issue following the acquisition of the licensed version of iText or any future library upgrades. There is a high likelihood that this issue will be resolved in those circumstances.

Issue: Docusign having duplicate sign blocks when tags placed in multiple pages
Tracking Code: TAPSUP-7364
Case Number: N/A
Reported Version: 1.15.6

Pre-Requisites
Access to TAP docusign tenant.

Steps to Reproduce

  1. Import the workflow.
  2. Preview and submit the workflow.
  3. In the submit interactive document, verify there are no duplicate signature blocks.
  4. Send the document for signing.
  5. Open the document from the mail notification.
  6. Sign at the first block of the DocuSign site.
  7. Click the next indicator.
  8. Sign at the next block.
  9. Observe that the Finish button should appear at the bottom.
  10. Observe the sign blocks asking for signatures to do again.

Expected Results of Steps
It should not prompt for multiple signatures even after one has been provided.

Actual Results of Steps
A signature is being asked even after the signature is done.

Workaround
In the case of DocuSign, it has been noticed that occasionally users are required to sign twice at the same location. This issue seems to have arisen after the most recent iText upgrade.
As a workaround, users can prevent double signing at the same spot by clicking on the signature indicator when signing at the placeholder.
We will attempt to address this issue by testing it with the licensed version of iText 7 or by considering an upgrade to another version of iText.

Issue: Position of signature blocks got little changed now
Tracking Code: TAPSUP-7365
Case Number: N/A
Reported Version: 1.15.7

Pre-Requisites
1. Attached PDF document downloaded
2. Access to TAP as any user

Steps to Reproduce

  1. Navigate to TAP business automation - designer.
  2. Create a new workflow with 2 roles added.
  3. Add a submit button in the form with 2 stages connected with a relationship.
  4. In relationship enable e-sign support using TAPSign and use the attached document as a signature document.
  5. Add 2 more signers.
  6. Save the signature support.
  7. Publish and save the workflow.
  8. Initiate the workflow and submit stage.
  9. Check for the signature block in tapsign iframe.

Expected Results of Steps
The positions of the signature blocks must remain consistent; otherwise, adjustments will be required for existing client documents.

Actual Results of Steps
The signature blocks are overlapping with content in the PDF due to slight changes in the position of the signature blocks caused by recent changes in iTextSharp. Client PDFs will require adjustments to the signature block positions to prevent overlap, especially if there isn't enough margin space at the top.

Workaround
Your signature blocks appear slightly higher in the documents when you sign them. To resolve this issue, consider reducing the size of the signer blocks in the PDF when placing them. This should help prevent any overlap.

Issue: Data on few acro fields not getting merged and populated in the document
Tracking Code: TAPSUP-7366
Case Number: N/A
Reported Version: 1.15.7

Pre-Requisites
1. Attached PDF document downloaded
2. Access to TAP as any user

Steps to Reproduce

  1. Import the workflow with pdf.
  2. Publish, save and preview the workflow.
  3. Enter values in all form fields and submit stage.
  4. Please check for values that may not be mapped correctly in the generated document for signature within the TAPsign iframe. Additionally, please note that the barcode, which used to map correctly with values entered in a field with the correct eSign tag, is now displaying differently.
  5. Create a new workflow.
  6. Use the "Create Form from PDF" feature and upload a PDF with fields mapped to dropdown and listbox options.
  7. Add options to these fields and remove any field populated with something similar to signer.
  8. Include two stages with a relationship between them.
  9. In the relationship settings, enable signature support using TAPsign.
  10. Upload a PDF file and save the workflow settings after publishing.
  11. Preview the workflow.
  12. Enter details into all form fields.
  13. Submit the workflow.
  14. Verify the generated document for signature values.

Expected Results of Steps
If the correct esign tags are used with PDF document acro fields, the data should be mapped in the document generated for signature, just as it did before.
Regarding the barcode behavior, we should examine client use cases with support or the product team. Since the behavior has changed from the old version to the new one, it's important to investigate this matter.

Actual Results of Steps
Data on a few acro fields is not getting merged and populated in the document.

Workaround
None

Issue: Signature block is not showing signature tag in text acro field along with listbox acro field with values is present.
Tracking Code: TAPSUP-7367
Case Number: N/A
Reported Version: 1.15.7

Pre-Requisites
1. Attached PDF document downloaded
2. Access to TAP as any user

Steps to Reproduce

  1. Import the attached workflow with attached PDF.
  2. Publish and save the workflow.
  3. Preview the workflow submit stage and observe signature tag not coming up in iframe.

Expected Results of Steps
Signature block should be visible.

Actual Results of Steps
Signature block is not visible.

Workaround
None

Issue: In generated document for signature for Listbox acro field it is always showing 2nd option selected and similar issue with checkbox also.
Tracking Code: TAPSUP-7368
Case Number: N/A
Reported Version: 1.15.7

Pre-Requisites
1. Attached PDF document downloaded
2. Access to TAP as any user

Steps to Reproduce

  1. Download the attached workflow and import the PDF.
  2. Save, publish and preview the workflow.
  3. Submit workflow without doing any changes in any form field.
  4. Examine the behavior of checkbox and listbox acro fields.

Expected Results of Steps
Values should be mapped dynamicly when correct esignature tags are used.

Actual Results of Steps
The document generation displays static values for listbox and checkbox acro fields.

Workaround
None

Issue: Signature blocks getting overlapped.
Tracking Code: TAPSUP-7369
Case Number: N/A
Reported Version: 1.15.7

Pre-Requisites
1. Attached PDF document downloaded
2. Access to TAP as any user

Steps to Reproduce

  1. Create a new workflow with 2 stages and a submit button.
  2. On relationship 1, configure TAP sign by using the attached PDF and save.
  3. Publish and Save the workflow.
  4. Preview it or use attached workflow.
  5. Submit stage 1.
  6. Observe the Signature blocks getting overlapped.

Expected Results of Steps
Signature blocks must not overlap, and only one block should be visible in it’s designated location.

Actual Results of Steps
Signature blocks are overlapping.

Workaround
None

Issue: In certain content source if signature tag is present then too block is not showing during signature
Tracking Code: TAPSUP-7372
Case Number: N/A
Reported Version: 1.15.7

Pre-Requisites

  1. Access to TAP Prod.
  2. Create a content source.

Steps to Reproduce

  1. Create a workflow and add 2 stages.
  2. Create a document builder PDF and use the created content source.
  3. Go to relationship 1 → Click on e-signature → Use TAPSign and add document builder PDF.
  4. Click Save.
  5. Save publish and preview the workflow.
  6. Submit the workflow.

Expected Results of Steps
The signature block should be visible.

Actual Results of Steps
The signature block is not displayed.

Workaround
None

Issue: Signature block not coming when a specific document is converted to PDF with signature tag using Adobe Acrobat
Tracking Code: TAPSUP-7373
Case Number: N/A
Reported Version: 1.15.7

Pre-Requisites
Access to TAP

Steps to Reproduce

  1. Create a workflow and add 2 stages.
  2. Go to relationship 1 → Click on e-signature → Use TAPSign.
  3. Upload the PDF file or convert docx file to pdf using Adobe and edit the existing signature tag with the correct TAPSIGN tag → Save.
  4. Publish and save the workflow.
  5. Preview → Submit the workflow.

Expected Results of Steps
The signer block should be visible.

Actual Results of Steps
The signer block is not displayed.

Workaround
None

Issue: Receiving error after signing the client provided document
Tracking Code: TAP-29863
Case Number: N/A
Reported Version: 1.15.6.1

Pre-Requisites
Access to TAP Prod

Steps to Reproduce

  1. Upload a PDF document enabling TAP signature.
  2. Publish and Submit the workflow.
  3. Preview the document and sign it.

Expected Results of Steps
Signing the document must be allowed.

Actual Results of Steps
Unable to sign the document. “Error processing request” error is displayed.

Workaround
None

 

  1. Back to top
  • Was this article helpful?

Recommended articles

  1. Article type
    Topic
  2. Tags
    1. 1.15.7
    2. TAP 1.15.7 Release