Bug Fixes

Issue: The notification in the highlighted stage is going to the user from an incorrect sender
Tracking Code: TAPSUP-7239
Case Number: 2023-0807-7938980
Reported Version: 1.14.3.0

Workaround

None

Pre-Requisites

Access to the TAP environment 

Steps to Reproduce

1. Select a workflow
2. Load the workflow and Preview
3. Submit the workflow
4. Go to email notifications and verify from the address

Expected Results of Steps

Correct 'from' address will be used for workflows submitted through API (check if this is UI).

Actual Results of Steps

The notification sent by the requester in a stage is being received by the user from an incorrect sender.

Root Cause Analysis

It appears that there is a settings data cache issue stemming from an application ID mismatch. The data retrieved from the settings is originating from a different tenant. To address this, we have included logs for further investigation in case the issue reoccurs. Additionally, based on our investigation, we have implemented a potential fix to resolve this matter.

Impacted Areas

1. Stage notifications 
2. Relationship notifications

Tested Areas

1. Stage notifications 
2. Relationship notifications via workflow submitted from UI and API

---

Issue: Urgent: Issue with Document Tagging and Merging
Tracking Code: TAPSUP-7264
Case Number: 2023-0811-7944860
Reported Version: 1.15.3.0

Workaround

None

Pre-Requisites

Access to the TAP environment

Steps to Reproduce

1. Import the workflow
2. Publish and save the workflow
3. Preview Workflow 
4. Fill in the values in form elements
5. Submit the Workflow

Expected Results of Steps

PDFs that have been tagged with multiple TAP field tags will merge as expected.

Actual Results of Steps

The PDF document only populates half of the sections, leaving the other half unfilled, despite the form elements being completed and prepopulated as configured.

Root Cause Analysis

itext7 has altered its approach to managing duplicate fields within PDF Acro Forms. 

Impacted Areas

1. Stage attachments with taggings
2. Pre-merge and without E-sign support
3. Document builder and document field with tagging
4. Word file

Tested Areas

1. Stage attachments with taggings
2. Pre-merge and with or without E-sign support
3. Document builder and document field with tagging
4. Word file
5. File uploads

---

Issue: Client is unable to see the document tagging in the documents after the latest release on 07/28
Tracking Code: TAPSUP-7265
Case Number: 2023-0811-7944868
Reported Version: 1.14.3.0

Workaround

None

Pre-Requisites

Access to the TAP environment

Steps to Reproduce

1. Import the workflow
2. Publish and save the workflow
3. Preview Workflow 
4. Submit the details
5. Download the document from the audit trail

Expected Results of Steps

The user should be able to see the document tagging in the documents.

Actual Results of Steps

The user is unable to see the document tagging in the documents after the latest release on 07/28.

Root Cause Analysis

In certain situations, the RenameFormFieldsStream() function is invoked twice. This also leads to the creation of two instances of the pdfDocument internally. During the first instance, the pdfDocument object is generated to read AcroFields and insert data into these fields. However, the changes are not yet written into the document, and the pdfDocument object remains unflushed. Following this, the RenameFormFieldsStream method is called once more right away, leading to the creation of another pdfDocument instance. As a result, the original instance with changes is discarded. As Acrofields have already been read during the initial instance, the iText library cannot locate any Acrofields in the document subsequently, preventing any modifications. Placing the pdfDocument object within a using block guarantees its immediate disposal and prompt writing of changes, preventing potential loss later on. Typically, the application invokes RenameFormFieldsStream() only once. Hence, this scenario doesn't arise frequently, making it less noticeable.

Impacted Areas

1. Stage attachments with taggings
2. Pre-merge and without E-sign support
3. Document builder and document field with tagging
4. Word file

Tested Areas

1. Stage attachments with taggings in pdf
2. Pre-merge and with or without E-sign support
3. Document builder and document field with tagging
4. Word file
5. File uploads