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 Autodesk Vault.

Requirements

Supported Autodesk Vault versions for HaloCAD

HaloCAD for Autodesk Vault 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 Autodesk Vault Release Notes.

Autodesk Vault 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.

New Features

This section lists the new features in the current release.

Added support for Autodesk Vault 2027. HCADVLT-610

Improvements

This section lists the improvements in the current release.

1. Starting with this release, HaloCAD for Autodesk Vault supports integration with HaloENGINE GenNXT and its features, replacing the legacy HaloENGINE integration.

2. Removed the System ID field and renamed Customer ID to Profile Name in the HaloCAD for Autodesk Vault Configuration tool.

3. Removed the Client Certificate and Password configuration fields from the Configuration Tool. HCADVLT-626

4. Renamed HaloENGINE to HaloENGINE GenNXT in the following areas. HCADTCR-640

   1. Configuration Tool

   2. Installer

   3. Shell command

5. 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.

6. Removed the Certificate Name and Password fields from the Configuration Tool.

Limitations

This section lists the limitations of the current release.

When HaloCAD is deployed in an environment, we recommend that the administrator restrict access to non-Proxy URLs 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 an issue where configured labels were not applied to files downloaded through the Vault–Inventor integration when Multi-label optimization was enabled. HCADVLT-545

2. Files are downloaded from Vault even when the HaloENGINE GenNXT Tomcat service is stopped and Fail Safe Mode is set to Strict. HCADVLT-563

3. Fixed an issue where only one file was blocked when downloading an assembly with Optimized Download Protection enabled. HCADVLT-594

4. Fixed an issue where files could not be opened in AutoCAD when using the double-click or right-click > Open option from the Vault client. HCADVLT-601, HCADVLT-608

5. Fixed an issue where AutoCAD files were opened without protection when downloaded using Check Out with the Update Properties option. HCADVLT-602, HCADVLT-607

6. Fixed an issue where files were downloaded even when an error occurred with Fail Safe Mode set to Strict and an incorrect HaloENGINE GenNXT host name was configured. HCADVLT-613

7. Fixed an issue where the Decision field was not updated to LABELED in the Monitor log when a label-only file was downloaded with the action rule set to Label without Protection. HCADVLT-627

8. Fixed an issue where downloaded files remained unprotected in Vault Thin Client 2027. HCADVLT-628

9. Fixed an issue where the Monitor log incorrectly displayed Error = Yes and Act = Blocked when uploading an unprotected file to Vault. HCADVLT-634

10. Fixed an issue where the Profile Name and Client Type fields were empty in the Monitor log for file download operations. HCADVLT-635

11. Fixed an issue where the connection between Vault and HaloENGINE GenNXT was allowed without successful certificate authentication. HCADVLT-637

12. Fixed an issue where the certificate_unknown error message was not displayed when invalid HaloENGINE GenNXT client certificates were configured for both the primary and secondary HaloENGINE GenNXT servers. HCADVLT-640

13. Fixed an issue where a file downloaded from the Vault Thin Client was not protected according to the configured rule, even though it was saved to the specified location. The Monitor log also incorrectly displayed Error = YES. HCADVLT-647

Known Issues

This section describes the known issues with the current release.

1. Thin client Autodesk Vault Browser-based access is not supported. HCADVLT-13

2. When using the Share View option to open a file, an error message appears: “The remote server returned an error: (500) Internal server error.” Consequently, the link is not created. HCADVLT-25

3. Intermittently, the protected file does not open with a double-click or a right-click. There will be an error message “File can't be opened in the application”, or “The remote server returned an error (500) internal server Error”.

4. HaloENGINE ID will be displayed as the "Owner" of the document, despite the email ID (Autodesk Vault login user) configured in the admin portal.

5. 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, ensure that the user(s) or the group to which the user belongs, who runs the Service, are not included in the group policy.

6. Monitor log entries are not updated correctly when multiple files are selected and downloaded from the Vault client. HCADVLT-633

7. The Host value is not displayed, and an incorrect IP address is displayed in the Monitor log when downloading a file from the Vault Thin Client. HCADVLT-645

8. The Author field in the Monitor log is not updated correctly when Document Owner is configured as User in HaloENGINE GenNXT. HCADVLT-646

Unsupported Versions

Support for Autodesk Vault 2024 has been removed in this release.

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