BETA CAE Releases SPDRM v1.1.1

beta_logoTHESSALONIKI, Greece, Apr 9, 2015 – BETA CAE Systems S.A. announces the release of SPDRM v1.1.1. This version delivers several most anticipated enhancements, along with a number of resolved known issues, to the users of the most advanced simulation process data and resources management tool.

040915_spdrm_1.1.1_picture1The most noticeable software enhancements and code corrections are listed below.

Enhancements

Process Management

  • From now on, the modification and execution privileges defined during the design phase and saved in the node definitions are respected.
  • From now on, the M instances of an MxN node will be automatically assigned (i.e. set execution privilege) to the N users of the selected Execution Roles.
  • The default contents of the Process Instance List have changed. It is also now possible to select and delete a multi-selection of nodes.
  • It is now possible to search also among draft node definitions.
  • A check was added for possible node name conflicts, to avoid the creation of nodes with identical names within the same sub-process.

Data Management

  • It is now possible to lock or unlock simulation models, to avoid their deletion or modification.
  • New context menu options have been added to linked directories of DM items.
  • The image of the selected component in the history graph is now displayed under the list of its properties and attributes.
  • It is now possible to search items based on their creation date, by using the variable “today”.

Resources Management

  • From now on, the values of the default launch options of applications, used by mimetypes and application nodes, are automatically updated when the registered application settings are updated.

Scripting

  • The script function dm.selectDataFromDataTree has been added to enable the selection of one or more files, folders and/or DM items from the data tree window.
  • A new argument was added in the script function dm.queryDMItems to enable the definition of the DM Item types for which the specified query will be applied.
  • The ability to define whether the associated TMP folders will be deleted or not upon the deletion of a node was added as an additional argument in the script function process.instantiateNode.
  • The script function emailer.sendMail has been modified to get multiple recipients and add attached files from the file system.

GUI

  • The pre-run, main and post-run script areas of application nodes have been rearranged using a tabbed layout, to provide more space for script editing.

Miscellaneous

  • It is now possible to send emails through the SPDRM Client (Tools > Send Email) by using an outgoing authenticated SMTP mail server.

Known Issues Resolved

Process Management

  • Deleting a starting option of an application node from the registered applications console was neglected when the application was called.
  • User could modify the properties/settings of a node, although his current role did not belong to the list of modification roles for this node.
  • The options “Auto Start” and “Auto Complete” were automatically activated for MxN instances, even for nodes that had been designed to have these options de-activated.
  • The information about the version history of nodes was lost when saving them in Drafts.
  • A user could replace a node with another version of it, through the “Check Available Versions” option, even without a delete permission on it.
  • The option “Check Available Versions” was not available to users whose current role had not been assigned “Design” privilege.

Data Management

  • An error could occur during changing the status of a component from “WIP” to “Error”.
  • When importing a new linked directory under a DM item the previous one was not deleted.
  • It was possible to import files and/or subfolders on DM folders, no matter if the user’s current role had “Modify” privilege on them. Moreover, in some cases a user was not possible to add subfolders on DM folders, although the folders were owned by him/her.

Resources Management

  • An error could occur when selecting a user, while the User Management window was minimized.

Scripting

  • In some cases, it was not possible to load Python functions help from their source.
  • The script function dm.downloadFolderById returned an empty list when the requested folder was empty.
  • The script function dm.selectComponentsFromQueryResults could return wrong error code.
  • The script function process.getValuesOfNode returned the default values of output slots and variables, instead of the run-time values. Moreover, the type of the returned variable was always of type string, instead of the same type as the one of the source variable.

ANSA Connect

  • The status of a component could be switched from “OK” to “WIP” through ANSA script.
  • Some rules needed to be removed from the Component section of the data model configuration file since they prevent version spin-up from ANSA v15.1.0 and later.

GUI

  • An error could occur when the user changed the Windows theme, while the SPDRM Client was running.

Miscellaneous

  • The operation of the switching user or role failed to be aborted, when the “Cancel” button was pressed in the “Unsaved Changes” window, in case there was unsaved work in the “Process Designer’.
  • An error could occur when sending email or setting up an SPDRM update notification, if the required server e-mail configuration had not been set properly.

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

Configuration

Updated configuration files

  • Updated data model configuration file (dm_structure_TBM.xml).

Documentation Updates

Updated Documents

  • Updated process template (component_build.json).
  • Updated ANSA script for parsing the XML file (ParseXML.bsx).

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 of other products of BETA CAE Systems, if such is already installed, and requires beta_lm, our proprietary license manager.

For details, refer to the System Requirements document.

Where to download from

Customers who are served directly by BETA CAE Systems S.A. may download the new software, examples and documentation from their account on our server. They can access their account through the “user login” link at their website http://www.beta-cae.gr.

Contact them if you miss your account details. The [Public] link will give you access to the public downloads area.

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.1.1” and are dated as of April 8, 2015. This package contains the server software on Linux 64bit and MS Windows 64bit, and the client software on Linux and MS Windows 64bit systems.

About BETA CAE Systems S.A.

BETA CAE Systems S.A., headquartered in Thessaloniki, Greece, is a private engineering software company committed to the development of state of the art CAE software systems that meet the requirements of all simulation disciplines. The company’s products, the ANSA / µETA pre- & post-processing suite, and SPDRM, the simulation-process-data-and-resources manager, hold a worldwide leading position across a range of industries, including the automotive, railway vehicles, aerospace, motorsports, chemical processes engineering, energy, electronics, heavy machinery, power tools, and biomechanics.

Committed to its mission to produce best-in-class CAE software systems, BETA CAE Systems offers products that consistently exceed expectations and provides exemplary technical support to its customers. The company’s continuously growth attest to the high level of customer satisfaction and user confidence.

Leave a Reply

Your email address will not be published. Required fields are marked *