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

The HaloCAD for PLM solution integrates seamlessly with the PLM application, including the features of HaloCAD PROTECT and HaloCAD MONITOR while utilizing Microsoft Purview Information Protection (MPIP), formerly Microsoft Information Protection (MIP), to provide Enterprise Digital Rights Management (EDRM) capabilities.

It provides access to MPIP-protected files, including label handling and privilege enforcement. Any file access actions, such as check-out or export, that may result in a download are intercepted by the HaloCAD for PLM solution, automatically protected based on predefined rules, and then delivered to the end user. Similarly, file access actions such as check-in or upload are intercepted and examined. If a protected file is detected, it is decrypted, and the unprotected file is returned to the PLM vault. For CAD users, the handling of CAD files remains seamless, as these processes occur entirely in the background. By applying MPIP labels, the solution ensures end-to-end security for CAD files, while all upload and download activities are continuously monitored and logged to provide complete traceability.

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 Autodesk Vault versions for HaloCAD for Autodesk Vault

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

Autodesk Vault 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 

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

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.

1. With this release, the Monitor log will be updated with the proper "act" when uploading to Vault. HCADVLT-480

2. Implemented single folder ASM file optimization for the Vault Client. This feature is enabled by default when the Single Label Optimization option is turned on in the configuration tool. Ensure that all ASM files are placed within a single folder for the optimization to take effect. HCADVLT-494

3. Compound IDs are applied to multiple files during folder downloads in the Vault Professional client. HCADVLT-504, HCADVLT-506, HCADVLT-507

Improvements

There are no improvements to mention in the current release.

1. Upgraded JDK 17 with Tomcat 10.x support. HCADVLT-501, HCADVLT-508

2. In earlier releases, HaloENGINE and HaloENGINE Service functioned independently and required separate installers. Beginning with this release, HaloENGINE is delivered as a unified component that bundles the HaloENGINE Service DLL within a single installer. HaloENGINE now connects to Microsoft Purview Information Protection to fetch the sensitivity labels and make them available for label configuration. Similarly, HaloCAD for Autodesk Vault is now delivered as a unified component that includes the HaloENGINE Service DLL, which not only fetches sensitivity labels but also manages file encryption and decryption. These enhancements simplify deployment and improve overall performance. HCADVLT-512

Limitations

This section lists the limitations of the current release.

When HaloCAD is deployed in an environment, we recommend that the administrator restrict access to non-Proxy URLs using a firewall or other network application. This is because, as HaloCAD is a proxy, non-proxied actual URLs will also be accessible, leading to data leakage. Therefore, we recommend restricting access.

Fixed Issues

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

1. With this release, the service is provided as a DLL, and tenant details have been incorporated into the HaloCAD for Autodesk Vault UI.

2. Service-related fields have been removed from the Configuration Tool user interface. HCADVLT-515

Known Issues

This section describes the known issues with the current release.

1. Thin client Autodesk Vault Browser-based access is not supported. HCADVLT-13

2. When using the Share View option to open a file, an error message appears: “The remote server returned an error: (500) Internal server error.” Consequently, the link is not created. HCADVLT-25

3. Intermittently, the protected file does not open with a double-click or a right-click. There will be an error message “File can't be opened in the application”, or “The remote server returned an error (500) internal server Error”.

4. HaloENGINE ID will be displayed as the "Owner" of the document, despite the email ID (Autodesk Vault login user) configured in the admin portal.

5. An error message appears as “Error 1069: The Service did not start due to a logon failure” when you start the HaloENGINE Tomcat Service. This is because the user who is running the service or a specific group that the user belongs to (e.g., Administrators) is added to the Deny log on as a service policy (Local Security Policy > Security Settings > Local Policies > User Rights Assignment). To prevent such an error, ensure that the user(s) or the group to which the user belongs, who runs the Service, are not included in the group policy.

6. Failover Configuration Limitation: When Failover is configured and the secondary HaloENGINE server is running, file protection is not applied. In this release, the Failover mechanism does not function as expected. Therefore, it is recommended not to configure Failover. This issue will be addressed in the next 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