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 PDM solution includes HaloCAD PROTECT and MONITOR capabilities and interacts with the respective PDM application. Files in SOLIDWORKS PDM folders are closely monitored. When a file is cut or copied to a non-SOLIDWORKS PDM folder, HaloCAD intercepts and protects it before reaching the destination folder. Also, any previously encrypted SOLIDWORKS application files or PDF files copied/moved to the SOLIDWORKS PDM folder will be decrypted and saved.
Requirements
The following system requirements table specifies the minimum and recommended technical specifications, such as software and network resources, necessary to run the product.
|
Components |
Details |
|---|---|
|
SOLIDWORKS PDM |
SOLIDWORKS PDM Server:
Supported SOLIDWORKS PDM Clients:
|
|
Office 365 Subscription |
Refer to the Technical Reference Manual for details on TLS 1.2 and application registration. |
|
Supported file types |
|
|
Other components |
HaloENGINE |
Requirements
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 1.5
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
There are no new features to highlight in this release.
Improvements
This section lists improvements added to the current release.
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 Tomcat 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. These enhancements simplify deployment and improve overall performance.
Limitations
This section lists the limitations of the current release.
When a non-office-protected file with a .pfile extension is copied to the SOLIDWORKS PDM vault folder, the file is decrypted, but the extension is not removed. HCADSWP-133
Fixed Issues
There are no major issues resolved in the current release to list.
Known Issues
This section describes the known issues with the current release.
-
A screen capture of a protected HaloCAD file is possible. HCADSWP-15
-
Using the COPY and XCOPY options, it is possible to copy a file from the SOLIDWORKS PDM Vault to a non-SOLIDWORKS PDM folder. HCADSWP-34
-
If Folder Name or Client Hostname metadata is defined in the classification engine, files will not be encrypted when copied from a SOLIDWORKS PDM folder to a non-SOLIDWORKS PDM folder. HCADSWP-85, HCADSWP-41
-
Files become corrupted when copied from the SOLIDWORKS PDM folder to a destination folder using the History option. HCADSWP-216
-
When copying files from the SOLIDWORKS PDM folder using the Copy to or Move to options, the file is copied without protection, and the audit log is not updated. HCADSWP-214
-
A .
tmpfile is created when opening a file from SOLIDWORKS PDM using the SOLIDWORKS application with HaloCAD for SOLIDWORKS PDM installed. The.tmpfile is not cleared automatically even after closing the SOLIDWORKS application. HCADSWP-242 -
A file that was applied with a watermark label by HaloCAD for SOLIDWORKS PDM does not display the watermark text when opened from the SOLIDWORKS PDM local folder. HCADSWP-248
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.
|
Metric |
Value |
|---|---|
|
Coverage |
84.2 % |
|
Maintainability Rating |
A |
|
Reliability Rating |
A |
|
Security Hotspots Reviewed |
A |
|
Security Rating |
A |
Quality Gate report