Release Summary
Version 13.3.0 strengthens security for communication between platform components. This release adds support for the following points:
-
The TCD Connector now authenticates to the PCS 13.3 APIs using dedicated API credentials.
-
Clearer error reporting when communication with PCS fails. See TCD Connector Updates below.
TCD Connector Updates
Configuration and upgrade steps for this release are available in the 13.3.0 Deployment Guide.
The TCD Connector has been updated to work with PCS 13.3, which requires every API request to be authenticated.
Key capabilities
-
Secure API access: Every request to PCS is authenticated with dedicated API credentials. Credentials are never included in request URLs and are never written to the logs.
-
Clear error reporting: When a request is rejected, the logs state the reason, such as failed authentication, an incorrect API path, denied access, or missing credentials, so setup issues can be identified quickly.
-
No data loss on failures: If a request to PCS fails, no records are skipped. Processing resumes automatically on the next run.
-
Simplified integration: An unused legacy PCS call has been removed, leaving a single, secured integration point.
Compatibility
TCD Connector 13.3.0 requires PCS 13.3 or later.
Limitations
|
Summary |
Description |
|---|---|
|
Web surveys |
Web survey not included in this release. Planned for next |
|
PCS reports |
Reports are not included in the application. The CUIC reports will be used instead |
|
Roles and permission |
Fine-grained permissions are not included in the application as in the previous version. Planned for next release |
Release Test Highlights
Tested With
-
PCS Application is tested on Google Chrome only
Not tested with
-
Load Test has not been conducted