RTist models are stored in XML files (.emx and .efx). If you have ever opened such a file in a text editor you have probably noticed that code snippets stored in the model can be quite difficult to read due to the encoding of certain characters that is mandated by XML. Here is an example:     Some code snippets are stored as attributes in XML and they can look even worse, since newlines also will be encoded so that the whole code snippet appears on a single line:     Starting with RTist 11.0 2020.33 it's now possible to set a preference so that code snippets will be saved in CDATA sections in the XML file. Thereby the code does not need to be escaped which greatly improves its readability. The preference is called Use CDATA when saving model files and is located on the Modeling preference page. In addition to code snippets, it also affects how documentation texts are stored.     After setting this preference, the code snippets in the examples above will look like this:       Note that older versions of RTist can still read model files that use CDATA. In that sense this feature is backwards compatible. Note, however, that if you edit and save the model in such an old tool version the code snippets will once again be stored without usage of CDATA.  If you decide to start using CDATA in your model files it can be a bit tedious to manually re-save all files in the workspace to use the new format. To simplify you can run a model fixup which will automatically convert all your model files to use CDATA.     Watch this video for more information.

As a result of our Sprint 2021.04, there are now two deliveries available for download: HCL RTist 11.0 2021.04 and experimental version 11.1 2021.04. Although the experimental version is not yet recommended for production use, we would greatly value any feedback you may have on it. Feel free to reach out to the development team. For now, let’s take a look at what’s new: Single-command Scripted Installation Installation of HCL RTist has never been easier! Just download the script from this page in Utilities section and after a simple configuration, given a product zip file it will automatically download corresponding Eclipse version and depending on RTist version being installed will perform all necessary configuration and installation steps to get you going in minutes. Visualization of Event Routing Complex UML RT models often have many levels of nested capsules, making it difficult to analyze how events are travelling through these structures. In Sprint 2021.04 HCL RTist provides experimental Event Routing Visualization feature, which generates a read-only view of all possible communication paths and relevant parts with respect to a certain port. Despite the new view cannot be used to change the model, you can pan and zoom the diagram, filter to only show paths for In or Out events and switch root capsule context with "Go Inside" and "Go Outside" commands. Please keep in mind that to try this feature you should first activate it in Experimental Features Preferences page. Simpler Qualified Names In many places in RTist like e.g. Properties view you could see fully qualified names of UML elements. Qualified Name of an element includes names of all owning model elements up to the model's root separated by ::. However Capsule Development viewpoint simplifies model representation by hiding some types of elements in Project Explorer view, for example Regions in statemachines. Starting from Sprint 2021.04 fully qualified...

A new version of RTist 11, 2020.50, is now ready to be downloaded. Let's take a look at some of the improvements implemented in the 2020.50 release.

The latest HCL RTist 11 release, version 2020.45, is now available. And there are several improvements and new features in this release:

The latest Design Room ONE delivery may not have too many user interfaces changes, but under the hood it is powered by the latest version of Node.js.Node.js version 14 has an updated Javascript V8 engine. So, its adoption has resulted in a faster, better, more stable and secure server.

UML-RT models within HCL RTist can now be examined from different perspectives.Take for example, the third-party extension MetaModelAgent from Adocus.

The latest HCL RTist 11 release, version 2020.39, is now available. And there are several improvements and new features in this release.

HCL RTist is an Eclipse-based modeling and development environment for creating complex, event-driven, real-time applications in C++.

HCL RTist 11 2020.33 is now available with several improvements in various areas.

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...