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 they take 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

Prerequisites

The following preparatory steps or conditions must be met before installing the product.

The add-on requires the registration of an application with Microsoft Entra ID, an Office 365 subscription, and access to recommended URLs. For additional information, please 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 statical 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 

• A = 0 Bugs

• B = at least 1 Minor Bug

• C = at least 1 Major Bug

• D = at least 1 Critical Bug

• E = at least 1 Blocker Bug

Security Rating

• A = 0 Vulnerabilities

• B = at least 1 Minor Vulnerability

• C = at least 1 Major Vulnerability

• D = at least 1 Critical Vulnerability

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

• A = >= 80%

• B = >= 70% and <80%

• C = >= 50% and <70%

• D = >= 30% and <50%

• 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 alternately stated by saying that if the outstanding remediation cost is:

• <=5% of the time that has already gone into the application, the rating is A

• between 6 to 10% the rating is a B

• between 11 to 20% the rating is a C

• between 21 to 50% the rating is a D

• anything over 50% is an E

Build 2.1

New Features

This section lists the new features in the current release.

1. Implemented a new feature to include metadata (label only) into CAD files using the CAD SDK. HCADSE-588

2. Support for watermarking CAD files (assembly, part, and draft) with MPIP labels, as well as 'label-only' MPIP labels that apply only metadata. HCADSE-589, HCADSE-595

Improvements

This section lists the improvements in the current release.

1. A proxy server configuration has been provided if the user's firewall blocks access to Secude's License Manager.

2. Support for a use case that compares the least permissions between source and destination files and applies the least permission during the import action. As a result, the destination file is modified with the least permission label and restricted control access. HCADSE-603

Fixed Bugs

This section lists the fixed issues in the current release.

1. Fixed an issue that triggered an BadInputError message while fetching the label with the custom Cloud Type configuration. HCADSE-346

2. Fixed an issue that prevented replacing a missing file in the main assembly file using SAP ECTR's Replace part and Update Active level options. HCADSE-439.

3. Fixed an issue that caused the Solid Edge application to crash when attempting to check-in a cloned large assembly file to SAP ECTR via the Save and display option. HCADSE-544

4. The option to deactivate the license (via the Deactivate button) has been removed from the HaloCAD About UI. HCADSE-591

5. Fixed an issue that caused the Design manager to crash and display an error message while trying to check-in the assembly file using the Save and display option in SAP ECTR. HCADSE-628

6. Fixed an issue that triggered an error message when attempting to open the cloned assembly file from SAP ECTR. HCADSE-632

Known Issues

This section lists the known issues in the current release.

1. SAP ECTR: During the upload sequence, in the Import on Demand Dialog only the protected ASM file will be visible and gets uploaded. Its dependent part files will not get imported to SAP. HCADSE-112

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

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

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

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

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

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

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

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

10. When a file is deleted from the SAP ECTR cache location, it will not load properly and a file missing window will appear. HCADSE-438

11. SAP ECTR: When attempting to open the cloned assembly file from SAP ECTR, an error message will appear as Function:"CIPropertyManager::SetPropertiesForClosedFiel". HCADSE-632

12. When importing a protected file into an unprotected file with the Replace part option, the HaloCAD restriction box does not appear, and the options are not restricted based on the least permission. HCADSE-635

13. The Solid Edge application will become unresponsive if you attempt to access the protected assembly file using SAP ECTR's Save and Display option. HCADSE-636

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