TAP 1.17.8 Release Notes
1.17.8 Production Date: 07-19-2024
New Feature(s)
Encrypt Field Data in Database:
We are introducing a new feature that allows field data to be encrypted in the database. This is implemented through a new checkbox option labeled ‘Encrypt Field values,’ available for the following TAP fields:
- Text
- Area
Key Features:
Encryption Mechanism:
When the 'Encrypt Field Values’ checkbox is selected, the value entered into the field will be encrypted in the database using System.Security.Cryptography. This is similar to the encryption method used for SSN-validated fields.
- We have introduced maximum value validation for text and area fields.
Integration with Existing Features:
Any configuration rules or other functionalities that utilize this field will work as expected, using the unencrypted value entered into the field. This includes:
- Formulas
- Pre-population
- Form Mapping
- Show/Hide conditions
- Document Tagging
- Notification Tagging
- Doc Builder
- External API
- Audit trail
Data Privacy:
- Field data will not be displayed on the dashboard.
- Field data will not be accessible through the API.
- If both the ‘Encrypt field values’ and ‘Add to repository’ checkboxes are selected for text and area fields, the value will be displayed as ‘Value Hidden’ on the dashboard.
- When the 'Edit Request' or ‘Audit Trial’ is clicked, all the details will be visible except for the SSN field. To view the SSN, select 'click to reveal'.
- Encrypted fields will not be accessible through the ‘Edit Request’ action on the dashboard.
External API Functionality:
Field data can be sent to third-party systems using TAP external API functionality. When this is done, the unencrypted value will be sent.
Template-Based Configuration:
This setting is not retroactive. Fields will encrypt or not encrypt based on the setting configured in the workflow template from which the record was generated.
Please note: If the ‘Encrypt Field values’ checkbox is selected, the SSN field will be disabled. Likewise, if the SSN field is selected, the ‘Encrypt Field values’ checkbox will be disabled.
This new feature ensures enhanced data security while maintaining ideal integration with existing TAP functionalities.
Tracking Code: TAP-48751
Bug Fixes
Issue: SSN is showing Scrambled Values- StringReplace on SSN field generates unreadable alphanumeric value.
Tracking Code: TAPSUP-8643
Case Number: 2024-0603-8262385
Reported Version: TAP 1.17.1
Workaround
None
Pre-Requisites
Access to TAP Default Docusign
Steps to Reproduce
- Import the workflow.
- Fill out the form with SSN value and submit the first stage.
- Edit the request from the dashboard and submit the second stage.
- Edit the request again from the dashboard and submit the third stage.
- Navigate to the dashboard and click on "View History" to review the workflow's progression.
- Observe the Quick SSN value.
Expected Results of Steps
Quick SSN should display the numeric values entered in the SSN field.
Actual Results of Steps
QuickSSN is displaying a scrambled alphanumeric number instead of the entered numeric values in SSN.
Root Cause Analysis
During the submission of the third stage, the SSN value is not being decrypted, resulting in the encrypted string being saved as-is.
Impacted Areas
Formula SSN Field
Tested Areas
- 2nd and 3rd stage by giving different SSN values
- Edit request for 2nd and 3rd stages
- View history for all the SSN values
- All type of form access in multiple stages
- All scenarios by using Formula SSN field
Issue: Issues with Table Form field Headers marked with read only when User submits data in Foreign Language.
Tracking Code: TAPSUP-9146
Case Number: 2024-0620-8281137
Reported Version: TAP 1.17.4.0
Workaround
None
Pre-Requisites
Access to TAP
Steps to Reproduce
-
Test 1:
- Navigate to the desired workflow.
- Preview the workflow.
- Submit the request without making any changes to the table field.
- Access the Dashboard, select the request, and click on "Edit Request."
- You will find the form with only the submit button visible, without the table.
-
Test 2:
- Preview the workflow.
- Translate the page using the browser's translation feature and submit the form.
- In the second stage, you will see the table displayed (instead of being blank as in Test 1).
-
Test 3:
- Preview the workflow.
- Enter table rows in English.
- Translate the page using the browser's translation feature.
- Go to the Dashboard, select the request, and click on "Edit Request."
- You will see only the table displayed in the translated foreign language.
Expected Results of Steps
As the form access setting is configured to display previous results, the table should not appear in the next stage if no data was entered in the first stage.
Actual Results of Steps
The table will not appear if a user submits the first stage in English without filling in any data.
Root Cause Analysis
This functionality works as intended based on the current implementation.
Impacted Areas
Table Form Field
Tested Areas
-
Table Form Field Verification:
- Table form field with read-only headers and row headers.
- Verified that when a user submits the workflow, the headers and rows' data remain unchanged.
-
Language Translation:
- Applied Google Translator to the workflow and changed the language.
- Submitted the workflow after translation.
- Verified that the read-only columns' data remains consistent with the original language.