What's New in 21.0.3

This section provides information about the new features and enhancements that have been implemented in Automic Automation 21.0.3.

This page includes the following:

Agents

This release includes features and functions for the agents listed below.

Agent for Google Cloud Composer

This release introduces the Agent for Google Cloud Composer Agent. This Agent establishes the connection between the Automation Engine and the Google Cloud Composer on which your Airflow DAG jobs run. The Agent starts the execution of these jobs and makes both their monitoring and the corresponding reporting possible.

For more information, see:

RA Avaloq

The Avaloq Agent implements an interface between Automic System and an Avaloq system. With the Avaloq Agent, Automic System can orchestrate both internal and external Avaloq jobs. For more information, see The Avaloq Agent.

Automic Automation Kubernetes Edition

This release of Automic Automation Kubernetes Edition introduces the features and functions listed below.

Resource Limits for Customization Pods

You can use the values.yaml file to define resource limits for customization pods. For more information, see Sizing of Automic Automation Kubernetes Edition.

If the resource limits are not defined, Kubernetes deploys the customization pods with the quality of service (QoS) BestEffort. For more information on QoS please refer to the official Kubernetes documentation.

Improved Tracing/Debugging Capabilities of AAKE

Now you can also use Persistent Volume Claims (pvc) to write logs and traces to a file instead of writing them to the console (default). For more information, see Setting the Log Target.

Automic Automation

This release of Automic Automation introduces the features and functions listed below.

Telemetry - PUC REST API Endpoint

In Client 0, you can use the new PUC REST API endpoint to pull usage data on demand. For more information, see PUC REST API Endpoint.

Telemetry - Usage Data View

The Usage Data page has been moved and is now located on the Telemetry section of the Administration perspective in Client 0.

The page now uses the new PUC endpoint to display the usage data and has also been enhanced to allow you to filter your data for a specific usage period. For more information, see Usage Data .

CyberArk - New Configuration Options to Retrieve Passwords

Additionally to the current configuration, now you can use the vault account/object name or address as a unique identifier to retrieve passwords from the CyberArk vault. For more information, see UC_VAULT_CYBERARK - Password Vault Configuration.

Automic Web Interface

This release of Automic Automation introduces the features and functions listed below.

Cleaned-Up AWI Logs

In AAKE , you configure the Automic Web Interface using environment variables. This means that the uc4config.xml file traditionally used for the AWI configuration is not necessary. Since they are not relevant for AAKE, we have removed all the errors, messages and warnings related to uc4config.xml from the AWI log files. This way, finding the information that is actually relevant and important for you is easier and faster now.

AWI Theming

Automic Automation administrators can now define global default settings that affect AWI's appearance. You do this on the Theming page in the Administration perspective. The left pane in the Administration perspective has been slightly redesigned to accommodate this new page, where you can specify the following:

AWI's theme color
The set of colors that will be available to users for selection as connection color
The logo

Important! The way you set the color in on-prem systems is different to the way you do it in AAKE.

For more information, see AWI Management: Theming.