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

HaloCAD acts as the guardian of your CAD files by automatically protecting them with Microsoft Purview Information Protection (MPIP) labels whenever they leave your secure IT perimeter. As a plug-in for CAD applications, HaloCAD offers access to MPIP-protected files, including label handling and privilege enforcement. CAD users will not notice any differences in the handling of CAD files because protection takes place in the background. By seamlessly attaching MPIP labels to the CAD files while they are being created, it provides end-to-end security for those files.

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 CAD applications for HaloCAD Add-ons

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

CAD applications and HaloCAD Add-on version

Prerequisites

Before installing the add-on, ensure that the following prerequisites are met:

1. An application 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.4

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 default values for silent command-line parameters.

2. Added support to display online documentation directly from the installer UI for both the standard and Reader add-on installers. When the Online Help button is clicked, the online documentation now opens in the user's default browser. HCADSE-684

3. Improved token-sharing encryption and FIPS compatibility by ensuring proper OpenSSL FIPS context initialization and preventing failures in child processes during configuration decryption. HCADSE-686

4. In previous releases, asterisks were used in MIP SDK logs to mask Personally Identifiable Information (PII), such as email names and IP addresses. This feature is now extended to HaloCAD logs to also mask information such as label name, label ID, engine ID, policy ID, and watermark text. HCADSE-689

5. Added support for Version 2025. HCADSE-687

Fixed Bugs

This section lists the fixed issues in the current release.

1. Fixed an issue where a newly created Assembly file could not be saved after importing a Part file protected with Edit/Co-Author rights. HCADSE-672

2. Fixed an issue where a file translation error occurred when exporting an IGES file from a protected file. The IGES file now saves correctly without errors. HCADSE-682

3. Fixed an issue where an exported STP file from a protected PAR displayed errors during open and did not load the design. The file now opens correctly with the design, and no errors are displayed. HCADSE-683

4. Fixed an issue where the Solid Edge application crashed when attempting to print a protected file with View rights. HCADSE-691

Known Issues

This section lists the known issues in the current release.

1. While uploading a protected ASM file using the Import on Demand Dialog, there will be an error message “Save and Display was cancelled because following document have no DIR”. HCADSE-236

2. It is possible to save and export a protected PDF file with no export rights to an unprotected file using the local printer > Paper Print option. HCADSE-199

3. It is not possible to add the protected assembly file to the newly created assembly file, doing so the Solid Edge will display a pop-up as “The part cannot be placed. Make sure it is not a Feature Library part”. HCADSE-260

4. There will be a time delay in opening an unprotected file in the Solid Edge application. HCADSE-269

5. It is possible to view the design dimensions and modify the diagram by changing the dimensions of the protected file with view rights. HCADSE-343

6. It is possible to open a DKE-protected file after stopping the DKE Service and removing the Email ID from the JSON file. HCADSE-345

7. It is possible to modify the design of a dependent Part file in a protected assembly file with view rights using the Select - Edit in place option and Select - Edit Definition. HCADSE-347

8. When opening a DKE-protected file without an authorized email address, the HaloCAD error message does not appear. HCADSE-377

9. Intermittently, the SolidEdge application may close when clicking OK in the Save Read Only Document window. HCADSE-690

Unsupported Versions

Support for Solid Edge 2020 is 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