Release Notes

Introduction

The release notes provide a high-level overview of the new features, fixed issues, known issues, and prerequisites for HaloCAD for PLM. Before installing HaloCAD for PLM, review these release notes to understand the changes, known limitations, and requirements that apply to this release.

Product Description

HaloCAD for PLM integrates with supported Product Lifecycle Management (PLM) applications and Microsoft Purview Information Protection (MPIP) to protect CAD files throughout their lifecycle. It automatically applies MPIP sensitivity labels based on predefined rules during download and removes protection during upload, returning the unprotected file to the PLM vault. This provides seamless file handling, end-to-end security, and complete traceability.

Prerequisites

Before installing HaloCAD for PLM, ensure that the following prerequisites are met:

• An active Microsoft 365 subscription is available.

• A Web application is registered with Microsoft Entra ID.

• Access to the required Microsoft service URLs is enabled.

• TLS 1.2 or later is enabled on all client workstations.

For detailed prerequisite and configuration information, refer to the Technical Reference Manual.

System Requirements

The following table lists the system requirements for installing and running HaloCAD for Teamcenter.

Requirements

Supported Teamcenter applications for HaloCAD 

HaloCAD for Teamcenter 3.0 is the first version to use HaloENGINE GenNXT. Versions earlier than 3.0 use the legacy HaloENGINE platform. For release information about these earlier versions, refer to the corresponding HaloCAD for Teamcenter Release Notes.

Teamcenter applications and HaloCAD component version

Code Quality and Security

Secude focuses on software quality and security. This is accomplished by adhering to and exceeding best practices in development, testing, and quality control. Secude has chosen SonarQube as the first building block for building and implementing a robust continuous code quality assurance (QA). SonarQube is a platform for static code analysis for continuous inspection of code quality. It performs automatic reviews of code to detect bugs, code smells, unit test coverage, and security issues in 29 programming languages.

SonarQube is utilized throughout the development process at Secude, and only the highest marks are accepted for a product to be released. It helps to regulate code quality from the beginning of development, find and repair issues promptly, and improve overall software stability.

Each build report can be found under its relevant version heading in this release notes.

Reliability Rating 

1. A = 0 Bugs

2. B = at least 1 Minor Bug

3. C = at least 1 Major Bug

4. D = at least 1 Critical Bug

5. E = at least 1 Blocker Bug

Security Rating

1. A = 0 Vulnerabilities

2. B = at least 1 Minor Vulnerability

3. C = at least 1 Major Vulnerability

4. D = at least 1 Critical Vulnerability

5. E = at least 1 Blocker Vulnerability

Security Review Rating 

The Security Review Rating is a letter grade based on the percentage of Reviewed (Fixed or Safe) Security Hotspots.

1. A = >= 80%

2. B = >= 70% and <80%

3. C = >= 50% and <70%

4. D = >= 30% and <50%

5. E = < 30%

Maintainability Rating 

A=0-0.05, B=0.06-0.1, C=0.11-0.20, D=0.21-0.5, E=0.51-1

The Maintainability Rating scale can be alternatively stated by saying that if the outstanding remediation cost is:

1. <=5% of the time that has already gone into the application, the rating is A

2. Between 6 to 10%, the rating is a B

3. Between 11 to 20%, the rating is a C

4. Between 21 to 50%, the rating is a D

5. Anything over 50% is an E

Build 3.0

This chapter provides an overview of the updates and quality insights included in this release. It covers the fixed issues, improvements, limitations, new features, and known issues, along with a summary of SonarQube’s key parameters to highlight code quality metrics and analysis results.

Improvements

This section lists improvements added to the current release.

1. Starting from this release, HaloCAD for Teamcenter supports integration with HaloENGINE GenNXT and its features, replacing the legacy HaloENGINE integration. HCADTCR-646

2. Removed the System ID field and renamed Customer ID to Profile Name in HaloCAD for Teamcenter Configuration tool. HCADTCR-614

3. HaloENGINE GenNXT communicates over HTTPS and supports self-signed and CA-signed certificates. Clients connecting to HaloENGINE GenNXT must install the appropriate certificate in Trusted Root Certification Authorities:

   1. For a self-signed certificate, install the public key.

   2. For a CA-signed certificate, install the Root CA.

4. Removed the Certificate Name and Password fields from the configuration tool. HCADTCR-647

5. Replaced ServerHost with Teamcenter 4-Tier URL in the configuration tool.

6. Added support for SSO-based SOA authentication in Teamcenter haloproxy. The Configuration Tool now provides SSO URL, SSO AppID, and SSO Proxy Path fields for configuring SSO authentication.

7. Previously, only the ip_classification metadata was supported. Starting with this release, gov_clearance and custom_metadata are also supported.

Limitations

This section lists the limitations of the current release.

1. A text file downloaded from RAC is protected as expected. But if the Teamcenter server is set up with Windows encoding, such as cp-1252, then a text file downloaded from the client will be inserted with a Windows line break, causing the file to be corrupted and unreadable. Therefore, it is advised against protecting text files when such a setting is present in your Teamcenter server environment. Additionally, if a protected text file is downloaded and uploaded again into Teamcenter (via RAC), the file size is updated as “0". HCADTCR-88, HCADTCR-132

2. When HaloCAD is deployed in an environment, we recommend that the administrator restrict access to non-Proxy URLs by using a firewall or other network application. This is because, as HaloCAD is a proxy, non-proxied actual URLs will also be accessible, leading to data leakage. Therefore, we recommend restricting access.

Fixed Issues

This section provides a list of the fixed issues in the current release.

1. Fixed the issue where files were downloaded without protection in Strict mode when invalid Microsoft Purview Information Protection (MPIP) details were configured. Files are now downloaded as 0 KB in Strict mode. HCADTCR-608

2. Fixed an issue where an error message was displayed, and the HaloENGINE GenNXT Tomcat service stopped automatically after stopping and restarting the FCC service. HCADTCR-616

3. Fixed an issue where the Monitor log was not updated during the decryption of a protected file during upload. HCADTCR-649

Known Issues

This section describes the known issues with the current release.

1. If an Office file is downloaded, the file gets protected, but the extension changes. For example, sample.docx > sample.doc. HCADTCR-127

2. If a Non-CAD/Non-office file is downloaded, the file gets protected as per the rule configured in HaloENGINE GenNXT, but the extension is saved with the native format (i.e., .txt, .jpg, .bmp) instead of .ptxt or .pfile. HCADTCR-35

3. An error message appears as “Error 1069: The Service did not start due to a logon failure” when you start the HaloENGINE GenNXT Tomcat Service. This is because the user who is running the service or a specific group that the user belongs to (e.g., "Administrators") is added to the Deny log on as a service policy (Local Security Policy > Security Settings > Local Policies > User Rights Assignment). To prevent such an error, make sure the user(s) or the group that the user belongs to who runs the Service does not exist in the group policy.  

4. When uninstalling HaloCAD for Teamcenter Proxy using the executable, the Secude installation folder and its associated files are deleted only if the Tomcat service is stopped manually. However, when uninstalling through Windows Control Panel, the associated files and subfolders are deleted, but the main Secude folder remains, even if the Tomcat service is stopped manually.

   Workaround: For this release, stop the Tomcat service before uninstalling HaloCAD for Teamcenter Proxy using the executable. HCADTCR-651

Quality Gate Report

Please see the table below for a list of SonarQube's key parameters for this version. Refer to the "Code Quality and Security" section for more information on rating definitions.

Quality Gate report

Last updated: October 29, 2026