Update Dataset to Ensure Correct Field Designations: 

When custom data fields are added and the Elasticube is updated from TAP, date field data will now be recognized and added as date field types. Text fields that undergo numerical validation will be categorized as number types. All other field types will default to text data supporting Unicode characters. Additionally, currency-validated text fields will be stored as number types within the eCube.

Impacted Areas: 
Datasets in TAP

Tested Areas: 

Provisional Flag Enabled Testing (Old Behavior)

1. Existing dataset and VIEW with multiple dynamic columns.

Provisional Flag Disabled Testing (New Behavior)

1. Existing dataset and VIEW with multiple dynamic columns.
2. New dataset (VIEW) with and without dynamic columns.

For more information on Analytics 2.0, refer to the Client Success Center.

Tracking Code: TAP-29374

Advanced Export Workflow Details:

The Advanced Export feature enables users to export a zipped folder containing essential files like the 'tapw' file, attachments, CSS files, data sources, and eSign documents. This feature requires new user permission and is accessible for all templates and revisions within a tenant. Below is a summary of these enhancements and the UI changes:

1. Selection of 'Advanced Export':
   1. Upon selecting 'Advanced Export', the following actions take place:
      1. The extracted .tapw file is named "(Workflow Template Name).tapw" instead of "template.tapw".
      2. A zipped folder (.tapz) is downloaded, titled '(Workflow Template Name) - (Date Downloaded)'. Please use an extractor tool to access those files.
      3. The folder includes:
         • .tapw file of the workflow template.
         • Attachments folder containing labeled attachments linked to any stage of the workflow.
         • CSS folder containing labeled CSS templates linked to stages or thank you pages.
         • Data Sources folder containing named TAP Stored data sources.
         • eSign Documents folder containing named eSignature uploaded templates.

For more information on Advanced Export, go to the Client Success Center.

2. Data Sources Folder Criteria:
   1. Data sources will use names from the TAP tenant data sources section.
   2. Conditional data sources will retrieve parent, child, and mapping files.
   3. Data sources from multi-select fields will be exported and visible in the JSON file.
   4. Each data source will be pulled only once, even if used across multiple fields.
   5. A JSON file will be downloaded alongside the .tapw file, containing all information, even if all checkboxes are deselected.
3. New Permission: 'Advanced Export Privilege': Introduced to the Admin Application Permissions, enabling access to the 'Advanced Export' option in workflows and revisions. For more information on Advanced Export Privilege, got to the Client Success Center.
4. Additional Option in 'Advanced Export': A new option is available in the revisions grid rows, allowing users to select any workflow template, choose 'revisions', and then 'Advanced Export'.
5. Organization of Files:
   1. The zip file and extracted folder will contain files and the .tapw file.
   2. eSignature files will be exported to a single folder, organized within subfolders corresponding to the relationship they were uploaded on.
6. CSS and Attachments Handling:
   1. Duplicate CSS files used across multiple stages and Thank You Pages are removed.
   2. Attachments are organized into subfolders based on the stage they are uploaded to and labeled similarly to their counterparts in the workflow.
   3. CSS files are named similarly to their counterparts in the workflow.

New API Endpoint for Roles and Departments Created: 

1. Introduced a new API endpoint for retrieving all roles and their corresponding role IDs.
2. Introduced a new API endpoint for retrieving all departments along with their department IDs.

Access Permissions: Users must have administration page access to generate a valid token for authentication when making this call.

Impacted Areas: 

1. Roles API List
2. Verification of Departments API List
3. User Permissions for User Administration Scenarios

Tested Areas: 

1. Verification of Roles API List
2. Verification of Departments API List
3. User Permissions for User Administration Scenarios

Tracking Code: TAP-32984

New API Endpoint for User Profile Creation and Update: 

To facilitate integration with TeamConnect, the TAP Team has introduced an endpoint that enables the creation or updating of user profiles within TAP. 

• Creation and updating of user profiles in TAP using designated endpoint(s).
• When creating a user, mandatory fields include Login, First Name, Last Name, Role, Department, and Password, with additional fields being optional and dynamically added to the user profile upon creation.
• When updating a user, only the specified fields are modified, ensuring the integrity of existing data. Additionally, users can also be locked out using the updated user API.
• The endpoint supports bulk operations, allowing for the simultaneous creation or updating of multiple user profiles.
• A comprehensive error handling mechanism provides detailed feedback in case of failed calls, including specific error messages and reasons for failure, when applicable.
• ‘Create User’ or ‘Update User’ endpoints utilize role IDs and department IDs, which can be obtained from the new Roles and Department endpoints.
• ‘Create User’ or ‘Update User’ endpoints adhere to standard API naming conventions, removing verbs from the endpoint names.

Access Permissions: Authentication requires a user account with administration page access to generate valid tokens for API calls.

Impacted Areas: 

1. Creation and modification of user profiles
2. Permission and access rights for creating new user profiles
3. Generic user fields

Tested Areas: 

1. Creation and modification of user profiles using the "Create User" and "Update User" APIs.
2. User management functionalities, including user creation and modification, within the administrator page.
3. User authorization verification for creating new user profiles.
4. Validation of roles and departments in Create/Update User APIs.
5. Validation of generic user fields.

Tracking Code: TAP-4472; TAP-32684

New API Endpoint for Deleting User: 

A new API endpoint is introduced in TAP to enable users to delete user accounts. Within the user table, there is a "isDeleted" flag that can be updated accordingly. Presently, user deletion in TAP is performed as a soft delete.

Impacted Area(s): 
Delete User API

Tested Areas: 

1. Three APIs: delete user, update user, and create user.
2. Presence of deleted or updated users on the admin page.
3. Proper user authorization for update and delete operations.
4. Scenarios involving permissions for super admin and non-super admin users.

Tracking Code: TAP-40475

For more information on API endpoints, go to the Client Success Center. 

New API Endpoint for Retrieving Comments from Records: 

A new REST API Endpoint for Retrieving Comments from the Record Communications Tab is introduced. This new REST API endpoint enables users to extract data from the communications tab of a record. Users can specify which records to pull by:

• Individual records using workflow name or ID
• Group of records using workflow names or IDs
• Group of records using Dashboard View ID

The JSON response will include the following details for each record and comment in the communications section of the audit log:

• Name of the user who left the comment
• Date of the comment
• Comment content

Introduced comments total count for each workflow ID/name. If no comments are present, an empty CommentsFieldsList is displayed (similar to the discussion endpoint).

Added an Error property to display an error message. If no comments are present, an empty CommentsFieldsList is displayed (similar to the discussion endpoint).

Access Permissions: Only users with 'View History' access can retrieve this information from a record.

Impacted Area(s): 
APIs for Retrieval of Comments from Records

Tested Areas: 
Retrieval of Comments from Records via 3 APIs

Tracking Code: TAP-22317; TAP-32706

New API Endpoint for Retrieving Discussion Section from Records: 

Introduced a new REST API endpoint that enables users to extract data from Discussion sections within a record's collaboration stages. This endpoint provides flexibility in specifying the records to retrieve data from, including:

• Retrieving data for a single record by workflow name or ID.
• Extracting data for a group of records using workflow names or IDs.
• Retrieving data for a group of records based on Dashboard View ID.

The JSON response from this endpoint includes the following details for each record and comment within a saved or completed collab stage discussion section:

• Name of the stage
• Name of the user who left the comment
• Date of the comment
• The comment itself

Access Permissions: Only users with 'View History' access can retrieve this information from a record.

Impacted Area(s): 
API for Retrieving Discussion from Records

Tested Areas: 
Retrieval of Discussion from Records via 3 APIs

Tracking Code: TAP-22476

Impact of Kendo UI Library Version Upgrade on UI and User Experience:

The transition from Kendo UI version 2017.3.1206 to 2023.2.718 in TAP has brought about changes to the user interface (UI) and enhancements to the user experience. This section provides an overview of these modifications, highlighting the subtle adjustments made to various elements for a more contemporary look and feel.

Migration of Filter Data from SQL to Mongo DB

On the Business Automation page, within the List of Configurations section, the dropdown menu should include all the options corresponding to the features for which pinned filters have been created, such as Workflow Dashboard, Document Library, Archive Library, and Signature Repository.

If no pinned filter is created for a particular feature, then the corresponding label will not appear in the dropdown menu. For instance, if there are no pinned filters for the "Archive Library," then "Archive Library" will not be listed in the dropdown menu.