November 29, 2019
BETA CAE Systems announces the
About this Release
BETA CAE Systems announces the release of SPDRM v1.3.2.
This version delivers a number of enhancements and fixes to the users of the most advanced Simulation Process Data and Resources Management tool.
The most important enhancements and fixes are listed below.
Enhancements and known issues resolved
In case of conflict during the creation of a new data object from the context menu of the "Structure" container (e.g. Add Simulation Model), the system automatically proceeds with the spin-up option.
Added support for rule-based generation of the file extension for the files of DM Items and Rich Library (e.g. request extension .nas for the files of Subsystems with File Type=Nastran and .k for the files of Subsystems with File Type = LsDyna).
Process Design / Execution
Added protection for the accidental removal of required/mandatory launching options through the Application Settings of Application Nodes.
Add the script function localFileReader.fileExists that checks the existence of a file in a network path, utilizing the mechanism that bypasses the SMB client side caching (on Windows clients).
The name of the running script action and the id of the selected data object are now displayed in the list of running tasks (appears at the bottom right corner), during the execution of a script action.
Users Management - Security
Add the ability to import Linux/Unix users from a passwd file.
Known issues resolved
Fail to save subsystem if the backslash character (" \ ") was used in the value of any of its attributes.
Process Design / Execution
Suppress erroneous error messages that could pop-up in the Notification Center during process execution.
File output slot could not be released when the file already existed in the target path.
Fix the failure of function dm.downloadFileById during downloading files that already exist in the target path.
Fix error that occurred when trying to export a Script Action that references a file that resides on the local filesystem.
Script API for Eclipse
Fix invalid reference to SPDRM Client libraries when editing SPDRM scripts in Eclipse.
For more details about the new software features, enhancements and corrections please, refer to the Release Notes document.
Updated installation guide.
Supported Platforms and System Requirements
The server software of SPDRM is currently available on Linux and MS Windows 64bits.
The client software of SPDRM is running under 64bit flavours 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.
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 "user login" link at our web site.
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.3.2 " and are dated as of November 29, 2019.
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 on each platform type, download from the respective folders, the .tar.gz file for Linux or the .zip file for Windows.
Earlier software releases are also available in the sub-directory called "Previous_Versions" or in a folder named after the product and version number.