Skip to content

Changes in 4.1.0

SAML enterprise single sign on

4.1 comes with the ability to integrate with SAMLv2 SSO. This provides an enterprise-level Single Sign On solution for all clients and works with any IDPs. See the KX Delta Platform deployment guides and SAML Workflow for more information.

Permissions namespace

As part of the 4.1.0 release the permissions namespace has been renamed from .p to .pm. In order to smooth the transition, a mapping of the functions from the new .pm namespace to the previous namespace .p has been introduced. This mapping is controlled by an environment variable, which is set to carry out the mapping by default. The environment variable is set in delta.profile:


If this environment variable is set to YES when KX Control is started, the mapping will be carried out. The mapping will also be carried out on any permissioned process.

The mapping will not create tables or global variables in the .p namespace, only functions.

The mapping is carried out using functions in the namespace.

Lambda permissioning

It is possible to permission the running of lambdas. This is controlled by an environment variable in delta.profile which is off by default:


If this environment variable is set to YES when KX Control is started, only administrators will be allowed to run lambdas on Control or permissioned processes.

When lambda permissioning is enabled all core components should work as normal.

Query Builder

The KX Dashboards Query Builder uses lambdas, and will not work with permissioned processes.

Query router

Polling requests

Client interfaces support registering polling requests with the framework. QR manages the polling of requests and client receives updates periodically.


Parameter in the QP instances to set the default request aggregation function.


Ability for the QP to initiate sub-requests after an aggregation if required in the case of missing data.

Client registration

Notification callback when QR registration complete in Java Stream API and kdb+ client (.qr.client.register1)

Logging correlator

Log messages are prefixed with a string that can be used to correlate messages across different process logfiles. The prefix will be the same for each log message relating to a request, so the user can easily grep log files to see the status of a request. Assigned by the client on creation of a request or by the QR if none provided. All log messages across multiple processes will use the same correlator prefix.


Optional ability to enable timestamp recording for the lifecycle of a request. Useful for tracking request state and examining framework latency. More information in the Query Router docs.

Enhanced instance configuration

Detailed configuration of process instances can be carried out via the Instance Config reserved parameter.

This takes overrides of the INSTANCE_CONFIG parameter as possible values.

Using this, it is possible to set various supported parameters on a process instance.
Enhanced Instance Configuration

DC checkpoints

Added a viewer for checkpoints in Control and the ability to set a new one or to revert to a previous one.


Process status view

Added a viewer that lists only running processes, without workflow information.


Email distribution lists

Allow email distribution lists to be created and edited.

Compare entity revision history

For any entity viewer with a Revisions tab, you can compare any two revisions.

Compare revision history

In the Package Exporter view, there is now a search area to see if an entity is already in the package.



  • Static code-analysis tools integrated with core JVM KX Delta Platform components
  • Enhanced password-management and storage, with encryption and content control