Release Notes

Introduction

The release notes provide a high-level overview of the new features, fixed issues, known issues, and prerequisites in HaloCAD Add-on for CAD. Before installing HaloCAD Add-on for CAD, review these release notes to understand any known limitations or issues that apply to this release.

Product Description

HaloCAD helps organizations protect CAD files by integrating with Microsoft Purview Information Protection (MPIP). It applies sensitivity labels to CAD files, helping safeguard intellectual property throughout its lifecycle. Protected files can be accessed only by authorized users with permissions defined by the applied sensitivity label.

Prerequisites

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

• Have an active Microsoft 365 subscription.

• Register an application with Microsoft Entra ID.

• Enable access to the required URLs.

• Enable TLS 1.2 or later on all client workstations to ensure secure communication.

Refer to the Technical Reference Manual for more information.

System Requirements

The following table of system requirements specifies the minimum and recommended technical specifications, including 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

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

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 Creo Parametric 13. HCADCRE-1138

Fixed Issues

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

1. Fixed an issue where both the configured .prt file type and the unconfigured .sec file type were protected and exported to the specified directory. HCADCRE-188

2. Fixed an issue where a sketch file could not be opened after opening an assembly file in the same session, and the error message "File .sec could not be retrieved" was displayed. HCADCRE-640

3. Fixed an issue where Creo file types were not saved correctly with protection to network locations when save_file_iterations was configured as yes or no in the config.pro file. HCADCRE-661

4. Fixed an issue where the design from a protected DRW file with a dependent part file could be imported into an unprotected drawing file, which could then be saved without protection. HCADCRE-671

5. Fixed an issue where exporting a protected drawing, format, or notebook file to DWG failed, and the message "DWG file creation failed" was displayed. HCADCRE-658

6. Fixed an issue where an exported DWG file from a protected part or assembly file opened with protection, but the design was not displayed and the Invalid DWG file error appeared. HCADCRE-659

7. Fixed an issue where a protected file could not be opened after protection was applied when the file was saved to a mapped or unmapped network location. HCADCRE-774

8. Fixed an issue where the ol file type was not protected when exporting a protected part file as Creo View (*.pvs), allowing the file to be opened and saved without protection. HCADCRE-784

9. Fixed an issue where a protected file imported using the Insert Layout option was imported without protection into a layout file, which could then be saved without protection. HCADCRE-853

10. Fixed an issue where a protected file imported using the Shrinkwrap option was imported without protection and could then be saved without protection. HCADCRE-858

11. Fixed an issue where .sldprt files were imported without protection when imported multiple times in the same or different sessions. HCADCRE-1062

12. Fixed an issue in Creo 11 where files could not be saved to a mapped network location when save_file_iterations was set to no. HCADCRE-1072

13. Fixed an issue where a part file instance opened without protection when opened from a large protected assembly file. HCADCRE-1094

14. Fixed an issue where watermark text from a previously imported file was displayed when creating or opening another file in the same session. HCADCRE-1142

15. Fixed an issue where protected files exported using the Save As Backup option were exported without protection. HCADCRE-1144

16. Fixed an issue where some options were disabled in a top-level assembly file with a Label without “protection label”. HCADCRE-1147

17. Fixed an issue where Creo closed unexpectedly when saving a protected file with save_file_iterations configured as no. HCADCRE-1148

18. Fixed an issue where authentication was triggered when a valid license was not available. HCADCRE-1152

19. Fixed an issue where a custom permission label was applied to a file when the user clicked Cancel or Abort in the custom permission dialog box. HCADCRE-1153

Known Issues

This section describes the known issues with the current release.

1. A Creo file can be opened by invoking the Creo Parametric application first, and then go to File > Open menu > select the file. Note that PTC itself does not suggest double-clicking, and as per the design, they recommend only using the File > Open option instead of double-clicking a file to open.

2. If you double-click on an encrypted Creo file, you will end up with an error message because the encrypted Creo file is forced to open before the HaloCAD DLL loads itself. Thus, the loaded file becomes unrecognized by the Creo Parametric application. HCADCRE-12

3. HaloCAD displays a pop-up “A file with the same name already in memory. Please rename the file or remove the existing file from memory “when a labeled file is relabeled and attempted to save. HCADCRE-169

4. When switching between the configured and unconfigured workspaces, a file will be labeled and exported from an unconfigured workspace. HCADCRE-186

5. In a protected file, the Sensitivity ribbon, along with the configured label, will be displayed while checking out an Assembly file. HCADCRE-189

6. Intermittently, the HaloCAD pop-up will display the message File may not be saved properly. Kindly save again when you save the Assembly file multiple times, and when you click OK on the pop-up. After closing and reopening the Creo application, when you open the same file, you'll receive a Cannot be retrieved error message. HCADCRE-386

7. The Creo application goes to the Not Responding state if you try to close it while the Microsoft Sign-in pop-up remains open. HCADCRE-412

8. Windchill: When the dm_upload_objects variable is configured as Explicit in the config.pro file, the saved protected file will not be uploaded during check-in after closing and reopening the application. HCADCRE-438

9. Windchill: When the dm_upload_objects variable is configured as Explicit, and dm verify subtype is configured as Yes in the config.pro file, the file upload fails while trying to check-In using the File -> Check-In option in the same session. However, after closing and reopening the file, it will be checked-in successfully. HCADCRE-443

10. Windchill: When the dm_upload_objects variable is configured as Automatic and dm verify subtype is configured as Yes in the config.pro file, the file upload fails for the first time. However, if uploading the file subsequently in the same session, the file will be checked-in successfully. HCADCRE-444

11. Windchill: When a sketch file is opened in the Windchill workspace and a part or assembly file is opened via the Open in Creo option during the same session, clicking the pencil icon changes the label from Not Set to the default label that is set in the Halo Core Server. HCADCRE-509

12. When a protected file is modified and saved several times, a HaloCAD error pop-up will appear, as “File may not be saved properly. kindly save again”. Also, if you try to label a new file in the same session, the file will not be protected. HCADCRE-557

13. Intermittently, Assembly files protected and saved on unmapped network locations using the Create Component option will not be loaded. HCADCRE-700

14. Windchill: When the life cycle state is configured, the drawing file will open without being protected in the Creo application. However, the dependent ASM and PRT will open with a configured label. HCADCRE-762

15. When you create a new drawing file, the Default model selection is updated with the name of the previously protected part file that was accessed in the same session, and the new drawing file is created with the protected part file's label. This is due to the application's actual behavior. HCADCRE-855

16. The label of the imported protected assembly file will not appear in the assembly file when the External Simplified representation option is selected. HCADCRE-859

17. PDF files exported from protected files by using the Adobe PDF printer option are not protected. HCADCRE-888

18. Windchill: When a large assembly file is protected with multiple labels and Multi-Label Optimization is enabled, if accessed from the Windchill workspace using the Open in Creo option, the same label is applied to both the assembly file and its dependent files. HCADCRE-1064

19. Exporting a DWG file may result in a 0 KB file being created. HCADCRE-887

20. Fixed an issue where the default label was not updated in the Sensitivity ribbon when importing an unprotected IGES or STEP file. HCADCRE-1019

21. Fixed an issue where only the top-level assembly (ASM) file was opened with the configured label, while dependent protected files were opened without labels when downloading the ASM file using the Export from Workspace option. HCADCRE-1149

Unsupported Versions

Support for Creo 10 has been removed in this release.

Changes

The HaloCAD Reader Add-on has been removed from this release. HaloCAD documentation no longer includes Reader-related content.

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 26, 2026