.. include:: vars.rst .. _section-release-notes: Release Notes ============= .. _section-release-notes-supported: Supported Platforms and Browsers -------------------------------- |SD| |SD_VERSION| is compatible with *Connext* |CONNEXT_VERSION|. See the |SD| column in the :link_connext_dds_pro_rn:`Table of Supported Platforms for Connext Applications, in the Core Libraries Release Notes <#release_notes/PAMtable.htm#PAM_AppsNotCompiled>`. |SD| works with these browsers: - Chrome version 77 - Firefox version 69 - Safari version 12 Compatibility ------------- For backward compatibility issues between the current and previous releases of |SD|, see the Migration Guide on the RTI Community Portal (https://community.rti.com/documentation). .. _section-release-notes-new: What's New in 7.0.0 ------------------- Support for the DISCOVERY logging category ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ .. SYSD-905 |SD| now supports the DISCOVERY logging category. New field to configure Domain tag when defining Participant QoS ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ .. SYSD-909 A new field has been added to easily configure the Domain Tag when defining a Participant QoS: .. figure:: static/SYSD-909-screenshot1.png :alt: New field for Domain Tag :name: Figure_new_field_Domain_Tag :align: center :figwidth: 100% The Domain Tag can also be configured as a regular property, ``dds.domain_participant.domain_tag``. In this case, |SD| will automatically show the Domain Tag value in the new field. .. figure:: static/SYSD-909-screenshot2.png :alt: New field for Domain Tag filled in :name: Figure_new_field_Domain_Tag_filled_in :align: center :figwidth: 100% The new field will also indicate if the Domain Tag has been inherited from a base QoS. .. figure:: static/SYSD-909-screenshot3.png :alt: New field for Domain Tag inherited :name: Figure_new_field_Domain_Tag_inherited :align: center :figwidth: 100% Improvements to .rtisdproj file to be human-readable and contain more metadata ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ .. SYSD-912 The |SD| ``.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. New field to configure Partition QoS when defining a DomainParticipant ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ .. SYSD-916 A new field allows you to configure the Partition QoS policy when defining a DomainParticipant's QoS. .. figure:: static/SYSD-916-releasenote-screenshot.png :alt: New field for DomainParticipant level Partition :name: Figure_new_field_DomainParticipant_Partition :align: center :figwidth: 100% QoS snippets can now be composed of other QoS snippets ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ .. SYSD-918 When creating QoS Snippets, now they can be composed of other QoS Snippets. Automatic validation of XML files when opening a project or adding XML files to a project ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ .. SYSD-931 |SD| 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. .. figure:: static/SYSD-931-validation-property-dialog.png :alt: Disabling auto-validation of XML files :name: Figure_disable_validation_XML_files :align: center :figwidth: 100% Improved usability of Representation QoS Policy editor ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ .. SYSD-947 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 Updated Shared Secret Algorithm field in Configure Security dialog ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ .. SYSD-1014 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” .. figure:: static/SYSD-1014-key-estab-algorithms.png :alt: Available Key Establishment Algorithms :name: Figure_available-key-establishment-algorithms :align: center :figwidth: 100% New security properties in Global Security settings ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ .. SYSD-1026 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 .. _section-third-party-software-upgrades: Third-party software upgrades ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ .. SYSD-1027 The following third-party software used by |SD| has been upgraded: .. list-table:: Third-Party Software Changes :name: Table_ThirdPartyChanges :widths: 30 30 40 :header-rows: 1 * - Third-Party Software - Previous Version - Current Version * - nodejs® - 10.24.1 - 16.15.1 * - express-fileupload - 1.2.1 - 1.4.0 .. _section-release-notes-fixed: What's Fixed in 7.0.0 --------------------- Unsupported QoS elements and policies appeared in Configuration ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ The following elements have been removed from |SD|, 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] Unconfigurable QoS XML elements and policies appeared in Configuration ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ The following elements have been removed from |SD|, 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] Renamed items were not updated in System Designer's UI ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ References to items were not updated in |SD| after the item was renamed. This caused |SD| to generate an invalid configuration file. This problem has been resolved. Now |SD| will automatically update all references to the renamed item. [RTI Issue ID SYSD-975] Incomplete error messages when importing an XML file in some web browsers ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ When importing an XML file, any error messages reported by |SD| were incomplete in some web browsers. This problem has been resolved. Now |SD| will report the cause of the error if there is a problem importing an XML file. [RTI Issue ID SYSD-978] 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] System Designer incorrectly allowed XML and IDL to be edited in XML and IDL views ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ |SD| 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] Discrepancy between range defined by System Designer and by API for certain elements ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ For certain elements, the range defined by |SD| did not match the range defined by the API. This problem has been resolved. Now, values that are supported by the API but not |SD|, will not appear as an error in |SD|, and vice versa. [RTI Issue ID SYSD-998] System Designer unable to edit Domain after detecting invalid Domain ID ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ If you entered an invalid Domain ID when creating a Domain, |SD| reported an error, such as "Invalid domain id". Then |SD| 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] IDL and XML text editors appeared empty on network-isolated system ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ On a network-isolated system, |SD| 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] System Designer failed to import multiple XML files ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ |SD| was unable to import multiple XML files. This problem has been resolved. The second window that |SD| displays after a file is selected has been updated to list the XML files that you are trying to import. .. figure:: static/select_file_to_import.png :alt: Selecting which file to import :name: Figure_select_file_to_import :align: center :figwidth: 100% [RTI Issue ID SYSD-1009] 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. .. figure:: static/SYSD-1011-default-case.png :alt: Entering a default case for a union member :name: Figure_enter_default_union_case :align: center :figwidth: 100% [RTI Issue ID SYSD-1011] Types tab did not show #include directives from XML file ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ |SD|'s Types tab did not display any #include directives found in the XML file. This problem has been resolved. Now |SD| will display any #include directives from the XML file in the Types Tab. .. figure:: static/SYSD-1012-display-includes.png :alt: #includes appear under types :name: Figure_display_include_directives :align: center :figwidth: 100% [RTI Issue ID SYSD-1012] 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. .. figure:: static/SYSD-1018-cannot-move-up-down.png :alt: Unable to move element up or down :name: Figure_unable_to_move_element :align: center :figwidth: 100% This problem has been resolved. Now |SD| will move the elements up or down as requested, even in the above scenarios. [RTI Issue IDs SYSD-1016, SYSD-1018] 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). .. figure:: static/SYSD-1017-add-module.png :alt: Now can add module with same name :name: Figure_add_module :align: center :figwidth: 100% [RTI Issue ID SYSD-1017] Could not create new file in Types tab if project contained read-only file ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ |SD| 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] Fixes related to vulnerabilities ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ This release fixes some potential vulnerabilities, descrbed below. Potential crash when receiving a modified form `````````````````````````````````````````````` |SD| had a third-party dependency on express-fileupload version 1.2.1. This version had a dependency on dicer, which is known to be affected by a number of publicly disclosed vulnerabilities. These vulnerabilities have been fixed by upgrading express-fileupload to the latest stable version, 1.4.0. See :ref:`section-third-party-software-upgrades`. For |SD|, the impact of using express-fileupload 1.2.1 was: * Exploitable through a modified form * |SD| could crash upon receiving the modified form. A complete denial of service can be achieved by sending the malicious form in a loop. * CVSS v3.1 Score: 7.5 HIGH * CVSS v3.1 Vector: AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H [RTI Issue ID SYSD-1029] 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/. 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. System Designer fails to create a string/wstring constant ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ *System Designer* fails to create a string/wstring constant, with the following error: .. code-block:: text Value does not match constant type.