You can now configure OAuth clients of type Native with redirect URLs that use prefixes other than http:// and https://. This enables broader, more flexible integration with OAuth clients such as AI-powered IDEs, including Cursor and Kiro.

Tenant Admins can configure these OAuth clients in Administration > OAuth.

Creating and managing OAuth clients

Direct Access gateway now surfaces benchmark test results directly in the Administration activity center, giving administrators more transparency into gateway performance without needing to dig through log files.

Benchmark tests are diagnostic operations that measure network connectivity and performance between the Direct Access gateway and Qlik Cloud. Use them to troubleshoot reload performance, establish performance baselines, or compare gateways.

You can now view the results of these benchmark runs directly in the Administration activity center, making it easier to identify network conditions that affect reload performance and to gather the information you need for troubleshooting — without leaving the admin experience.

To use this functionality, you need Direct Access gateway version 1.7.17.

For more information, see Viewing and running benchmark tests.

Trusted OAuth machine-to-machine (M2M) bot users can now back up, audit, migrate, and manage automations across a tenant programmatically with the admin.automations scope, including ones owned by other users – without having to temporarily transfer ownership first.

This builds on the admin.apps scope which already provides access to private application content for these administrative and programmatic use cases.

For more information, see the Qlik Developer portal change log.

Semantic types can now be imported and exported directly from the interface, using a JSON file. This supports migrating types between tenants and replicating configurations across environments in a few clicks.

Importing and exporting semantic types

Write table now supports a Date picker input type for editable columns. Users can select dates directly in table cells and save changes to the change store, alongside existing manual entry and single-selection input methods.

For more information, see Date picker.

Automations can now be scheduled using the same recurrence options available for app reload scheduling, making it easier to run automations exactly when you need them.

Previously, automation schedules were limited to a start date, an end date, and a fixed recurrence interval. Anything more specific, such as running only on weekdays, had to be built into the automation logic itself using condition blocks.

With this update, you can now schedule automations to run at frequencies including:

• Weekly, monthly, or yearly, and not just at fixed intervals

• On specific days of the week or month

• On recurring patterns such as the last day of every month

• Multiple times per day within a defined time window

• Between a start time and end time each day until a defined end date

For more information, see Working with automation scheduling

You can now export new conversations with the Qlik Answers assistant as PDF files. This capability supports conversations involving both structured and unstructured data within an application and assistant context.

Trusted OAuth machine-to-machine (M2M) bot users can now back up, audit, migrate, and manage automations across a tenant programmatically with the admin.automations scope, including ones owned by other users – without having to temporarily transfer ownership first.

This builds on the admin.apps scope which already provides access to private application content for these administrative and programmatic use cases.

For more information, see the Qlik Developer portal change log.

Store changes settings are now available for lake landing replication tasks in a dedicated Store changes tab. With these new capabilities, lake landing replication functionality further bridges the gap with standard replication functionality, enabling consistent change management across replication task types.

Key features include:

• Change Table capture: Automatically store INSERT, UPDATE, and DELETE operations from the source in Change Tables on the target platform for incremental downstream processing.
• DDL handling options: Choose whether to automatically apply schema changes from the source to Change Tables or ignore DDL modifications to maintain fixed table structures.
• Configurable storage: Select whether to capture both before and after image data on updates, and customize Change Table naming conventions with configurable suffixes and header column prefixes.
• Header column management: Exclude specific system metadata columns from Change Tables to reduce storage requirements, or keep all header columns for complete audit information.
• Flexible full load behavior: Determine how existing Change Tables are handled when a full load starts—DROP and CREATE, delete old changes only, or keep all historical changes.
• Reorganized settings: Change Data Partitioning settings have moved from the General tab to the new Store changes tab for better organization and usability.

Store changes settings