Release notes for Genus 11.1

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.

See also the following notes.

#23647 Changes to Helm values regarding enabling of serviceMontiors and prometheusRules

The helm value global.servicemonior.enabled, which is used to disable deployment of serviceMonitors in cases where Prometheus is not running in the cluster, is moved to the following location, and is accompanied by a similar setting for disabling prometheusRules. Please note the capitalization of M in serviceMonitor.

global:
  metrics:
    serviceMonitor:
      enabled: true (default) | false
    prometheusRule:
      enabled: true (default) | false

This affectes both Genus 11.1 and Genus Operator 7.1.

#23658 Change in versioning strategy for Genus Opeartor

Starting with the version following 7.1 of Genus Operator, the version number will match the version number of Genus.

This means that the next version will be 11.2, and that version of Operator will work with the 11.2 version of Genus. In the future, all version numbers of Genus and Genus Operator will be 1:1.

The reason for this is that we are working on moving some functionality from Genus Studio to Genus Operator, and for this to work, the versions will be tightly coupled and will need to be upgraded at the same time.

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.

There is no deprecated functionality in this release.

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.

#23646 Helm values: "true" and "false" are now booleans instead of strings in some cases

In some cases where "true" and "false" helm values were strings, they are now booleans, meaning they must not be quoted.

The cases that will need to be updated are:

global:
  published: true|false
  enableSentry: true|false
  enabledDebugInformation: true|false
  reportSensitiveBreadcrumbsToSentry: true|false

#23653 The "On Active" button in input fields will no longer be disabled when the input field has no value

If the "On Activate" is connected to an input field, a button is added to the right of the input field, which can be clicked to run the action. Previously, this button was disabled when the field was empty. This decision should be made by the business engineer, not the platform. Therefore, this restriction has been removed.

#23655 Sign in history has been removed

Sign-in history functionality has been removed from the platform. The following action must be performed. All occurrences of Delete Effects that delete sign-in history must be removed.

Without performing the described step, the error message "Unhandled audit object storage. Id = 4627" will be displayed to the user/or logged.

#23657 Background color is no longer set when a component is embedded in a page

Earlier, all components had a background color set implicitly. This caused problems when a component was embedded in for instance a repeating containter where the background changes depending on state (for instance on hover) As a result of this change, some components may no longer have the expected background.

You need to change your components where a specific color is desired.

#23665 Default page på web

We can now define multiple page links to web pages on the Object Class and select one of them as default. The new page link also includes an app. The old definition witch only included a page is no longer available

Major new functionality

#23656 New features in the 4 chart controls:

  • Bar, Line, Area (formerly BarPlot)
    • BarPlot is now called Bar, Line, Area and is a dynamic chart control which supports charts of type Bar (Column), Line and Area.
    • Bar, Line Area, also supports multiple data series.
      • Show Average, Color Set and Type is moved into the data series edit (from the BarPlot control itself), so different data series can have different settings for color, average line and chart type.
    • Data series using different value axes is now supported.
    • Validation (in the designer) for multiple data series in Bar, Line, Area
    • Improved default values in the configs.
  • Categories (formerly Category axes)
    • The "Category axes" config is renamed to "Categories" and now supports chosing one of the created categories as active in the categories collection edit dialog. The chosen category wil be used for all data series in the control.
      • If no category is chosen as active, the first/top one is used.
  • Data Series
    • Increased the size of the data series collection edit dialog to reduce the need for scrolling to find all configs.
    • Add a label config to a data series. (Shown in the tooltip when hovering over a point in the chart)
  • PiePlot
    • Bug fixes for value labels, pie sizing and center label + center value
    • Fixed PiePlot crashing on load when Scatter or Box Plot simultaneously was being loaded.
    • Text in the center value or center label will now be cut off (ellipsis) if the rendered text length exceeds that of the pie's diameter of which the center label and value is in.
    • Pie as default over Doughnut
  • Other
    • The four chart controls are organized as their own section in the controls list in the page designer.
    • Tests, bug fixes for all chart controls

Minor new functionality

#23645 Core-service now has 2 replicas and PDB enabled as default

As of 11.1.0.alpha.5, the core service runs two replicas as default, when in a published runtime. Additionally, PodDisruptionBudged (PDB) is enabled as default, specifying that at least 1 instance of the core-service should be available at all times.

This should help prevent downtime in instances where Kubernetes reschedules the core-service pod to a different node.

It is important to note that when using PDB to specify minAvailable pods, there must be more than that minimum number of pods running. If that is not the case, the PDB will prevent nodes from draining, and potentially preventing Kubernetes from scaling the cluster properly.

#23649 Default LANG for core-service

Default LANG is now set to nb_NO.UTF-8 in the core-service (and rest-soap-service, data-mart-query-service, scheduled-action-service and mq-subscriber-service).

This should help with any .toUpper()-issues for Norwegian characters, and correctly sort names starting with AA.

This setting can be overridden by setting the global.lang helm-value.

#23650 Simplified Redis configuration

We have redesigned how we use Redis for storing live update messages, trace log messages and -level and a couple of other properties. This means that the Redis instance in the origin, green and blue environments are no longer used, and is therefore removed.

This should result in lower infrastructure cost, and better persistance for the properties mentioned above.

#23652 Identityprovider type MS Entra ID now supports samAccountName as account id property

MS Entra ID (previously known as Azure AD) now supports samAccountName as account id property in addition to upn. To use samAccountName one must add a new ClaimsMappingPolicy in Azure on the Authenticator app registration and set the property acceptMappedClaims to true in the app registration manifest. Any other account id property value than samAccountName will fallback to upn.

#23664 Trigger Server Action from Desktop

It is now possible to trigger a Server Action to run on the server from Desktop. This is done using the Run an Action effect and selecting the Run on Server checkbox in the effect dialog.

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.

Change log