October Release Now Available! Explore the Latest Updates.
HaloCAD for Dassault Systemes SOLIDWORKS PDM
Auto Light Dark
Auto Light Dark

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 for PDM solution includes HaloCAD PROTECT and MONITOR capabilities and interacts with the respective PDM application. Files in SOLIDWORKS PDM folders are closely monitored. When a file is cut or copied to a non-SOLIDWORKS PDM folder, HaloCAD intercepts and protects it before reaching the destination folder. Also, any previously encrypted SOLIDWORKS application files or PDF files copied/moved to the SOLIDWORKS PDM folder will be decrypted and saved.

Prerequisites

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

  • A Public client/native (mobile & desktop) application is registered with Microsoft Entra ID.

  • An active Microsoft 365 subscription is available.

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

Requirements

The following table lists the system requirements for installing and running SOLIDWORKS PDM.

Components

Details

Supported Operating System

Windows Server 2022 and above with updates installed.

Supported file types

.sldprt, .sldasm, .prt, .asm, .slddrw, .x_t, .tif, .dwg, and .dxf

Other components

HaloENGINE GenNXT

Requirements

Supported SOLIDWORKS PDM applications for HaloCAD 

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

SOLIDWORKS Product Data Management (PDM) Server

HaloCAD Add-on version

  1. SOLIDWORKS PDM Server: 2024 SP 4.0, 2025 SP 1.2, and 2026 SP 0.0

  2. SOLIDWORKS PDM Client: 2024, 2025, and 2026

  3. SolidNetWork License Manager: 29.51.0001

2.0

SOLIDWORKS PDM 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 2.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 SOLIDWORKS PDM version 2026.

Improvements

This section lists improvements added to the current release.

  1. Starting with this release, HaloCAD for SOLIDWORKS PDM supports integration with HaloENGINE GenNXT and its features, replacing the legacy HaloENGINE integration. HCADSWP-282

  2. Removed the System ID field and renamed Customer ID to Profile Name in the HaloCAD for SOLIDWORKS PDM installer UI. HCADSWP-283, HCADSWP-313

  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.

Limitations

This section lists the limitations of the current release.

  1. When a non-office-protected file with a .pfile extension is copied to the SOLIDWORKS PDM vault folder, the file is decrypted, but the extension is not removed. HCADSWP-133

  2. File protection is not applied when copying files from a PDM folder in a VM to a local machine. Protection works when copying files between PDM and non-PDM folders within the same VM. HCADSWP-286

Fixed Issues

There are no major issues resolved in the current release to list.

  1. Fixed an issue where files were copied to the destination folder using Pack and Go, but only the main assembly file was protected, and the dependent files were not. HCADSWP-280

  2. Fixed an issue where files were copied to the local folder without protection when metadata was configured for Ad_group. HCADSWP-308

  3. Fixed an issue where the file was copied with protection, but the Event Type, IP Address, and OS fields were not updated in the HaloENGINE GenNXT Monitor log. HCADSWP-303

  4. Fixed an issue where the Event Type was not updated in the Monitor log when copying a file from a SOLIDWORKS PDM folder. HCADSWP-304

  5. Fixed an issue where the file was moved to the Documents folder, but File Explorer closed automatically when using the Send To option with Only Label (without protection) configured. HCADSWP-312

  6. Fixed an issue where .tmp files matching the size of the opened file were created when opening a file from a PDM folder in SOLIDWORKS. HCADSWP-314

  7. Fixed an issue where a file was not blocked, and the HaloCAD pop-up was not displayed when copying the file from a SOLIDWORKS PDM folder to a local folder with the action rule configured as Block. HCADSWP-316

  8. Fixed an issue where watermark text was not displayed correctly when opening a watermarked file from a SOLIDWORKS PDM folder in a local folder. HCADSWP-317

  9. Fixed an issue where the correct After Size value was not updated in the HaloENGINE GenNXT Monitor log when uploading a protected file to an SOLIDWORKS PDM folder. HCADSWP-323

Known Issues

This section describes the known issues with the current release.

  1. A screen capture of a protected HaloCAD file is possible. HCADSWP-15

  2. If Folder Name or Client Hostname metadata is defined in the classification engine, files will not be encrypted when copied from a SOLIDWORKS PDM folder to a non-SOLIDWORKS PDM folder. HCADSWP-41

  3. Files become corrupted when copied from the SOLIDWORKS PDM folder to a destination folder using the History option. HCADSWP-216

  4. When copying files from the SOLIDWORKS PDM folder using the Copy to or Move to options, the file is copied without protection, and the audit log is not updated. HCADSWP-214

  5. A .tmp file is created when opening a file from SOLIDWORKS PDM using the SOLIDWORKS application with HaloCAD for SOLIDWORKS PDM installed. The .tmp file is not cleared automatically even after closing the SOLIDWORKS application. HCADSWP-242

  6. Copying files from the PDM folder with an unconfigured rule may take longer than expected. HCADSWP-278

  7. An “Item Not Found” pop-up may appear. Clicking Try Again displays the same pop-up again, after which the file is copied successfully to the local folder. HCADSWP-279

  8. The Error field in the Monitor log is not updated to YES for error cases. HCADSWP-332

  9. The correct After Size value is not updated in the Monitor log when opening a file through the SOLIDWORKS application with a configured or unconfigured rule. HCADSWP-333

  10. The ACT field displays Decrypted instead of Allowed when opening a file through the SOLIDWORKS application with an unconfigured rule. HCADSWP-334

  11. Multiple Monitor log entries are created when an unauthorized user attempts to open a file from a PDM folder through the SOLIDWORKS application. HCADSWP-335

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.

Metric

Value

Coverage

85.7%

Maintainability Rating

A*

Reliability Rating

A*

Security Hotspots Reviewed

A*

Security Rating

A*

Quality Gate report


Last updated: