RELEASE DATE: 19 April 2021
This topic provides information on enhancements, bug fixes, deprecated features, as well as minor functionality changes for version 3.0.0 of the Tetra Data Platform (TDP). Links to the release notes for Agents and the SDK appear in the other release notes that appear near the bottom of these release notes.
There were several notable enhancements in this version of the software.
The platform now supports bi-directional command queues for all agents and generic connectors. Please note that this feature is disabled by default.
The audit trail feature is now more granular to comply with 21 CFR Part 11 standards. The feature has also been restyled to be easier to use. Audit log data can be downloaded to a CSV file for further analysis.
Editable labels have been included to help you catalog data without creating a new version of the raw, processed, and IDS files, as they do not affect the sanctity of the data. This saves you storage costs because there are fewer files to store.
Metadata and tags have also been enhanced to make them easier to use and apply. A larger character set is available for use as well.
- Metadata, Tag, and Label Concepts
- Managing Labels, Metadata, and Tags
- Using Metadata, Tags, and Labels
Tetra Data Pipelines now provide more detailed overviews and additional information to help you gain more insight into which pipelines have failures and why. This version of the software provides a means to easily reprocess files, an automatic retry feature, reusable containers and the opportunity to use a standby feature, and much more. There is also an improved pipeline overview user interface, which provides more information about pipeline processing.
Additionally, there have been Self-Serve Pipeline improvements that make it easier for you to create your own custom pipelines.
The Solace Connector, which provides SubPub functionality, is now included. The Solace Connector is equipped to be Bi-Directional.
The platform now integrates Fargate functionality to make leverage AWS updates and patching for its server allocation needs.
The IoT functionality is now deployed on its own layer, with its own cloudformation template.
EDSL extracts data from the Waters Empower 3 Acquisition Server to produce continuous, high-quality chromatography analytics that scientists can use to improve quality control, method development, performance and distribution, and other R&D tasks. The EDSL consists of several components:
- One pipeline (RAW to IDS to harmonize the data)
- One Tetra Empower Agent per Waters Empower Acquisition Server
- A Subset of TDP Features that are essential for EDSL
Documentation has been updated to include more topics, a new organization that includes the division of System Administration Documentation into three sections (Installation, Deployment and Upgrade; General Topics, and Security), as well as more conceptual data.
Documentation improvements will continue in the coming months. Documentation has also been branched to more easily differentiate between this version and previous versions of TDP and other components.
Listed below is a sampling of new documentation or significantly revamped topics and features.
- Documentation Landing Page
- Tour of the TDP UI
- Single Tenant Deployment Overview ](https://developers.tetrascience.com/v3.0/docs/managing-your-personal-user-account)
- File Info API
- Integrations Supported Sources and Targets
- Required AWS Services
The following bug fixes were made to the platform.
DI-3664 - Fix boundary plicy and IAM prefix bugs
Prefixes can now be used in IAM policies.
DI-3686 - Workflow notification URL link is incorrect
Corrected the “Test Notifications” URL link that appears in the email that has details about file processing failures.
DI-3687 - SSO redirect to “login” after logout or session timeout
When a user’s session expired or the user logged out, the browser redirected to the main login page, not the login page for the SSO page as specified in the environment variable. This was fixed; redirects are now to the specified SSO page.
DI-3698 - Datahub installation issue in Red Hat 7.9
The installer failed due to missing libraries. This issue was resolved and other changes were made to allow installation of the Data Hub to occur.
DI-3709 - Missing Information about “Last Modified By” for Shared Settings in IIDP DEV
The Shared Settings Page did not correctly indicate the user who modified the settings. This has been addressed. Information is also captured in the audit trail.
DI-3739 - Incorrect usage of shared settings in IIDP UI
The Pipeline parameter’s Usage column did not display whether the pipeline used a particular Secret, although this was reflected in the Shared Setting’s Usages column. This was fixed so that the secret usage is seen in both places.
DI-3805 - No Logs Found for Different Workflows
Some failed workflows showed the message “No Logs Found” when the user clicked on the View Details link for a pipeline workflow. Workflows now show logs for successful and failed completions. Logs older than 90 days are no longer automatically deleted.
The following features are currently deprecated.
- Usage of the API Key for Authentication
The API Key, which is used for authentication, is deprecated. While the API Key still works, we strongly recommend that you use the JSON Web Token (JWT) instead.
The following minor functionality changes are in this version of the software.
- When administrative users make password changes, they must now be at least 8 characters long, with one upper-case letter and one lower-case letter.
- When selecting files for reprocessing, clicking the “Select All” files all files that match the trigger are selected, not just the ones that currently appear on the screen.
- Labels are now limited to 128 characters.
- You can now add more characters in your metadata. Please see this topic for the supported character set.
- The term “Master Script” has been changed to “Protocol” throughout pipeline pages to more accurately match the terminology.
- Only one value per metadata key is permitted.
For platform upgrades, if the platform was previously using EKS, be sure to add the
EKS_CLUSTER_LOG_GROUP_NAME parameter to the workflow service. The parameter should point to the containers log group of the EKS cluster.
Other release notes for different TDP components appear in the following places: