Release notes for Genus 11.3

Introduction

This document lists all user-visible changes to Genus since the previous release.

This release note will be updated prior to the release and may also be updated as long as the release is available, e.g. with information of new patches or known issues. Please take note of the installation and upgrading comments, and the release notes change log.

Installation and upgrading

Prior to upgrading to this release, you must:

Upgrade to the previous release. See the Release notes for the previous release for more information.
Review the Expiry date of your Genus License File and install a new one if necessary.
Review the rest of the release notes for this release.
Please note that there does not exist any Genus Upgrade Assistant for this upgrade.

End-of-life functionality

End-of-life functionality is functionality that was available in the previous release, but is no longer available in this release.

There are no end-of-life functionality identified in this release.

Deprecated functionality

Deprecated functionality is available in this release, but will (most probably) no longer be available in the next release.

#23672 Rerun -functionality for rest and soap services will be removed

The Consume a Web Service and Consume a Rest Service effects both have a Rerun Attempts functionality. This functionality does not provide the desired functionality, thus it will be removed in release 11.3. The functionality can normally be modelled with a Descicion - or While block.

Breaking changes

This section lists important changes introduced in this release. You will need to use this list in order to understand the changes you might need to make to your application to support the new release.

#23673 Breaking change in Pie Plot and Bar, Line, Area (Bar Plot)

The setup and meta model for these two chart controls is now altered in a way leading to a breaking change. The controls will need re-modelling.

Short version:

The business engineer now needs to set a MANDATORY category, by choosing an object reference field from the main data binding of the control/data series. This effectively removes auto categories, i.e. there being a 1-1 relationship between a category and an object/data row in the main data binding. (Automatic generation of the categories).

Longer version:

Pie Plot:

Previously, one could use auto categories by having each "pie" in the chart originating from an object in the data binding. Now, after choosing a data binding, the business engineer has to choose a category object reference from a drop down (whose options are generated from the different reference fields available on the object class of the data binding).

The business engineer then must choose one of two options for the categories: Specified in data set or Derived from data.

If Specified in data set is chosen, a data set of the same data source type must be chosen. The "pies" in the chart will then correspond 1-1 to objects in the chosen data set. Even if no object from the main data binding "points" to the category, the category will still be present in the pie, legend, and value labels, as an "empty pie".

If Derived from data is chosen, no data set needs to be chosen. The only categories (pies) which will appear will be the ones referenced as field values from objects in the main data binding.

Another new config in the pie plot is the Data may contain duplicates per category switch. If enabled, the business engineer must choose a local aggregation method (sum, min or max) for handling the mapping of duplicate value objects into a single category. If disabled, and duplicates still occur in the runtime data, the pie plot will be replaced by an inline error message box. (Duplicates in the data prevents the use of functionality for exploring the source data of an Aggregate Object Class.)

Bar, Line, Area:

The changes in this control are similar but distributed in the category edit and data series edit modal.

As presently, the business engineer defines categories, value axes and data series separately in each their own modal. Choosing a category composition, category data set vs. derived categories and potentially a category data set is done in the category configuration. Allowing duplicate data per category and potentially a local aggregation method is done in the data series configuration.

Choosing a category field in each data series is now mandatory, rather than only required when a non-auto category was chosen as the axis category.

Remark:

The data set in context in the page designer will be affected by the categories being derived or not, and whether the control/data series allows duplicate data entries per category.

Selection is also affected by the same two parameters.

Major new functionality

There are no major new functionality in this release.

Minor new functionality

There are no minor new functionality in this release.

Resolved issues

There are no resolved issues in this release.

Known issues

Known issues are errors or lack of functionality. Known issues may be solved in a future release based on customer demand.

There are no known issues in this release.

Tips and hints

Tips and hints are design decisions or answers to support questions that may be of general interest.

There are no tips and hints specifically targeting this release.