April 30, 2025

BETA CAE Systems announces the release of
SPDRM v1.11.5

About this Release

BETA CAE Systems announces the release of SPDRM v1.11.5.

This version delivers a number of enhancements and fixes to the users of the most advanced Simulation Process Data and Resources Management software.

The most important enhancements and fixes are listed below.

Contents

Enhancements in SPDRM v1.11.5
Known issues resolved in SPDRM v1.11.5
Documentation Updates
Supported Platforms and System Requirements
Download

---

Enhancements in SPDRM v1.11.5

Process Design / Execution

A new optional argument (reset=True/False, with default value False) was added to the scriptCommands.abort function. This controls whether the node will get in Error state after execution or if it will be Reset.

Process Observer / HPC submission

From now on, the start date of the observer node is used as job dispatch date. In addition, the retention policy for observable jobs now also applies to dispatched jobs, based on their dispatch date.

 

Known issues resolved in SPDRM v1.11.5

Data Management

Exporting a Subsystem Group, of solver File Type, that contained adapted Subsystems “with References” in its Representation File Content, would fail to export the source "unadapted" Subsystems.

Data Search

Queries containing the 'NOT' operator and queries for an empty Comment field might not function correctly.

Data Migration / Archival

The import of an SPDRM DM package would be aborted in case the dataset included objects of type 'changeset'.

Users Management - Security

The sorting function in the Users list of the SPDRM Admin web portal (Users Management tab), might not work as expected.

It wouldn't be possible to control the visibility of accepted values for a property (e.g., Project) per role, if the list of accepted values was determined by rules.

Scripting

Exporting a DM item through scripting would fail (error code -100: 'the user does not have the required privileges') for “private items”, even for their owner. Private items are typically those without privileges assigned to any role (user group), making them accessible only to their owner.

 

For more details about the new software features, enhancements and corrections please refer to the Release Notes document.

 

Documentation Updates

Updated Documents

Updated Installation Guide, Administrator’s Guide, Scripting API Guide and REST API documentation.

 

Supported Platforms and System Requirements

The server software of SPDRM is running under 64bit flavors of Linux.

The client software of SPDRM is running under 64bit flavors of Linux and MS Windows.

The software requires a different license key to the rest of the products of BETA CAE Systems. This license key should be incorporated into the same license file, if such is already installed, and requires beta_lm, the proprietary license manager of BETA CAE Systems.

For details, refer to the System Requirements document.

 

Download

Where to download from

Customers who are served directly by BETA CAE Systems, or its subsidiaries, may download the new software and documentation from their account on our server. They can access their account through the "sign in" link at our website. Contact us if you miss your account details.

The Downloads menu items give you access to the public downloads.

Customers who are served by a local business agent should contact the local support channel for software distribution details.

What to download

All files required for the installation of this version reside in the folder named: "SPDRM_v1.11.5" and are dated as of April 30, 2025.

These files should replace any pre-releases or other files downloaded prior to that date.

The distribution of this version of SPDRM is packaged in one, single, unified installation file that invokes the respective installer and guides the procedure for the installation of the required components (i.e. SPDRM server and client).

For the installation of the software download the .tar.gz file.

Earlier software releases are also available in the sub-directory called "Previous_Versions" or in a folder named after the product and version number.