Backend - Release Notes¶

Backoffice — Release Notes¶

EnQualify Signalling — Elastic APM Integration Tag: enqualify-signalling:20260907.1¶

Summary
Elastic APM integration has been added to the signal server. With this integration, the server's HTTP transactions, error logs, and Node.js runtime metrics (heap usage, CPU, event loop latency) can now be monitored through Kibana APM. The APM agent is preloaded at the application startup so that all requests are automatically tracked; http://socket.io, /health, and /metrics endpoints are excluded from monitoring to avoid unnecessary transaction generation.

Changes Made

1. Added to the .env file:

The following parameters are added to the end of the .env file. Values are filled according to the environment:

ELASTIC_APM_ACTIVE=true
ELASTIC_APM_SERVICE_NAME=<service_name>
ELASTIC_APM_SERVER_URL=<apm_server_url>
ELASTIC_APM_ENVIRONMENT=<environment_name>
ELASTIC_APM_TRANSACTION_IGNORE_URLS=/socket.io/*,/health,/metrics
ELASTIC_APM_CAPTURE_BODY=off
ELASTIC_APM_LOG_LEVEL=error
ELASTIC_APM_METRICS_INTERVAL=30s
# If APM Server requires authentication, one of the two is filled, both are not used
# ELASTIC_APM_SECRET_TOKEN=<token>
# ELASTIC_APM_API_KEY=<api_key>

1. In docker-compose.yml — Added to the enqualify-signalling service:

Values from the .env file are automatically read by compose, the following lines are added to the service:

- ELASTIC_APM_ACTIVE=${ELASTIC_APM_ACTIVE:-false}
- ELASTIC_APM_SERVICE_NAME=${ELASTIC_APM_SERVICE_NAME}
- ELASTIC_APM_SERVER_URL=${ELASTIC_APM_SERVER_URL}
- ELASTIC_APM_ENVIRONMENT=${ELASTIC_APM_ENVIRONMENT}
- ELASTIC_APM_TRANSACTION_IGNORE_URLS=${ELASTIC_APM_TRANSACTION_IGNORE_URLS}
- ELASTIC_APM_CAPTURE_BODY=${ELASTIC_APM_CAPTURE_BODY:-off}
- ELASTIC_APM_LOG_LEVEL=${ELASTIC_APM_LOG_LEVEL:-error}
- ELASTIC_APM_METRICS_INTERVAL=${ELASTIC_APM_METRICS_INTERVAL:-30s}
# If APM Server requires authentication:
# - ELASTIC_APM_SECRET_TOKEN=${ELASTIC_APM_SECRET_TOKEN}
# - ELASTIC_APM_API_KEY=${ELASTIC_APM_API_KEY}

1. Restarting the service:

docker compose stop enqualify-signalling && docker compose rm -f enqualify-signalling && docker compose up -d enqualify-signalling

enqualify-coturn 20260923.1 Release Notes — 23.09.2026¶

[VIDEO CALL] [NO CUSTOMER ACTION] [BACKWARD COMPATIBLE]

1. Version Summary¶

This release adds log rotation and human-readable timestamp logging to the enqualify-coturn (TURN) service, and prepares the infrastructure for metric monitoring. These changes enhance the operational visibility of the service and control over resource usage, while making no changes to TURN/relay functionality.

2. Customer Impact¶

3. Changes¶

Docker Log Rotation Added

Component: Video Call
Type: Improvement

What changed?
Automatic rotation based on size and number of files has been added to service logs; this eliminates the risk of disk overflow and ensures that sufficient historical logs are kept for problem analysis.

Does it affect customers?
No.

What needs to be done:
No implementation or configuration changes are required.

Log Timestamp Format Improved

Component: Video Call
Type: Improvement

What changed?
Human-readable (ISO 8601) timestamps have been added to log lines; this makes time-based matching of logs easier during problem analysis.

Does it affect customers?
No.

What needs to be done:
No implementation or configuration changes are required.

Preparation for Metric (Prometheus) Infrastructure

Component: Video Call
Type: New Feature

What changed?
Infrastructure has been prepared for the future transfer of service health and capacity metrics to monitoring systems.

Does it affect customers?
No.

What needs to be done:
No implementation or configuration changes are required.

4. Known Issues¶

There are no known issues.

v1.5.59 → 1.5.76¶

1. Scope¶

This section summarizes the changes in versions v1.5.70, v1.5.74, and v1.5.76 released between versions v1.5.59 to v1.5.76 of the BackOffice product.

During this period, the dynamic rule definition behavior has been expanded, NFC referenced comparison mode has been added, improvements have been made in BackOffice reporting and management screens, and the performance of video call recording initialization and token validation stability have been enhanced.

2. Administrator Summary¶

• A rule sequence has been added to the Dynamic Rule Definition module, and the rules are now updated to stop after producing results from the first rule according to the specified order.
• A new result type has been added to checklist result types, which can be used when not all expected answers are given for the questions.
• A new module and parameter have been added to allow NFC data to be compared with OCR/document data.
• Improvements have been made in the Call History Report, Online Quantity and Duration Information report, and in BackOffice management screens regarding visuals, filtering, and usability.
• The process of initializing recording in the video call has been expedited.
• Reliability of liveliness detection has been increased by adding a real person verification check to the DepthLivenessDetection method.
• Internal token validation tolerance has been expanded to reduce temporary connection errors that may arise from time differences between servers.

3. New Features and Major Improvements¶

3.1 Dynamic Rule Definition — Sequencing and Stopping at the First Matching Rule¶

Component: Backend / BackOffice
Type: Breaking Change

A Sequence field has been added to dynamic rule definitions. The rules are now evaluated according to this sequence, and evaluation stops after the first rule that produces a result. In the previous behavior, all rules were evaluated sequentially, and results were combined.

Customer impact: Conditional. It only affects integrations defining multiple dynamic rules.

What needs to be done: The Sequence value should be entered for existing dynamic rule definitions through BackOffice, and the priority sequence should be verified. Rules with the sequence field left empty may be evaluated in an unexpected order and may lead to deviation in the result set.

3.2 Dynamic Rule Definition — New Control Result Type¶

Component: Backend / BackOffice
Type: New Feature

A new option (AllNo) has been added to the checklist result type that captures cases where an expected answer is not provided for all questions in the list.

Customer impact: No. The new option can optionally be used through BackOffice.

3.3 Comparing Based on NFC Data Reference¶

Component: Backend
Type: New Feature

A new mode has been added to allow the comparison of document (OCR) data based on NFC (chip) data reference in the authentication flow.

Customer impact: Conditional. It only affects integrations that want to use this mode.

What needs to be done: The Verify.Setting.Web.UseNfcAsCompareReference parameter is turned off by default. If this comparison mode is desired, it must be activated for the relevant call type through BackOffice.

3.4 Video Call Recording Initiation Accelerated¶

Component: BackOffice — Video Call
Type: Improvement

The process of initiating recording in a video call has been expedited. The triggering of recording occurs in a shorter time after the connection is established.

Customer impact: No. No implementation or configuration changes are required.

3.5 DepthLivenessDetection Real Person Check¶

Component: BackOffice — AI / Verification
Type: Improvement

A real person verification check has been added to the DepthLivenessDetection method. This improvement increases the reliability of liveliness detection.

Customer impact: No. No implementation or configuration changes are required.

4. Reporting and Management Screen Improvements¶

4.1 Call History Report Screen Improvements¶

Component: BackOffice
Type: Improvement

Improvements have been made to loading indicators, internet connection speed display, and visuals and filters in integration data/detail windows in the BackOffice Call History Report screen.

4.2 Online Quantity and Duration Information Report — Duration Format Revision¶

Component: BackOffice
Type: Improvement

In the Online Quantity and Duration Information report, the display format of duration information has been revised to hour:minute:second format, including screen and Excel export.

4.3 Call Retry Log Text Updated¶

Component: BackOffice — Management Panel
Type: Improvement

The expression Video Call Restarted displayed on the representative log screen has been updated to the more accurate definition Video Call Connection Retried. TR/EN/AZ localization has been included.

4.4 UI Modal Background Transparency Updated¶

Component: BackOffice — Management Panel
Type: Improvement

The modal background transparency value has been updated.

5. Infrastructure, Stability, and Build Improvements¶

5.1 Internal Token Validation Stability Improved¶

Component: BackOffice — Authentication
Type: Improvement

Time offset tolerance in the internal token validation mechanism has been expanded, and improvements have been made for token validity duration validation. Thus, temporary connection errors arising from time differences between servers are prevented.

5.2 BackOffice Angular Interface Build Stability¶

Component: BackOffice
Type: Bug Fix

Stability issues that could occur during the build process of the BackOffice Angular interface have been resolved.

6. New / Changed System Parameters¶

7. Version and Compatibility¶

8. Migration Steps¶

1. Ensure that the database update scripts, especially those related to the Sequence column and relevant source texts, have been applied.
2. Enter the Sequence value for existing dynamic rule definitions via BackOffice after the version update.
3. Validate rule results in the test environment for integrations using multiple dynamic rules.
4. For integrations that want to use the NFC referenced comparison mode, activate the relevant parameter.

9. Known Issues¶

There are no known issues.

v1.4.131 → v1.5.59 versions

1. Scope¶

This document summarizes the features added, business rules changed, new system parameters, and improvements during the period from version v1.4.131 to v1.5.56 of the EnQualify Plus Backoffice product.

The goal is to enable the business units and integration teams to evaluate the new capabilities and configuration options before the version transition. Technical improvements that do not reflect on user experience or configuration are excluded from scope, and only changes affecting product behavior are listed.

2. Administrator Summary¶

Key changes during this release period include:

• Authentication security has been strengthened with three new layers: Visual Security Element Verification, Touch Test (Conceal Testing), and a completely new Voice Verification module.

• The structure for storing call records has been renewed: records are now kept in a date and time-based folder hierarchy; existing records are also automatically migrated to the new structure.

• Chunk loading capability has been added to allow larger video files to be uploaded reliably over weak connections.

• Support for verifying name-surname for Azerbaijani identity cards has been added; the name comparison engine has been updated to perform tolerant (fuzzy) matching.

• The reflection of face verification and anti-spoofing results in the final assessment has been reinforced.

• The video call screen (Flexible View) is now highly customizable on an organization basis; many elements such as color, font size, camera layout, OCR frame visuals can be configured in detail.

• New dashboard indicators and an "Approval Pending List" menu have been added for the supervisor approval process.

• Personal data masking (email, phone number) can now be managed separately for Supervisor and Representative roles.

• The dynamic assessment structure has been improved; call termination reasons can now be managed based on rules.

• The user interface and server-side infrastructure have been modernized for performance and sustainability.

3. New Features and Major Improvements¶

3.1 Voice Verification¶

During the call, predefined questions are asked of the customer (in random order if desired), and their verbal/visual responses are automatically compared with the predefined expected answers. This entirely new authentication channel strengthens verification through asking a customer-specific security question in addition to existing facial/identity verification.

On the mobile application side, three new services have been added for this module:

• Sending the group of questions/scenario to the mobile device (Verbal Approval List configuration)

• Uploading the customer's verbal/visual response to the system

• Approval of voice verification by the representative

3.2 Visual Security Element Verification¶

Physical security elements on the identification document (hologram, security thread/microprint, crescent, signature, optical variable ink-OVI, barcode, chip, MRZ, etc.) are now evaluated and recorded each separately, with their own security score and threshold value.

According to the type of identity, the rule of "how many front + how many back security elements must be valid" can be defined from the Parameter screen. Thus, the rule of verification rigidity can be adjusted by the business unit for different identity/document types. If a document does not meet this criterion, a defined action (e.g., give a warning / stop the process) is triggered.

3.3 Touch Testing (Conceal Testing)¶

A new test has been added that checks whether the security elements on the identification card (microprint, crescent, signature, OVI) can be accurately detected by the system even when partially covered or tilted by a finger. This adds an extra layer of security that increases the likelihood of capturing physically replicated or shown-in-screen fake identities.

The test result and the minimum security threshold (default 30%) can be managed from the Parameter screen, and the feature can be activated or deactivated on a system-wide basis.

3.4 Renewal of the Call Record Storage Structure¶

Call records are now written into subfolders structured by Year / Month / Day / Hour based on their creation date and time. This structure ensures that file access and management performance is maintained as record volume increases. The change is applied the same way for both local disk storage and S3-compatible cloud storage.

The transition of existing records to the new folder structure is done gradually with a background transport task that operates automatically and seamlessly; this process is designed not to impose system load and is carried out while maintaining the integrity of the records.

3.5 Chunk Video Uploading¶

Large call videos are uploaded in small portions to avoid timeouts during single uploads, especially over weak connections. The maximum waiting time for normal uploads (default 180 seconds) has been made parameterized; when this time is reached, the system automatically switches to chunk uploading.

3.6 Flexible Call Screen Customizations¶

The video call screen viewed by the representative and the customer can now be customized largely on an organization basis: color themes, font sizes, positioning/sizing and shifting of camera images, OCR frame visuals (success/failure/default, separately for front and back), visibility and position of the representative name, flash button icon like numerous visuals can be configured without code changes.

3.7 Supervisor Approval Process Improvements¶

A new menu ("Pending Approval List") that facilitates tracking pending operations for users in the Supervisor role and dashboard cards added with "Total Pending Approvals" and "Pending Approvals Assigned to Me". Additionally, it is now possible to manage whether the reason for terminating a call will be displayed as a card on this approval dashboard from the parameter screen.

3.8 Personal Data Masking¶

Whether the customer's email address and phone number will be masked on the Supervisor and Representative screens can now be managed separately for both roles (by default email is masked on the Supervisor screen, and visible on the Representative screen). This allows for more sensitive control of personal data visibility based on the role.

3.9 Azerbaijani ID Support and Name-Surname Matching Engine¶

The logic for name-surname comparison has been expanded to support not only Turkish identities but also Azerbaijani (AZE) identities; correct processing of characters specific to the Azerbaijani alphabet in MRZ-identity record matching is ensured.

In this scope, a general-purpose, reusable name matching engine has been developed; the engine can perform matching with a certain tolerance ("similarity ratio") instead of exact matching when necessary. Issues related to punctuation in abbreviated names have also been resolved in this context.

3.10 Dynamic Assessment Structure¶

A structure has been established to bring call termination reasons according to the rules defined during the call.

• A process definition screen has been added to manage multiple processes.

• A rule definition screen has been added.

• The Evaluation structure has been revised to run the rules.

3.11 Integration and Infrastructure Capabilities¶

• A new e-commerce platform integration API has been added.

• In corporate integrations, the status update and authentication (login) services have been separated to increase configuration flexibility.

• Support has been added for additional cloud storage providers that are S3 compatible; compatibility options with on-prem and non-AWS S3 compatible providers have been expanded.

• Infrastructure has been prepared and integrated with EnQualify for Speech-to-Text and Text-to-Speech services.

• Data protection / field encryption capability can be activated at the installation level.

4. Evaluation of Verification Results¶

With this release, the following improvements have been made in generating the final verification result of a call:

• The cases where the facial similarity score could not be produced for technical reasons have been improved to be reflected in the result evaluation; these cases are now marked as "failed" (Red).

• The result of anti-spoofing/liveliness detection now directly reflects in the overall result of face verification (Green/Yellow/Red color code).

• The artificial intelligence check that verifies whether the face in the photo on the identification document is covered by an object/hand has been made activatable through parameters.

• The issue of name-surname matching which can occur when there are punctuation characters in names in the population registry has been resolved.

These improvements increase verification reliability. After the version transition, you can review the alignment of the settings with your organization's needs.

5. Data Structure Changes¶

During this release period, the data model has been expanded to support the new features. Changes are applied automatically with the product update; no action is required on the business unit side.

6. New / Changed System Parameters¶

The following parameters are system parameters that can be managed via the Settings/Parameter screens, enabled/disabled on an organization basis, or set as values.

7. Integration Capabilities¶

During the period, new service capabilities directly related to integration processes have been added. Detailed endpoint and parameter documentation is provided through the Developer Portal for integration teams.

• Touch Testing: Uploading the security visuals on the identity for verification.

• Voice Verification: Services for delivering the verification scenario to the mobile client, uploading customer responses, and for representative approval.

• Identity Pre-Identification: An identification service that determines the document type before OCR.

• Queue Management: Querying the customer queue position.

• Model Configuration: The new version of the mobile model/configuration download flow.

• Verification Rigidity: More flexible configuration of authentication parameters including the number of visual elements to be verified and actions based on document type.

• Nationality Distinction: The name-surname comparison service can operate based on nationality (TUR/AZE).

8. Release Content — Detailed List¶

This section provides a detailed list of changes made during the release period categorized by type.

8.1 New Features¶

• Support for additional cloud storage provider (object storage) has been added.

• Azerbaijani ID verification has been added.

• Encryption feature using SHA256 has been added.

• Chunk video uploading/playing feature has been added.

• Call retry feature has been added.

• Dynamic management of visual element analysis has been enabled.

• Touch Testing feature has been added.

• Anti-spoofing historical analysis feature has been added.

• Column settings have been added to the General Performance Report.

• A refresh button has been added to the Representative Analysis Report.

• A daily view option has been added to the Call Performance Report.

• Description windows have been added to the Call History Report.

• A close button has been added to the flash screen.

8.2 Improvements¶

Key updates that improve user experience in existing features:

• Evaluation flow: The evaluation steps on the video call screen have been made smoother.

• Approval menu: Approval menus have been reorganized under the Parameters menu, and menu names have been clarified.

• Personal data masking: Masking options in General Settings have been improved.

• Reports: Column settings have been added to the General Performance Report, a daily view to the Call Performance Report, and a refresh feature to the Representative Analysis Report; date validation has also been added to the Call Routing Report.

• Audio management: Management of audio files according to call types and the audio change function have been improved.

• Snapshot Category: The parameter screen (list and modal views) has been updated.

• Visual consistency: Font and default visual usage between screens have been standardized.

Additionally, background improvements such as the call record storage structure, integration traceability, dynamic naming of "Successful/Failed", and various screen performance have been made that do not directly change customer experience.

8.3 Fixes¶

The following fixes directly affect behaviors users can observe on the screens:

• Call statistics: Some answered calls were appearing as "unanswered" in reports; calls are now correctly classified.

• Report date filters: The issue where the starting date filter produced results different from expected has been fixed in redirection, Representative Check In-Out, and Unanswered Call reports.

• Excel export: The issues that occurred during the export of the Process List Monitoring report to Excel have been resolved.

• Date of birth display: The display of birth dates in the Process List Monitoring report has been corrected.

• Password renewal: The issue preventing passive users from completing the password renewal process has been resolved.

• English interface: The display issue that occurred on some screens when the Backoffice language was selected as English has been fixed.

• Appointment Day: The incorrect display of the status list on the screen has been corrected.

• Cloud storage: The connection issue affecting access to call records in certain cloud storage configurations has been resolved.

Furthermore, various stability and display fixes that do not directly change the customer experience have been made in reporting, dashboard indicators, call control definitions, evaluation description settings, and general UI areas.

8.4 Infrastructure and Performance Work¶

Comprehensive infrastructure improvements that do not affect current usage have been completed in the background for the product's performance, security, and long-term sustainability.

9. Pre-Migration Recommendations¶

• New security controls (Visual Security Element Verification, Touch Test) come with default threshold values. These values can be freely adjusted from the Parameter screen according to your organization's needs; you may also continue using the defaults if you wish.

• Since new verification layers have been introduced, it would be beneficial to observe the alignment of results with your organization's expectations during the initial period after transition and fine-tune the settings.

• The defaults for personal data masking (email masked on the Supervisor screen, visible on the Representative screen) should be confirmed according to your organization's data visibility policy.

• Since flexible customization of the Call Screen can be configured on an organization basis, it is advisable to check the appearance settings prior to the migration.

If you need further details or clarification regarding the impact of any item in this document on your business processes, you can contact your Enqura account representative.