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 Teamcenter applications for HaloCAD 

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.

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

New Features

This section lists the new features in the current release.

1. Added support for testing SOA connections with the Windows Credential Manager using the configuration tool. HCADTCR-481

2. Support for the Teamcenter 2312 version. HCADTCR-462

3. HaloCAD for Teamcenter allows for failover connections between two HaloENGINEs. If the primary HaloENGINE fails, the secondary HaloENGINE takes over, minimizing downtime and ensuring continued functioning. This failover mechanism can be configured using the HALOCAD Config tool as well as the command line. HCADTCR-460

Improvements

This section lists the improvements in the current release.

1. All file information related to ASM Optimization with Multi-Label configuration will be updated in the monitor log. HCADTCR-457

2. Teamcenter client property values will be correctly updated in both the haloproxy and monitor logs. HCADTCR-442

3. Support for configuring HaloCAD and HaloENGINE parameters using the command line. HCADTCR-489

4. Added a new browser client parameter to log the user agent value in the RequestClientAppliation field. HCADTCR-487

5. A new field named "blocked_by":["blocked_by_rule"] has been added to the HaloENGINE monitor log to describe the Block action. HCADTCR-473

Limitation

This section lists the limitations of the current release.

A text file downloaded from RAC is protected as expected. But if the Teamcenter server is set up with Windows encoding, such as cp-1252, then a text file downloaded from the client will be inserted with a Windows line break, causing the file to be corrupted and unreadable. Therefore, it is advised against protecting text files when such a setting is present in your Teamcenter server environment. Additionally, if a protected text file is downloaded and uploaded again into Teamcenter (via RAC), the file size is updated as “0". HCADTCR-88, HCADTCR-132

Fixed Issues

This section lists the fixed issues in the current release.

1. Fixed an issue that caused the protected Office file extension to become generic protection with the pfile extension and prevented opening in the MS Office application. HCADTCR-483, HCADTCR-479

2. Enabled SHA-256 algorithm for ticket digest option in Teamcenter RAC for TLS configuration. HCADTCR-480

Known Issues

This section lists the known issues in the current release.

1. If an Office file is downloaded, the file gets protected, but the extension changes. For example, sample.docx > sample.doc. HCADTCR-127

2. If a Non-CAD/Non-office file is downloaded, the file gets protected as per the rule configured in HaloENGINE but the extension is saved with native format (i.e., .txt, .jpg, .bmp) instead of .ptxt or .pfile. HCADTCR-35

3. Error message appears as Network Error: Socket Timeout Exception while downloading a large file from Teamcenter with HaloENGINE Service mode configured as Remote. HCADTCR-239

4. Error message appears as “Error 1069: The Service did not start due to a logon failure” when you start the HaloENGINE 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.  

5. It is possible to export an NX file without protection using the option Export assembly from Teamcenter in the NX application. HCADTCR-300

6. MS Word file does not open in the Teamcenter Rich client application's Viewer Tab, though the file is protected. HCADTCR-304

7. The deployment of an already installed HaloENGINE is not supported by the current installer. The next release will include a fix for this.

8. Teamcenter Creo Integration does not function properly with Creo 10 and Teamcenter 14 when combined with the HaloCAD Creo Add-on. Errors appear when you use the Open folder option. HCADTCR-448

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