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 Viewers is a lightweight application designed to view HaloCAD-protected files in other CAD-Viewer applications with “View only” access to all users who have access to it. This application is useful for Suppliers or Partners who need to access HaloCAD-protected models or drawings in their environment.

System Requirements

The following system requirements table outlines the minimum and recommended technical specifications, including software and network requirements, necessary to run the product.

Requirements

Supported Viewer applications for HaloCAD for Viewers

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

Viewer 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 1.6

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 highlights the new features in the current release.

Support for enabling the FIPS module has been added to both the installer UI and silent installation. When enabled, MPIP uses only FIPS-compliant encryption algorithms, and when disabled, it uses standard encryption algorithms. If this option was not enabled during installation, it can later be enabled through a registry entry. HCADV-360

Improvements

This section lists the improvements in the current release.

1. Integrated eDrawings Viewer support into the existing viewer implementation to enable handling of eDrawings file formats. HCADV-365

2. Added support for Autodesk Revit LT 2026. HCADV-358

3. Added support for eDrawings 2026.

4. Updated MSAL code to enforce TLS 1.2. HCADV-388

Limitations

This section lists the limitations of the current release.

When a protected file (ED/EDZ/PVS/PVZ) with ‘View’ rights is exported using the Save As option, the export is blocked; however, a 0 KB file is still downloaded. HCADV-289

Fixed Issues

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

1. Fixed an issue in which protected files could be exported as unprotected video (.avi) files from the Teamcenter Visualization Professional application via the Record option. HCADV-211

2. Fixed an issue where the Teamcenter Visualization application closed after clicking OK in the HaloCAD pop-up while exporting a protected file as PNG using the Export Image option. HCADV-300

3. Fixed an issue where a protected JT file was imported as an unprotected JT file using the File → Insert option in Teamcenter Visualization. HCADV-311

4. Resolved an issue where the HaloCAD information pop-up appeared multiple times, and the exported PVS file was saved as 0 KB when exporting from an unprotected file while the Viewer was running. HCADV-312

5. Resolved an issue where markup and annotation text were not added to the PVZ/EDZ file when saving the file using the Save All option. HCADV-302

6. Resolved an issue where an error was displayed and HaloCAD for Viewers failed to start when installed using a new folder name in the Destination Location field. HCADV-197

7. Fixed an issue where the Creo View application closed unexpectedly when opening an unprotected EDZ file. Additionally, when opening an unprotected PVZ file, a HaloCAD restriction pop-up and a Creo View error pop-up were displayed, preventing the file from opening. HCADV-334

8. Fixed an issue where the HaloCAD for Viewers pop-up was delayed and loaded only after 20–25 seconds when opening the Solid Edge 2D Drafting application. HCADV-350

9. Fixed an issue where an unprotected file was exported with protection when a protected file was already open in the same session. HCADV-354

10. Fixed an error where protected files could be opened without the user cache. HCADV-369

11. Fixed an error where unprotected .jt files could not be opened when HaloCAD for Viewers was running. HCADV-368

12. Fixed an issue where a HaloCAD error was displayed and protected DWG/DXF files could not be opened in the eDrawings application. HCADV-387

Known Issues

This section describes the known issues with the current release.

1. It is not possible to open a protected DWG file in Creo View Express 7.0. HCADV-35

2. It is not possible to capture a screenshot of an unprotected file in Creo View Express, Solid Edge 2D Drafting, AutoCAD LT, or Teamcenter Visualization Viewer once HaloCAD for Viewers is initialized. HCADV-39

3. When you double-click or right-click to open a protected VDS file with the SAP 3D Visual Enterprises Viewer option, it does not open in SAP 3D Visual Enterprise Viewer. HCADV-46

4. When opening protected files, such as IGES or IGS, or when cloning an unprotected intermediate.PAR or.VDS files will be created. HCADV-48

5. Multiple times, the HaloCAD restricted will appear while opening a protected file in Teamcenter Visualization Base and clicking on the option Tool-> Home button. HCADV-50

6. A protected IGS file fails to open; instead, a pop-up will display as Failed to open document appears while opening it. Furthermore, the Teamcenter Visualization base application goes to the Not Responding state. HCADV-51

7. In Creo View Express 7.0, the application will close abruptly if the Active Mail via E-Mail option is selected. HCADV-54

8. While you double-click to open the protected file, an error message will appear as “The file is not supported by Creo View”. HCADV-60

9. It is not possible to open the protected file in SAP 3D Visual Enterprise Viewers by anyone other than the user who installed HaloCAD. HCADV-66

10. AutoCAD LT application will crash while exporting the protected file in .DGN format. HCADV-69

11. When a Viewer application is installed in a way to start (run as) administrator, you may receive an error message “Drawing file” is not valid instead of the HALOCAD pop-up “Protected files can be loaded”. This is because the HALOCAD for Viewers application did not load properly due to the lack of administrator privileges in the existing instance. HCADV-75
    Workaround: Close the existing HALOCAD for the Viewer instance and start the viewer with administrator privileges.

12. Protected JT files exported from NX 1953 and 1899 series will not open in Teamcenter Visualization Base 12.0. HCADV-87

13. It is not possible to open the protected Solid Edge file by double-clicking on it, and doing so would result in an error message from the Solid Edge 2D Drafting tool. HCADV-95

14. The protected AutoCAD file cannot be opened by double-clicking on it, and doing so will result in an error message from the AutoCAD LT 2020 application. HCADV-97

15. It is possible to take a screenshot or print a screen of the protected JT file from the JT preview window in the Teamcenter Embedded viewer application. HCADV-98

16. It is possible to export the protected file as unprotected from the Creo View application using the Save Current View As option. HCADV-160

17. The Creo View 9.1 application will crash if an unauthorized user attempts to open a protected file. HCADV-161

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