Search
Link Search Menu Expand Document
Kony Quantum is now HCL Volt MX. See Revised Terminology. Current Quantum users, see the important note about API naming.
Release:

HCL Volt MX Foundry 9.2 Release Notes

This page lists changes and new features in HCL Volt MX Foundry 9.2.

Changes

  • Volt MX Legacy Sync has been deprecated. The last version of Legacy Sync server was 8.3. You cannot create a new Legacy Sync-based client application. New applications that need offline and sync capabilities must use the Offline Objects feature. For more information, see Using Volt MX Legacy Sync with Foundry.
  • HCL Cloud License Server is the preferred method for activating licenses. If your Foundry server does not have access to the Cloud License Server, you can use your HCL Software ID to download the installer for the HCL Common Local License Server from the HCL License and Download Portal. Instructions for activating a license on a private network have been updated. You must have valid HCL Flexnet server credentials to activate your license. If you are upgrading from a Temenos Fabric server to a Foundry server, your existing, activated Temenos license will be removed, and you must acquire a fresh license through the HCL Flexnet server. For more information, see Volt MX Foundry.
  • For Foundry Installer On-Premise, we have upgraded JBoss from 7.2 to 7.3 and Tomcat from 9.0.33 to 9.0.45. For Foundry Container On-Premise we have upgraded Tomcat from 9.0.33 to 9.0.45.
  • The USE_DSA_AS_DEFAULT_FOR_TOKEN_SIGNING -D parameter has been removed. RSA is set to default.
  • Foundry console login token expiration can be configurable.

New Features & Enhancements

In this release, the following features have been introduced or enhanced to provide a better Volt MX Foundry experience.

  • Added a new Red Hat PAM Adapter in Integration services

    From Volt MX Foundry V9 SP2 onwards, a new Red Hat PAM adapter is added in the Volt MX Foundry Console. You can use this adapter to explore Rules, Process, and Cases defined in your Red Hat Process Automation Manager instance and create Services and Operations in the Foundry Console.

    For more information about this feature, click here.

  • Support for OpenAPI 3.0 files in the OpenAPI (Swagger) adapter.

    From Volt MX Foundry V9 SP2 onwards, you can import OpenAPI 3.0 files to create Integration services and operations.

    For more information about this feature, click here.

  • Added a new type of Workflow service – Event triggered

    From Volt MX Foundry V9 SP2 onwards, Foundry Workflow can now be initiated by listening to Foundry Events. The following three new Signal Events are introduced to support Event based invocations.

    • Signal Start (to start a workflow instance)
    • Catch Signal (to resume a paused workflow)
    • Throw Signal (to raise an Event from workflow)

    For more information about this feature, click here.

  • Enhancements to Object linked workflows

    From Volt MX Foundry V9 SP2 onwards, the ability to access parameters based on array index in the workflow designer while configuring conditional logic has been added.

    For more information about this feature, click here.

    Also, added the ability to store the Identity and Session scope parameters from incoming requests into FOUNDRY_WORKFLOW_CONTEXT at the User Task level.

    For more information about this feature, click here.

  • Enhancements to Workflow Audit history

    The Workflow Audit history has been enhanced for the following:

    • Added support to manually retry a failed task in a workflow along with Editing the payload via namespaces. This is a runtime edit to the erroneous payload and helps retry the failed task in a workflow and resume execution from point of failure.
    • Added support to display the primary key of linked object in case of object linked workflows.
    • Added support to display the Correlation ID values in case of Event triggered workflows.

    For more information about this feature, click here.

  • Enhancements to Foundry application Publish

    • The Publish section has been enhanced to display environments status such as Available, Busy, and Unknown. This is a quick feedback mechanism to inform a user in case the server is busy publishing another application.
    • Added incremental application publish support to significantly reduce the publish time of an app after the first publish.
    • Added a new reconfiguration option to skip swagger generation steps during publish.
    • Improved error messaging in case of publish failures.

    For more information about this feature, click here.

  • Enhanced reconfiguration file

    From Volt MX Foundry V9 SP2 onwards, a new simplified format of reconfiguration file is supported to improve the readability and simplify the editing of the file.

    For more information about this feature, click here.

  • Added a new application Promotion Mechanism

    From Volt MX Foundry V9 SP2 onwards, a new application promotion mechanism is introduced. From the snapshot page of an environment, a user can download a deployment package containing the application archive at the publish time and reconfiguration file. The Deployment package can be directly promoted to an environment without being impacted by the changes in console

    For more information about this feature, click here.

  • Support for PKCE in OAuth 2.0 Identity Providers

    From Volt MX Foundry V9 SP2 onwards, all OAuth Identity providers support PKCE (proof key for code exchange) in authorization code flow. For backend Identity providers that support PKCE, Iris SDK and Identity will honor additional PKCE mechanism implicitly without any code changes. For the providers that do not support PKCE or in case of clients that use Volt MX V9.1 or lesser, the authorization code grant flow will continue to be honored without the PKCE enhancement.

    For more information, click here.

  • Support for Refresh Token Grant type in OAuth 2.0 Identity Providers

    From Volt MX Foundry V9 SP2 onwards, Refresh Token Grant Type support is added for OAuth 2.0 Identity services. The Refresh Token grant type is used by clients to exchange a refresh token for an access token when the access token has expired. This allows clients to continue to have a valid access token without further interaction with the user. A new Refresh login API is added in SDK to support the refresh login flow.

    For more information, click here.

  • Added Console Access Control for Identity services

    From Volt MX Foundry V9 SP2 onwards, console access control is added for Identity services. You can now control who can access and edit a particular Identity service.

    For more information, click here.

  • Support for Remember consent in OAuth Provider

    In OAuth Provider client consent dialogue, from Volt MX Foundry V9 SP2 onwards, a new option is added to remember the Consent provided by the user.

    For more information, click here.

  • Enhancements to support application merger from Foundry CLI

    From Volt MX Foundry V9 SP2 onwards, a new command is added in Foundry CLI to support application merge.

    For more information, click here.

  • Enhancements to External User Authentication

    From Volt MX Foundry V9 SP2 onwards, External User Authentication has been enhanced to support configuring multiple identity providers. You can now configure more than one Identity providers in a single Foundry account, which allows the users to log in to Foundry console by using multiple types of authentication providers.

    For more information about this feature, click here.

  • Support for Oracle 19c

    From Volt MX Foundry V9 SP2 onwards, support for installing Volt MX Foundry on Oracle 19.c is added.

    For more information about this feature, click here.

  • Enhancements to the MySQL support

    From Volt MX Foundry V9 SP2 onwards, support for the following is added:

    • Support for installing Volt MX Foundry on MySQL 5.7.31.
    • Support for MySQL Cluster with Group Replication.

    For more information about this feature, click here.

  • Enhancements to the MSSQL support

    Support for case sensitive collations on MSSQL Server.

HCL App Factory

  • Added support for Flyway Migration.

    You can now use App Factory to fetch Flyway scripts from your source-control module, add specific commands and command-line options, and then run the scripts on your database.

    For more information, click here.

  • Added support for Build on Push in Foundry projects.

    You can now configure watchers for your Volt MX Foundry projects, which will trigger the build job when changes are pushed to the source-control module.

    For more information, click here.

  • Added new parameters in Project Settings.

    After you create an App Factory project, you can use the revamped Project Settings to configure parameters that are related to source control, internationalization, quality, and notifications.

    For more information, click here.

  • Added support for Service Configuration Profiles

    You can now use Service Configuration Profiles in the Foundry build pipeline to configure endpoints for different environments, such as development, testing, or production.

    For more information, click here.

  • Added support for Arxan Web Obfuscation

    You can now configure Web Protection parameters in the Iris build to enable Arxan Web Obfuscation for your app.

    For more information, click here.

Naming changes

Product names, API namespaces, and other terms have changed.

  • Replace any references to Kony headers in Fabric (now Foundry) services, pre/post-processor, or custom code with Voltmx headers. (Replace “X-Kony-“ with “X-Voltmx-“.)

Refer to the following table for details.

Product names

New Terms (Volt MX) Old Terms (Temenos)
Volt MX Quantum
Iris Visualizer
Foundry Mobile Fabric
Foundry Fabric
Flare Nitro

API namespaces

This table shows the new Volt MX APIs namespaces versus the old Temenos APIs namespaces, along with examples. The new namespaces are used throughout this documentation; however, if you use a Temenos branded version older than 9.2, you must keep using the old Temenos namespaces.

New Namespace (Volt MX) Old Namespace (Temenos)
voltmx kony
com.hcl.voltmx com.konylabs
com.hcl.voltmx com.kony
com.voltmx \* com.kony
VMXMetricsService KNYMetricsService
VMXFoundry KNYMobileFabric
voltmx.sdk.VMXObjSvc kony.sdk.KNYObjSvc
voltmx.sdk.VMXObj kony.sdk.KNYObj
VoltMXApp KonyApp
VoltMXUtil KonyUtil
Examples
voltmx.ui.Alert kony.ui.Alert
voltmx.os.deviceInfo kony.os.deviceInfo
com.hcl.voltmx.middleware.api com.konylabs.middleware.api
com.hcl.voltmx.middleware.dataobject com.konylabs.middleware.dataobject
VMXFoundry.OfflineObjects.drop KNYMobileFabric.OfflineObjects.drop

* Beacon API. Requires rebuilding/conversion to NFI

Other

This table shows new Volt MX terms versus old Temenos terms.

New Terms (Volt MX) Old Terms (Temenos)
iris viz
Iris Viz