The latest release of RTist 11, called 2020.22, is now available. Here’s a look at what’s most noteworthy:

Final Modifier Supported

The C++ 11, Final Modifier is now supported by the model compiler. There is a new Final property that can be set on classes and capsules to specify that they cannot be inherited. The same property is also available on operations to specify that they cannot be overridden.

Properties Final

Automatic Variables with Auto Keyword

Another C++ 11 feature is automatic variables declared with the auto keyword. In RTist, you can now create attributes typed by a special auto type that has been added to the CppPrimitiveDatatypes package. You need to specify a default value for the attribute, set its Initializer Kind property to either “equal” or “brace” and make it static const or static constexpr, so that the model compiler will generate an initializer for the corresponding C++ variable. The C++ compiler will deduce the type of the variable from that initializer value.

Auto Type

 

Fix for Broken References

An important improvement in the 2020.22 release is the better support for working with broken references. In the previous versions, the tool had difficulties coping with certain broken references, and as a remedy it sometimes deleted elements with such references. Now this no longer happens, and instead we have made it easier to fix broken references by means of a new Quick Fix called “Rebind Broken References”. This quick fix can be run from the context menu of a broken reference problem in the Problems view, and it is able to rebind broken references that have been introduced by refactorings, where not all affected references could be updated at the time of the refactoring. A common example is when elements in a model library are moved so they end up in a different model file. This affects all client models that use the library, and since the refactoring of a library typically is done without knowledge of which clients that may use it, many references in client models can become broken because of this. The “Rebind Broken References” quick fix is able to update all such broken references in one go.

QuickFix

TC Editor Enhancements

We have also improved the TC editor in this release. The TC editor’s Code tab now highlights syntax errors which makes it easier to work with transformation configurations textually.

 

Finally, let’s mention the graphic visualization of TC relationships that was first available as an experimental feature in the previous release. In this release, we have continued to improve this feature and it now can show both prerequisite and inheritance relationships for TCs (separately or both at the same time). The layout of the graphs has also been improved which is noticeable especially for big graphs. This feature is still experimental, and we hope to complete it in the next release.

 

 

Graph Visualization

 

Comment wrap
Further Reading
article-img
Secure DevOps  /  July 23, 2020
Introducing Design Room ONE Version 2.1
By: Alexander Strabykin, Development Lead at HCL Software
The latest Sprint 2020.26 bring us a new version 2.1 of Design Room ONE available for HCL RTist users. In this new version authentication functionality has been significantly improved and lost its EXPERIMENTAL tag. One of the improvements includes refactoring the way the Design Room ONE server integrates with Keycloak for authentication. As a result, the configuration procedure is now easier: all the settings that need to be updated are now located in Design Room ONE’s main configuration file – server-config.json. Due to these improvements, there is now no need for Design Room ONE to store a Keycloak administrator key making this integration even safer, since Design Room ONE server would only be able to access pieces of Keycloak information it needs to manage access to its designs. You can refer to Authentication Setup for detailed instruction on migrating Keycloak realms configured with previous versions of Design Room ONE without loosing any information about users and their roles. Another update related to server configuration is the introduction of a single property dr_db_url controlling database connection — provides more flexibility and allows using password protected databases, which are standard in cloud environments like Azure or AWS. This is since version 2.1 Design Room ONE supports integration with Collaborative Lifecycle Management (CLM) tools version 6.0.6.1. If you are using CLM tools to track your requirements with CLM 6.0.6.1 (read System Requirements for the full list of supported versions and other requirements) you would be able to create “Derived From” links in your modeling tool e.g. HCL RTist from a model element to a requirement. These links will be visible in Design Room ONE after the model has been exported to the server. After that matching “Derives Architecture Element” links will be visible in your requirements management application and you would be able...
article-img
Secure DevOps  /  June 22, 2020
Developing IoT and Embedded Applications the Efficient Way
By: Nabeel Jaitapker, Product Marketing Lead, HCL Software
In order to gain a competitive advantage, companies need advanced tooling to support and scale their embedded and IoT applications with strategic uses of these model-based designs.Companies that adopt new technologies and are able to react to this data to enhance the customer experience, gain a significant edge on their competitors.
article-img
Secure DevOps  /  April 30, 2020
Design Room ONE Gets Authentication Improvements
By: Alexander Strabykin, Development Lead at HCL Software
During several last sprints, the Design Room ONE team has been working on various improvements and enhancements in Authentication functionality. The latest Design Room ONE 2.0 2020.16, which is a part of HCL RTist, brings multiple important updates. First, we simplified the installation and configuration procedure significantly by introducing Docker support. Now, with a fewer commands, users can get Keycloak, NodeJS, Mongo running and connected, watch the demo video or check the detailed instruction on GitHub to learn more. Second, authentication is no longer blocking running reports against models published on the Design Room ONE server; updated instructions cover the necessary configuration steps. Before running a report, a user needs to enable Basic authentication scheme in Design Room ONE server settings, and after that provide necessary credentials when configuring the Data Source in the reporting tool, as shown below.     Third, automated publishing scenarios, when for example a new version of the model gets published to server each time it is updated in the repository now also support authentication. Two new attributes user and password were introduced to specify the credentials to be used during automated publishing process. And finally, multiple improvements were made to publishing wizard. If the Allow insecure connection checkbox is checked, it will also permit communication with Keycloak server, even if its HTTPS certificate cannot be verified, this comes handy for example when the default self-signed certificate is used in Keycloak deployment. Another improvement can be observed when connecting to a Design Room ONE server takes noticeable time, e.g. because of network delays. Now users are notified on the operation being performed in the header section of the Export wizard window.   Stay up-to-date with all our releases and features by checking out our blog.
a/icon/common/search Created with Sketch.