Release Notes

Introduction

The release notes provide brief and high-level descriptions of the new features of HaloCAD. Before installing HaloCAD, it is recommended to read the release notes to understand any current limitations or bugs that may apply to this version of the software.

Product Description

The HaloCAD for PLM solution integrates seamlessly with the PLM application, including the features of HaloCAD PROTECT and HaloCAD MONITOR while utilizing Microsoft Purview Information Protection (MPIP), formerly Microsoft Information Protection (MIP), to provide Enterprise Digital Rights Management (EDRM) capabilities.

It provides access to MPIP-protected files, including label handling and privilege enforcement. Any file access actions, such as check-out or export, that may result in a download are intercepted by the HaloCAD for PLM solution, automatically protected based on predefined rules, and then delivered to the end user. Similarly, file access actions such as check-in or upload are intercepted and examined. If a protected file is detected, it is decrypted, and the unprotected file is returned to the PLM vault. For CAD users, the handling of CAD files remains seamless, as these processes occur entirely in the background. By applying MPIP labels, the solution ensures end-to-end security for CAD files, while all upload and download activities are continuously monitored and logged to provide complete traceability.

System Requirements

The following system requirements table specifies the minimum and recommended technical specifications, such as software and network resources, necessary to run the product.

Requirements

Supported Autodesk Vault versions for HaloCAD for Autodesk Vault

You are currently viewing the release notes for the current build. For previous versions, please refer to their respective release notes.

Autodesk Vault and HaloCAD component version

Prerequisites

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

1. An application of type Web is registered with Microsoft Entra ID.

2. An active Office 365 subscription is available.

3. Access to the recommended URLs is enabled.

4. TLS 1.2 or later is enabled on all client workstations to ensure secure communication.

For more information, refer to the Technical Reference Manual.

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 2.8

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

There are no new features to highlight in this release.

Improvements

This section lists the improvements in the current release.

1. Added support for Autodesk Vault 2026. HCADVLT-522

2. Added support for automatic HaloENGINE service initialization during deployment. After a successful HaloCAD for Autodesk Vault installation, the WAR file is deployed and initialized automatically.

3. Implemented file encryption for downloads initiated via the View option in the Thin Client context menu. HCADVLT-478, HCADVLT-477

4. Improved Vault Client performance during ASM file download operations. HCADVLT-531

5. Added support for Optimized Download Protection. This option is available in the Configuration Tool and is disabled by default. When enabled, during the download of multiple files (for example, a parent ASM with dependent files), the smallest single file is protected first and delivered to the user location. The remaining files are then automatically protected at the user location using the HaloCAD for PLM Client. HCADVLT-561

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 to ensure immediate file download after logging in to the Vault Thin Client. HCADVLT-510

2. Fixed an issue where files downloaded using the Print → Save As PDF option were not protected. The file is now downloaded with protection applied. HCADVLT-511

3. Fixed an issue where the system did not properly switch to the Secondary HaloENGINE when the Primary HaloENGINE was unreachable or powered off, even though failover was configured. HCADVLT-519

4. Fixed an issue where files downloaded through the Autodesk Vault 2026 Thin Client were not protected during the download process. HCADVLT-527

5. Fixed an issue where Secondary HaloENGINE configurations were deleted after making changes to the Primary HaloENGINE configuration. HCADVLT-528

6. Fixed an issue where a file download failed with an error in Tolerant Mode when HaloENGINE was configured with invalid MPIP application details. HCADVLT-529

7. Resolved an issue where the system generated incorrect log entries for Block actions, even though the action rule condition was successfully matched. HCADVLT-530

8. Fixed an issue where files downloaded using the Three dots → Download → File option were not protected during the initial download. HCADVLT-540

9. Fixed an issue where the Vault Client failed to establish a connection via the proxy when the Secondary HaloENGINE instance was down or powered off, even though the Primary HaloENGINE instance was up and connected. After the fix, the Vault Client now successfully connects via the proxy when the Secondary HaloENGINE is unavailable, and files are protected using the Primary HaloENGINE. HCADVLT-555

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

Unsupported Versions

Support for Vault 2023 (Professional/Basic) server and client 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