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 PLM includes HaloCAD PROTECT and MONITOR capabilities, which actively monitor file access, upload, and download events while running in the background. During a file upload, HaloCAD evaluates if the file is already encrypted, and if so, it decrypts and then allows the file to be checked-in to the PLM Vault. In the event of a file access or download, the selected file is automatically protected. HaloCAD operates independently during the check-in and check-out process according to the rules established in the Classification Engine.

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 reading the current version of the release notes; however, if you are searching for a previous version, refer to the release notes for that version.

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

New Features

This section highlights the new features in the current release.

Support for Autodesk Vault Thin Client has been added to protect file downloads.

Improvements

There are no improvements to mention in the current release.

Limitation

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.

With this version, a file with a "label-only" MPIP label uploaded to PLM is stored following the metadata removal process. When the file is successfully downloaded, a configured MPIP label is assigned with protection.

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. While using the Share View option to open a file, an error message will occur as The remote server returned an error: (500) Internal server error and the link does not get 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 Service ID will be displayed as the "Owner" of the document, despite the email ID (Autodesk Vault login user) configured in the admin portal.

5. 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, make sure the user(s) or the group that the user belongs to who runs the Service does not exist in the group policy.

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