AppLocker compliance

In order to comply with Win10 AppLocker, the structure of the Rhapsody installation has been modified to separate executable files from Rhapsody files that require read/write access.

The Rhapsody folders affected by this change include the sample, property, and profile folders. As a result of these changes:

• The site.prp file is now located in \UserShare\Properties.
• If you want the New Project dialog to include profiles that you have created or out-of-the-box profiles that you have modified, you must put them in \UserShare\Profiles.

Depending on the options that you selected during the installation of Rhapsody (data file location, install all files in one location), the UserShare folder can be found under: <Rhapsody installation directory>, C:\Users\<username>\IBM\Rhapsody, or C:\ProgramData\IBM\Rhapsody.

Code generation: building of Rhapsody framework files

The installation wizard now allows you to specify the path where the Rhapsody framework files should be built. If you need to modify this path after Rhapsody is installed, you can change the value of FRAMEWORK_LIB_ROOT in the General section of the rhapsody.ini file or change the value of the property CG::Configuration::FrameworkLibRoot.

Code generation: support for MinGW compiler

For C and C++ models, the list of available environments now includes an entry for MinGW.

Code-signing for binaries

Additional Rhapsody binaries (including the installation executable) are now digitally signed.

Command-line interface: open model as read-only

The "open" command now has a "readonly" parameter, which can be used if you want to open a model as read-only. The syntax for this option is: -cmd=open <path to the .rpyx file> readonly

Configuration Management: integration with ClearCase

Rhapsody's integration with ClearCase can now be used with ClearCase 9.x

Diagrams: information displayed for attributes in compartments

It is now possible to control what information is displayed for attributes when they are shown in a compartment of a graphic element. This applies also to "new terms" that are based on attributes, such as flow properties. To customize the information displayed, modify the values of the following new properties: ObjectModelGe::Attribute::CompartmentDisplayFormat and StructureDiagram::Attribute::CompartmentDisplayFormat. These properties support the following keywords: DirectedFeatureDirection, Name, Multiplicity, FlowPropertyDirection, Type, DefaultValue.

Diagrams: new "Expand/shrink to fit text" option

Now, in addition to the "Expand to fit text" option, diagram elements have an "Expand/shrink to fit text" option, which can be used to both expand and shrink the selected elements as required.

Helpers and plugins: maximum number of helpers and plugins

Rhapsody can now load up to 1000 helpers and up to 500 plugins.

Modeling: prevention of unresolved elements

The property General::Model::DisableIgnoreReadOnlyFilesOption is now True by default. This reduces the likelihood of a user introducing unresolved elements into a model.

Performing EWM actions from within Rhapsody: accepting incoming changes

When using the integration with EWM (Engineering Workflow Management), it is now possible to accept incoming changes from within Rhapsody. In addition, the icon mechanism that is used to indicate the CM status of Rhapsody units has been enhanced so that the status indications are propagated upward to the parent unit and onward up to the project level. For example, if a package contains a class with incoming changes, the icon of the package also has the incoming arrow added to it. If you don't want unit status to be propagated upward, you can turn off the feature by changing the value of the property ShowCMStatusOfSubUnits.

Ports: interface selection

When selecting a provided interface for a port, the list of available interfaces now starts with the required interface of the port that the first port is connected to. Similarly, when selecting a required interface, the list starts with the provided interface of the connected port.

Property help files for custom properties

A new property called AdditionalPropHelpLocation has been added (under Model::Profile). If you want to write help files for custom properties that you have added, you can use this property to specify a folder where Rhapsody should look for custom property help files. The format of any such custom help files should be the same as that used in the files in the ..\Doc\PropertyHelp folder. The folder hierarchy in the additional location should also be the same as that used for the different languages in the ..\Doc\PropertyHelp folder. For example, if you are adding English help files, the .xml files should be put in the folder <custom property help location>\PropertyHelp\EN\.

RTOS support: WindRiver VxWorks 7 (Workbench 4)

Rhapsody can now be used with WindRiver VxWorks 7 (with Workbench 4).

Reporting: generation of HTML model reports with Engineering Publishing (formerly Rational Publishing Engine)

Enhancements have been made to the generation of HTML documents, using an auto-generated Engineering Publishing template, including: use of element icons in the report browser, navigation from diagrams to model elements, support for reporting on Java models, and improvements in the structure and appearance of the reports.

SysML: code-generation support for proxy ports with multiplicity greater than 1

In SysML models, Rhapsody can now generate code for proxy ports that have multiplicity set to a value greater than 1 (C++ only).

SysML: new perspective - Getting-Started

If you create a new SysML project, and enable perspectives, the default perspective is now the Getting-Started perspective, which was added in this release. This perspective makes Rhapsody more accessible to new users, and simplifies the user interface by hiding options that such users are unlikely to need.

User Interface: product renaming changes

The relevant parts of the Rhapsody user interface have been modified to reflect the changes made to the names of the individual programs that make up the IBM Engineering Lifecycle Management family.

User Interface: use of new combo box for filtering

Additional dialogs now use the combo box that dynamically filters list elements as you type, which was introduced in an earlier release.

Back to top