December 19, 2022
BETA CAE Systems announces the release of
About this Release
BETA CAE Systems announces the release of SPDRM v1.8.1.
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.
Enhancements and known issues resolved
From now on, any Additional Attributes that are assigned to a simple file are automatically inherited when it is overwritten.
It is now possible for authorized users to get the "Last Seen" attribute for a user through the "um.getUserProfileInfo" script function.
Improved error handling when a script action with a wrong function name is executed.
Users Management - Security
The role of the active users is now displayed in a new column in the "Logged In Users" window.
Sorting of issues columns is now applied to all filtered issues and not only to the issues in the current page of the Issues workspace.
The new boolean key "preserveDMACL" has been introduced in taxis.conf to support the need to preserve the existing ACLs of a file after the file is overwritten. In the "false" case, the ACLs are initialized when a file is overwritten (default).
From now on, environment variables can be used for the parametric definition of paths in SPDRM Server and Client configuration files (i.e. taxis.conf, taxisprops.xml.linux, taxisprops.xml.windows).
Known issues resolved
It was not possible to edit an external file (i.e. a file for which SPDRM only stores its path as a link), through a SPDRM client on Windows OS.
On Windows OS, when executing an ANSA application node with "-i" option and Value Type "From input slot" in its Application Settings, the Input slot file would not be sent for opening in ANSA. This occurred when the file path contained forward slashes as path separators.
A scheduled node would fail to start its execution in KOMVOS.
An error could occur while trying to access the Pedigree of a Subsystem with Iteration (or any other versioning property) larger than 1.
Data Migration / Archival
During data migration, using the DM Import function, all non-STRING (e.g. FLOAT, ATTACHED_FILE) additional attributes would be stored as STRING in the target environment.
In some cases the DM Import operation would fail to import all data to the target environment despite returning a success signal.
Process Design / Execution
The standard output would be printed multiple times in the output window during a script/process execution, when the task was executed in a no-gui client session with Python engine.
Any space character left by mistake in a variable name used by the command line options of an application node, would block both the editing of the application settings and the launch of the application upon node execution.
Process Instance List
The Process Instance List would fail to launch properly on Oracle-based SPDRM environment.
The progress value would not be displayed for a not started sub-process of an instantiated MxN node.
It is now possible to set specific ACLs for Nodes or Inner Workflows (sub-processes), through the "Privileges" context menu option on the Process Library.
Process Observer / HPC submission
Under certain circumstances, some Observer Nodes would be re-executed instead of resumed. Consequently, their already submitted jobs would be re-submitted due to re-execution of their pre-run script.
The "process.updateObservableJobs" would fail with error -100 if a job was submitted through an Observer Node ran in no-gui mode, with the session closed before the execution of the function.
The function "dm.getDMItemAdditionalAttributes" would fail to return the additional attributes of a rich library item.
The function "dm.uploadFiles" would reset their ACLs in case of overwrite of files.
The function "dm.uploadFiles" would not return a handle id when the skip option was used in case of conflict.
The function "process.periodicScript" would fail to be executed in Python script engine.
The function "dm.getDMItemReferences" would raise a TypeError exception in Python script engine when all optional arguments were used.
It was not possible to delete past executions of hanging scheduled jobs (i.e. Execution State=RUNNING).
Users Management - Security
In some cases it would not be possible to set privileges on RLI containers, through the data tree.
During the creation of a new role, the system would partially fail to copy/inherit the ACLs from the "source" (existing) role to the "target" (new) one, when the option "Apply privileges of role" was used. To fix any ACLs that may be missing due to this bug, a new web service named "Copy ACL" is provided through the "migration" tab of the SPDRM Admin page, to trigger the copy of ACLs on demand, from a "source" to a "target" role.
A user would be able to access the Properties/Attributes of part instances, through the GUI (i.e. Contents tab of Subsystem), although he/she lacks the required permissions.
The login to the SPDRM admin web console through LDAP authentication would fail.
For both "auth/login" and "auth/roleLogin" REST endpoints, in case of incorrect credentials, the Response Status is set to 401 (Unauthorized). Also, in the Response Body, only data with non-null values are returned.
For the "auth/login" REST endpoint, in case of correct credentials and existence of multiple roles assigned for the current user, the set of the available roles is returned.
The communication between the BETA Apps Launcher (BAL) and the SPDRM Server would fail, in case the SPDRM_EXTERNAL_CONNECTIONS license feature was not available on the license server.
For more details about the new software features, enhancements and corrections please, refer to the Release Notes document.
Updated user's guide, Installation Guide, Scripting API guide, and REST API documentation.
Supported Platforms and System Requirements
From this version onward, the server application of SPDRM is available only for Linux 64bit.
NOTE: Installation of SPDRM server application on MS Windows is not supported anymore.
The client application 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 "sign in" 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.8.1" and are dated as of December 19, 2022.
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).
Earlier software releases are also available in the sub-directory called "Previous_Versions" or in a folder named after the product and version number.