Skip to content

Release 2.7.1

Release Notes

We’re excited to announce the release of version 2.7.1!

🚀 New Features

  • SSN Verification for Customers
    Added SSN verification to strengthen identity validation during customer onboarding and profile updates.

  • Enhanced Transaction History API
    Transaction History API now includes custom namespace details in the response for improved traceability and clarity.

🐛 Critical Bug Fixes

  • Fixed a critical issue affecting the update of Finclusive users to Silver/Gold tiers.
  • Addressed an issue with assigning "Proof of Address" information badges via the Update Customer API.
  • Platform and tenant users can now successfully Block/Unblock users.
  • Resolved Dashboard Insights issues related to:
    • Token visibility
    • Transaction-based categories
    • Off-chain transaction data
  • Fixed issue where custom namespaces were not updating during new wallet additions.
  • Resolved missing token balance display on the Customer Details Card for select users.
  • Corrected the console balance display on the Wallet User page.
  • Fixed a failure in Customer Full Details API when no financial badge is assigned.
  • Applied additional minor bug fixes and security improvements.

Upgrade Notes

The sequence of steps to follow to upgrade are:

  1. Container images and configmaps
  2. DB migrations

Container images and configmaps

All provided images, available in the Image List section should be downloaded and built to be LGPL compliant.

All new images tags will be used to update Kubernetes manifests.

Core microservice

ConfigMap

Replace the following values in Core microservice's ConfigMap:

configmap.yml
OSCILAR_WORKFLOW_VERSION: ''

Empty value

Clear any existing value from OSCILAR_WORKFLOW_VERSION; it is intentionally left empty.

Listener microservice

ConfigMap

Replace the following values in Listener microservice's ConfigMap:

configmap.yml
OSCILAR_WORKFLOW_VERSION: ''

Empty value

Clear any existing value from OSCILAR_WORKFLOW_VERSION; it is intentionally left empty.

DB migrations

Download DB migrations ZIP file available in Assets, unpack/unzip it in order to perform remaining instructions.

DB backup

Before proceeding with remaining steps, it's strongly advised to take a database backup before proceeding.

Update credentials

Edit/create a file named development.env inside db-migrations/src/common/envs folder

db-migrations/src/common/envs/development.env
DB_HOST=[replace with db host url]
DB_USER=[replace with db user]
DB_PWD=[replace with db user password]
DB_NAME=[replace with db name]

AZURE_TENANT_ID=[replace with azure tenant id]
AZURE_CLIENT_ID=[replace with azure client id]
AZURE_CLIENT_SECRET=[replace with azure client secret]
AZURE_KEYVAULT_NAME=[replace with azure keyvault name]

Execute DB migrations

Execute the remaining commands located inside the extracted content folder (e.g.: db-migrations):

Execute migrations
$ npm install
$ npm run migrate

Image list

Microservice name Image tag
Core Microservice omnumisandbox.azurecr.io/core:2.7.1-deliverable
Listener Microservice omnumisandbox.azurecr.io/listener:2.7.1-deliverable
Rule-Engine Microservice omnumisandbox.azurecr.io/rule-engine:2.7.1-deliverable
Frontend Microservice omnumisandbox.azurecr.io/frontend:2.7.1
Auth Microservice omnumisandbox.azurecr.io/ul-auth:1.0.1-deliverable

Assets

Login into files portal