4. Release Notes¶
4.1. Supported Platforms and Browsers¶
System Designer 7.0.0 is compatible with Connext 7.0.0.
See the System Designer column in the Table of Supported Platforms for Connext Applications, in the Core Libraries Release Notes.
System Designer works with these browsers:
Chrome version 77
Firefox version 69
Safari version 12
4.2. Compatibility¶
For backward compatibility issues between the current and previous releases of System Designer, see the Migration Guide on the RTI Community Portal (https://community.rti.com/documentation).
4.3. What’s New in 7.0.0¶
4.3.1. Support for the DISCOVERY logging category¶
System Designer now supports the DISCOVERY logging category.
4.3.2. New field to configure Domain tag when defining Participant QoS¶
A new field has been added to easily configure the Domain Tag when defining a Participant QoS:
The Domain Tag can also be configured as a regular property,
dds.domain_participant.domain_tag. In this case, System Designer will
automatically show the Domain Tag value in the new field.
The new field will also indicate if the Domain Tag has been inherited from a base QoS.
4.3.3. Improvements to .rtisdproj file to be human-readable and contain more metadata¶
The System Designer .rtisdproj file has been changed to a human-readable JSON format,
instead of a single-line string.
The .rtisdproj file now contains these additional properties:
The original creation date of the project.
The version of System Designer used to create the project.
The Project Properties pane has been updated to display these properties.
4.3.4. New field to configure Partition QoS when defining a DomainParticipant¶
A new field allows you to configure the Partition QoS policy when defining a DomainParticipant’s QoS.
4.3.5. QoS snippets can now be composed of other QoS snippets¶
When creating QoS Snippets, now they can be composed of other QoS Snippets.
4.3.6. Automatic validation of XML files when opening a project or adding XML files to a project¶
System Designer now automatically validates all the XML files when opening an existing project, and when adding an XML file to a project. You can disable this validation in the Advanced Project Properties dialog.
4.3.7. Improved usability of Representation QoS Policy editor¶
The Representation QoS Policy editor has been improved by adding a suggestion list with the following values:
AUTO_DATA_REPRESENTATION
XML_DATA_REPRESENTATION
XCDR_DATA_REPRESENTATION
XCDR2_DATA_REPRESENTATION
4.3.8. Updated Shared Secret Algorithm field in Configure Security dialog¶
The “Shared Secret Algorithm” field in the Configure Security dialog for a Participant QoS has been renamed to “Key Establishment Algorithm”.
New algorithms have been added and existing algorithms have been renamed:
auto
ECDHE-CEUM+P384 (Elliptic Curve Diffie-Hellman p384)
Diffie-Hellman (DH) has been renamed to “DHE+MODP-2048-256”
Elliptic Curve Diffie-Hellman (ECDH) has been renamed to “ECDHE-CEUM+P256”
4.3.9. New security properties in Global Security settings¶
The “Configure Security” dialog for a Participant QoS has been updated. The following fields have been added to the Participant Trust tab in the “Global Security Settings” dialog to configure new Security properties:
Maximum Key Redistribution Delay in seconds
Maximum Key Revision History Depth
4.4. What’s Fixed in 7.0.0¶
4.4.1. Unsupported QoS elements and policies appeared in Configuration¶
The following elements have been removed from System Designer, since they are not supported:
table_allocation_block_size from DDSDatabaseQosPolicy
writer_depth from DDSDurabilityServiceQosPolicy
multi_channel from DDSDatareaderQosProfile
assertions_per_lease_duration from DDSLivelinessQosPolicy only for DataReader and Topic QoS
cpu_list from thread only for Event and Database QoS
cpu_rotation from thread only for Event and Database QoS
address_bit_count
[RTI Issue ID SYSD-936]
4.4.2. Unconfigurable QoS XML elements and policies appeared in Configuration¶
The following elements have been removed from System Designer, since they are not configurable through XML:
Participant QoS:
discovery_config.asynchronous_publisher.thread.cpu_list
discovery_config.asynchronous_publisher.thread.cpu_rotation
discovery_config.asynchronous_publisher.disable_asynchronous_batch
discovery_config.asynchronous_publisher.asynchronous_batch_thread
discovery_config.asynchronous_publisher.disable_topic_query_publication
discovery_config.asynchronous_publisher.topic_query_publication_thread
discovery_config.publication_reader.min_app_ack_response_keep_duration
discovery_config.subscription_reader.min_app_ack_response_keep_duration
Publisher QoS:
asynchronous_publisher.thread.cpu_list
asynchronous_publisher.thread.cpu_rotation
asynchronous_publisher.asynchronous_batch_thread.cpu_list
asynchronous_publisher.asynchronous_batch_thread.cpu_rotation
asynchronous_publisher.topic_query_publication_thread.cpu_list
asynchronous_publisher.topic_query_publication_thread.cpu_rotation
presentation.drop_incomplete_coherent_set
DataReader QoS:
representation.compression_settings.writer_compression_level
representation.compression_settings.writer_compression_threshold
Topic QoS:
durability.writer_depth
[RTI Issue ID SYSD-950]
4.4.3. Renamed items were not updated in System Designer’s UI¶
References to items were not updated in System Designer after the item was renamed. This caused System Designer to generate an invalid configuration file. This problem has been resolved. Now System Designer will automatically update all references to the renamed item.
[RTI Issue ID SYSD-975]
4.4.4. Incomplete error messages when importing an XML file in some web browsers¶
When importing an XML file, any error messages reported by System Designer were incomplete in some web browsers. This problem has been resolved. Now System Designer will report the cause of the error if there is a problem importing an XML file.
[RTI Issue ID SYSD-978]
4.4.5. Deleting project files from disk may have left some empty directories¶
Deleting project files from disk may have left some empty directories. This occurred if any of the XML files in the project were in a different directory than the project file. This problem has been resolved.
[RTI Issue ID SYSD-984]
4.4.6. System Designer incorrectly allowed XML and IDL to be edited in XML and IDL views¶
System Designer incorrectly allowed the XML and IDL to be edited in the XML and IDL view. These changes were not reflected in the structured view. This problem has been resolved. Editing the XML directly can only be done by clicking on the Edit XML button.
[RTI Issue ID SYSD-989]
4.4.7. Discrepancy between range defined by System Designer and by API for certain elements¶
For certain elements, the range defined by System Designer did not match the range defined by the API. This problem has been resolved. Now, values that are supported by the API but not System Designer, will not appear as an error in System Designer, and vice versa.
[RTI Issue ID SYSD-998]
4.4.8. System Designer unable to edit Domain after detecting invalid Domain ID¶
If you entered an invalid Domain ID when creating a Domain, System Designer reported an error, such as “Invalid domain id”. Then System Designer would not allow you to further edit that domain and logged another error, such as “Domain name already used.” This problem has been resolved.
[RTI Issue ID SYSD-1000]
4.4.9. IDL and XML text editors appeared empty on network-isolated system¶
On a network-isolated system, System Designer failed to populate the IDL and XML text editors with their content; the editors appeared empty. This problem has been resolved.
[RTI Issue ID SYSD-1003]
4.4.10. System Designer failed to import multiple XML files¶
System Designer was unable to import multiple XML files. This problem has been resolved. The second window that System Designer displays after a file is selected has been updated to list the XML files that you are trying to import.
[RTI Issue ID SYSD-1009]
4.4.11. Unable to add default case to Union member when adding more than one case value¶
The default case could not be added to a Union member when adding more than one case value. This problem has been resolved. Now you can enter the default case when adding more than one case value.
[RTI Issue ID SYSD-1011]
4.4.12. Types tab did not show #include directives from XML file¶
System Designer’s Types tab did not display any #include directives found in the XML file. This problem has been resolved. Now System Designer will display any #include directives from the XML file in the Types Tab.
[RTI Issue ID SYSD-1012]
4.4.13. Unable to move an element up or down in Types tab, in some cases¶
Moving an element up or down in the Types tab did not work in in some cases.
For instance, suppose you wanted to move an element we’ll call “E”. It could not be moved if:
Another element, above or below E, was not available to be moved due to its DomainParticipant-level Partition.
Another element, above or below E, had a member with the same name as E.
The name of another element, above or below E, was the same as one of E’s members.
This problem has been resolved. Now System Designer will move the elements up or down as requested, even in the above scenarios.
[RTI Issue IDs SYSD-1016, SYSD-1018]
4.4.14. Failure in Types tab when trying to add module with same name as another¶
When defining a module in the Types tab, System Designer failed when trying to add a module with the same name as another module that was defined in a read-only file. This problem has been resolved (as shown in the screen capture below).
[RTI Issue ID SYSD-1017]
4.4.15. Could not create new file in Types tab if project contained read-only file¶
System Designer could not create a new file in the Types tab if the project contained a read-only file. This problem has been resolved.
[RTI Issue ID SYSD-1022]
4.5. Known Issues¶
Note
For an updated list of critical known issues, see the Critical Issues List on the RTI Customer Portal at https://support.rti.com/.
4.5.1. Modules defined in multiple files, with different annotations¶
Modules can be defined in multiple files, and each file might define the module with different annotations:
@autoid
@transfer_mode
@language_binding
@allowed_data_representation
Semantically, those annotations (when defined in a module) apply only to the contained entities. Since internally modules are identified by a single object, when their definition comes from multiple files, their annotations must be the same.
4.5.2. System Designer fails to create a string/wstring constant¶
System Designer fails to create a string/wstring constant, with the following error:
Value does not match constant type.