Release notes for Genus 11.6

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.

#23707 BREAKING CHANGE: Discontinuing support for Helm 2 charts. Switch to using Helm 3/oci charts.

The Azure container registry containing our Helm charts and container images are dropping support for Helm 2 charts. Genus have supported Helm 3 since version 10.22, and we will stop publishing Helm 2 charts after version 10.5.

To switch over from deploying the old charts to the new charts, some changes must be done to the deploy pipelines or GitOps (Flux or ArgoCD) configuration.

If you are deploying with pipelines, make sure that the pipeline job run on version 2.6.5 or newer of the genusbiz/genus-bootstrap image.

If you are deploying with Flux or ArgoCD, make sure that the HelmRepository definition is of type: "oci", and that the url is "oci://genus.azurecr.io/genus/helm".

More information about the change can be found here.

#23708 Helm value validation when deploying Genus versions

The Helm values will now be validated before deploying, and attempting to deploy with invalid values will no longer work (unless the flag --skip-schema-validation is set).

Validation errors are displayed in the deploy log, or can be found using Version Deployment in Genus Operator.

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.

#23717 Table Naming Method is no longer in use

Table Naming Method was a feature used to concatenate the Data Partition identifier to a Provider Name on a table to simulate what would today be solved by using schemas.

#23721 Delete unused privilege: Log in as a SOAP user

This privilege is not in use. The permissions to a SOAP service is specified at each endpoint.

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.

#23710 Service "message-subscription-service" renamed

Any Helm values for message-subscription-service defined under genus-message-subscription-service, must be moved to genus-live-update-subscription-service

For example if you have the following in the Helm value files:

genus-message-subscription-service:
  resources:
    requests: 
      memory: 200Mi

It should now look like this:

genus-live-update-subscription-service:
  resources:
    requests: 
      memory: 200Mi

#23714 Service "rest-soap-service" renamed

Any Helm values for rest-soap-service defined under genus-rest-soap-service, must be moved to genus-exposed-web-service

For example if you have the following in the Helm value files:

genus-rest-soap-service:
  resources:
    requests: 
      memory: 200Mi

It should now look like this:

genus-exposed-web-service:
  resources:
    requests: 
      memory: 200Mi

#23715 Default value for repository.image for core-services now default to Linux only

Previously the default value for image.repository for core-services depended on wether or not runOnWindows was true. This is no longer the case.

This means that if you have set runOnWindows to true, you must now also specify the image.repository value. The value here should be either "genus.azurecr.io/genus/images/core-service-ltsc2019" or "genus.azurecr.io/genus/images/core-service-ltsc2022", depending on the Windows version of your Windows nodes.

This concerns the microservices genus-core-service, genus-mq-subscriber-service, genus-exposed-web-service, genus-scheduled-action-service and genus-data-mart-service.

An example: If you previously had

genus-core-service:
  runOnWindows: true

You must now have

genus-core-service: 
  runOnWindows: true
  image:
     repository: genus.azurecr.io/genus/images/core-service-ltsc2019

#23716 Service "trace-input-service" renamed

Any Helm values for trace-input-service defined under genus-trace-input-service, must be moved to genus-tracelog-input-service

For example if you have the following in the Helm value files:

genus-trace-input-service:
  resources:
    requests: 
      memory: 200Mi

It should now look like this:

genus-tracelog-input-service:
  resources:
    requests: 
      memory: 200Mi

#23719 Updated Button Colors in Genus

Button colors generated from user-defined palettes have been slightly adjusted to better align with common standards. This fix ensures more consistent and expected color behavior across button states.

What You Need to Know:

  • Improved Accuracy: Button colors now match the expected design standards more closely.
  • Affected States: Minor visual differences may appear in button states such as hover, pressed, disabled, and others.
  • Customized Styles Unchanged: If you have manually set button colors for a state, no action is required.

#23720 Change path for mounting certificates in microservices

If mounting any certificates in the services mentioned below, the path must be changed from /home/appuser/certificates/ to /opt/genus/certificates/ (or fromC:\home\appuser\certificates` to C:\opt\genus\certificates\for Windows containers).

This change affects the core-service, mq-subscriber-service, exposed-web-service, scheduled-action-service and data-mart-query-service.

Major new functionality

#23718 Pod scaling improvements in Genus Operator

We have made several scaling-related improvements in this release.

  • We have added new Helm values disableOperatorScaling (per microservice) and global.disableOperatorScaling. Setting this to true will cause the provided replicaCount to always be used, and no scaling will be done by Genus Operator. This includes scaling down outside of availability windows, so use this option with caution.
  • Unless the Helm value described above is set to true, we no longer set the replicas property of the Kubernetes deployments. This means that deploying new Genus versions will no longer cause immediate up-and-down scaling of the various microservices.
  • The default number of pod replicas has been adjusted. This means that if you have made no changes to replicaCount or scaled from Genus Operator, there will be 2 replicas running for the microservices that are critical for not perceiving downtime on the web. This should make deployments and other interruptions less noticeable to the end users. The Helm value global.highAvailability can be set for a runtime to cause all microservices to run with 2 replicas by default.
  • It is now possible to enable and configure autoscaling in Genus Operator. This means it is no longer necessary to redeploy the runtime to turn this on or off.
  • Genus Operator will now automatically create and delete Pod Disruption Budgets (PDBs) depending on the number of replicas that are running. This should also help with minimizing the impact of interruptions and deployments of runtimes.

Minor new functionality

#23701 Effect "Download Tables as Excel File"

A new effect has been added to "On Activate," replicating the table component's built-in Excel download functionality. This feature is now externalized, allowing you to connect it to any desired table

#23702 Conditional Expanded and Fullscreen for containers

  • Conditional Expanded for Control
    • A new field named Expanded has been introduced under the "General" section of the container. This enables conditional expansion or collapse of a container based on an expression. When this field is used, the standard collapse toggle in the header is disabled, and the container's state is determined exclusively by this field.
  • Conditional Full Screen for Control
    • A new field named Fullscreen has been added under the "General" section of the container. This allows you to conditionally toggle fullscreen mode for a container based on an expression. When this field is used, the standard fullscreen toggle in the header is disabled, and the container's state is controlled by this field instead.

#23703 Effect "Change Color Scheme"

A new effect has been added to "On Activate," allowing you to switch the color scheme (Light Mode, Dark Mode, or Browser Default) when triggered.

#23704 Effect: "Show History"

A new effect has been added to "On Activate," extending the built-in Show History functionality found in the app bar and context menu. This effect lets you select a specific dataset to connect, displaying only datasets where auditing is enabled.

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