Q1 26 - 2.7.1784.39
Overview
The Q1-26 EM and POS release (v2.7.1784) delivers a comprehensive, fully packaged platform update spanning Store Server, POS, PDP/PDC, and Mobile clients (Android and iOS), together with the associated updaters and third-party integration components.
This release focuses on strengthening platform stability, improving operational resilience, and enhancing reporting and performance capabilities, rather than introducing new functional features.
Updated installers, configuration assets, and supporting documentation are included for all affected components to ensure a streamlined deployment and upgrade experience.
| Component | Version | Release Available At |
|---|---|---|
| Platform Release | 2.7.1784.39 | Artifactory: https://artifactory.enactorondemand.com/artifactory |
| Standard Docker Images | 2.7.1784.39.32 | Docker Registry: enactor.azurecr.io/enactorstandard/lin |
| Application Installers / Updaters | 2.7.1784.39.33 | Release SharePoint: Customer Release Space |
| Android version (APK) | 27.3.2 | Release SharePoint: Customer Release Space |
| iOS version (iOS) | 27.3.3 | Release SharePoint: Customer Release Space |
Distributables
Application Files
Installers
| Application Name | Installer File |
|---|---|
| Enactor Store Server | EnactorStoreServer-2.7.1784.39.33.msi |
| Enactor POS | EnactorPOS-2.7.1784.39.33.msi |
| Enactor PDP | EnactorPDP-2.7.1784.39.33.msi |
| Enactor PDC | EnactorPDC-2.7.1784.39.33.msi |
| Enactor PDP Client | EnactorPDPClient-2.7.1784.39.33.msi |
| Android Mobile POS | AndroidMobilePos-Generic-release-v27.3.2.apk |
| iOS Mobile Client | Generic_EnactorMobileClient_27.3.3.ipa |
Application Updaters
The following application updates are supported with the RC2 (2.7.747.RC2.535) and 24 Q3 (2.7.133.245).
| Component | Installer File |
|---|---|
| Application Updater | application-updater-2.7.1784.39-update.zip |
| PDP | update-2.7.1784.39.33-PDP-Min.zip |
| Back Office | update-2.7.1784.39.33-BO-Min.zip |
| PDC | pdc-update-2.7.1784.39.zip |
| POS | update-2.7.1784.39.33-POS-Min.zip |
Installer How-to Guides
POS Installation
EnhancementStore Server Installation
EnhancementStore Server on Docker
EnhancementPDP Server Installation
EnhancementThin Client Installation
EnhancementStandard Central Application - Docker Container Deployment
EnhancementStandard Central Application - Kubernetes Deployment
EnhancementVersions and Compatibility
| OS / Component | Minimum | Recommended | Maximum |
|---|---|---|---|
| Windows | 11 | 11 | 11 |
| Android | 14 | 14 | 16 |
| iOS | 16 | 18 | 26.2 |
| JDK | 17.0.11 | 17.0.11 | 17.0.11 |
| OS / Component | Minimum | Recommended | Maximum |
|---|---|---|---|
| Windows | — | 11 | — |
| JDK | — | 17.0.11 | — |
| Tomcat | — | 9.0.109 | — |
| OS / Component | Minimum | Recommended | Maximum |
|---|---|---|---|
| Ubuntu | — | 22.04 | — |
| Windows | 11 | 11 | 11 |
| Docker version | — | 20.10.24 | — |
The following docker images were used with JDK 17.0.1 and Tomcat 9.0.1077: EMA, EMP, EMP-SFTP, EMS, EMR, EMC, PDP, SOLR, SS.
| OS / Component | Minimum | Recommended | Maximum |
|---|---|---|---|
| MariaDB | — | 10.11.3 | — |
New Features
POS Features
Add Support for Supplementary Transaction Reference Entity
NewThe Supplementary Transaction Reference feature enables customers to associate one or more reference codes with a transaction. These codes can represent identifiers such as gift receipt numbers or exchange codes.
Reference codes may be scanned or system-generated and are stored with the transaction. They can later be used at the POS to quickly locate transactions for returns or other operational processes, offering a more efficient and flexible method for transaction retrieval and management.
To enable the Supplementary Transaction Reference services, it needs to import the process connection and process connection type files available in the how-to guide.
POS Transaction and Sequence Number Recovery (Disaster Recovery)
NewWhen the POS sends transactions to a Back Office or Estate Manager, two key numbers are included in each message: Transaction Number and Transaction Sequence Number. These numbers are typically managed by the POS, but the receiving systems use them to detect duplicate or missing messages.
Currently, if the POS database is lost, these numbers must either be manually reset on the receiving device (by editing the Back Office or Estate Manager database) or the POS must be configured to start from the previous Transaction and Sequence numbers (via the POS enactor.xml).
To streamline this process, the POS will be enhanced to automatically detect when it is running on an "empty" database and attempt to recover these numbers from the Back Office or Estate Manager automatically.
To support this service invocation, we have added a new process connection diagram extension. Relevant attachments are included in the how-to guide.
QR Code Customer/Loyalty Signup on Own Device
NewThis feature allows customers to register via a QR code shown on the Customer Display. With the required configurations, the POS will present a dedicated "Customer Sign Up" QR code that the customer can scan (e.g. with a mobile device) to open the online registration page. This removes the need for staff to capture full customer details at the till, speeds up the registration process, and helps ensure that customer data is captured accurately and consistently.
Please refer to the how-to guide for configurations.
Support Language Selection in Self-Checkout (SCO) implementation
NewIntroduced language selection to the customer-driven SCO POS application. When the customer selects a language button, the SCO start transaction screen will update to the chosen locale, and the transaction will proceed in that language. The selected locale button will be highlighted by changing the text colour to indicate the customer's choice.
If the customer does not select a language and starts the transaction, the system will default to the locale configured for the primary SCO user in the enactor.xml.
For transactions requiring operator intervention, the POS terminal will display the operator sign-on screen in the terminal's configured locale. Once the operator signs on, the screen will display the locale associated with their user record.
Please refer to the how-to guide for the configurations.
POS / ReactPOS - Implement RFID and Serial Numbered Products Scanning
NewThis functionality enables RFID-based item scanning for both POS and SCO systems. RFID tags are automatically scanned when within range, eliminating the need for manual intervention. The system adds new items to the basket while preventing duplicates, handles incomplete scans, and allows manual management of item removals.
Please refer to the how-to guide for configurations.
RFID API Security
NewThe online serial update feature can be enabled or disabled in POS Terminal or POS Terminal Template maintenance.
If enabled, the POS will make a real-time API call to the Serial Number Status Service. This will be a single POST request, with the request body containing an array of all the serial numbers sold or returned in the transaction. The Serial Number Update call is made from the POS on a background thread. If the service does not respond within a timeout period (e.g. 5 seconds), the user will be prompted with a Cancel button, allowing them to either wait for the full timeout or cancel the request. If the API call times out or the user cancels it, the event will be logged, and the POS will proceed to complete the transaction.
If the request fails for any reason, the failure is logged, and the POS continues to complete the transaction. SCO will fail silently. Serial number updates are supported in: Take Now and Returns, Post-Transaction Void, Order Returns.
A new Boolean property called Requires Security Clearance has been added to inventory types. By default, this property is set to false, meaning all inventory types are initially considered not to require security clearance and are allowed through the security API. If an inventory type should be restricted, the Requires Security Clearance checkbox must be checked to enforce validation through the security API.
POS Enhancements
Big Button POS Menu for Display Reports and Web Reports
EnhancementCurrently, both the Display Reports and Web Reports menus use the standard menu layout. With this enhancement, the Big Button menu layout will be applied to both menus, aligning their appearance with other menus such as Admin and Terminal Cash Management. These changes will be implemented across all POS platforms - PageDef POS, React POS, and Mobile POS. In addition, new icons, reused from Estate Manager, will be introduced for each report type.
All the required configurations are available in test configs; for more detailed configurations, please refer to the how-to guide.
Additional Buttons in the POS Header Menu and Burger Menu
EnhancementThis enhancement adds buttons to the POS Header Menu and Mobile Burger Menu. These buttons simplify navigation by enabling users to access the Terminal Cash Management and Inventory menus directly, reducing the need to navigate through longer menu flows.
The following privileges control the visibility of the buttons. These must be enabled for the respective roles.
| Function ID | Purpose |
|---|---|
enactor.pos.header.ShowTerminalCashManagementButton | Enables the Terminal Cash Management button |
enactor.pos.header.ShowInventoryButton | Enables the Inventory button |
Launch Menu Enhancement for Extended List of Functions
EnhancementThe new launch screen configuration now provides access to the following functional areas: Sell, Products, Order, CRM, Task, Inventory, Cash Management, and Administration.
This enhancement allows customers to configure and access key application functions directly from the launch screen, improving usability and navigation.
Enable the Launch menu configs from the POS Terminal Maintenance. Updated launch menu configurations are available in the how-to guide.
Inventory Launch Event - Implementation
EnhancementThe Inventory POS Launch feature enables users to start the POS system directly in Inventory mode. This mode restricts access to inventory functions only, offering a simplified and focused interface for inventory management.
Pos Terminal -> User Interface
| Configuration | Value | Description |
|---|---|---|
| Default Launch Event | InventoryLaunchStart | Directs the POS to open directly in the Inventory interface. Fixed value. |
| Display Launch Menu | Tick box selected | Required for the default launch event to work. |
The following parameters should be set to create the Inventory menu:
| Configuration | Value | Description |
|---|---|---|
| Menu Set | POS | POS is selected. |
| Role | Sales Assistant | Select the appropriate role for the user. |
| Menu Group | Default Standard POS | Select the appropriate menu group. |
| Locale | English (UK) | Select the appropriate locale. |
| Menu ID | INVENTORY_LAUNCH | Fixed menu ID, must be used. |
CRM Launch Event
EnhancementThe CRM POS Launch feature enables users to start the POS system directly in CRM mode. This mode restricts access to CRM functions only, offering a simplified and focused interface for customer management.
| Configuration | Value | Description |
|---|---|---|
| Default Launch Event | CRMSearchStart | Directs the POS to open directly in the client search interface. |
| Default Launch Event | CRMLaunchStart | Directs the POS to open directly into the CRM menu. |
| Display Launch Menu | Tick box selected | Required for the default launch event to work. |
Non-Functional Changes
Report Improvements
Optimised reports - new RPT design files
EnhancementOptimisation was done under three categories:
- Update index and query optimisation. (No need to update the menu to reflect the changes.)
- Update the rptdesign file. (Need to update the menu to reflect the changes.) If the customer uses this version, no changes are required as the menu will, by default, show the new report menu.
- For the existing configuration bundles, the table below defines the new RPT files as V2.
| Report | New RPT Design file |
|---|---|
Product/ProductSales | ProductSalesV2.rptdesign |
SalesSummary/TransactionTotals | TransactionTotalsV2.rptdesign |
Product/Replenishment | ReplenishmentV2.rptdesign |
Tender/TerminalX | TerminalXV2.rptdesign |
Product/TradingSummary | TradingSummaryV2.rptdesign |
CashUpSummary | CashupSummaryV2.rptdesign |
CashOnHand | CashOnHandV2.rptdesign |
ReasonCodeByWeekday | ReasonCodeByWeekDayV2.rptdesign |
MMGSummary | MMGSummaryV2.rptdesign |
MMGSummaryPieChart | MMGSummaryPieChartV2.rptdesign |
RollingReplenishment | RollingReplenishmentV2.rptdesign |
UserSales | UserSalesV2.rptdesign |
TenderTotalsPieChart | TenderTotalsPieChartV2.rptdesign |
A further 10 reports received index and query optimisations only (no rptdesign change): SalesSummary/DailySalesSummary, SalesSummary/SalesAnalysisByHour, Promotion/PromotionSummary, CashManagement/TerminalDiscrepancies, TransactionVoids, Exception/UserExceptionAnalysis, BankingTransactions, TerminalExceptions, TenderTotals.
Fiscal Core Countries
This release includes fiscal compliance capabilities for five core fiscal countries: Austria, France, Germany, Norway, and Portugal.
Data bundles for relevant countries are available in the release folder - Fiscal Data Bundles.
| Country | Solution Type | How-to guides / Configuration Bundles |
|---|---|---|
| Austria | Service Based - PrimeSign | How To Configure Fiscal Austria |
| France | Signature Based | How To Configure Fiscal France |
| Norway | Signature Based | How To Configure Fiscal Norway |
Fiscal New Changes
Austria | Registering POS using FinanzOnline Web Services
FiscalThis feature enables the registration of POS devices with FinanzOnline, the Austrian Tax Authority's online portal, directly through web services integration.
Configuration details and setup instructions can be found in the linked how-to guide.
Digital Payment Services
| Name | Type | Distributed file |
|---|---|---|
| Citcon | Digital Payments (Via Payment Portal) | digital-pay-2.7.1784.39.zip |
| Klarna | Digital Payments (At POS) | digital-pay-2.7.1784.39.zip |
Mobile Release
Enhancements
Customisation of background colour and status bar style
EnhancementCurrently the iOS client app hardcodes a background colour of black and a status bar style of "Black Translucent". For the new mobile UI, customers may want a white background and a different status bar style. To support existing clients while allowing this to be customised, preferences have been added so the user can change the background colour and status bar style.
Use Preferences to set: Use Safe Area Bounds, Status Bar Style (Default / Black Translucent / etc.), and Application Background Colour (e.g. #FFFFFF for white, #000000 for black). Default settings retain the existing black-translucent UI; new mobile UI clients should set status bar style to Default and application background colour to white.
Operating System Requirements
| OS / Component | Minimum | Recommended | Maximum |
|---|---|---|---|
| Android | 7.0 | 16 | 16 |
| iOS | 12 | 18 | 26 |
Android SDK Details
| Setting | Value |
|---|---|
| Compile SDK Version | 36 (Android 16) |
| Min SDK Version | 24 |
| Build Tools Version | 36.0.0 |
| Android Gradle Plugin | 8.13.0 |
| Gradle | 8.14.3 |
| NDK | 29.0.14206865 |
| JDK | 17 |
iOS SDK Details
| Setting | Value |
|---|---|
| Compile SDK Version | 17.2 |
| Min SDK Version | 12.0 |
| Support Models | iPhone / iPad |
| Xcode | 15.2 (15C500b) |
| Command Line Tool | 15.1.0.0.1.1700200546 |
Known Issues
| Key | Summary | Priority |
|---|---|---|
| POS-7166 | User is unable to see the EM reports with the transaction details | P2 |
| PPI-365 | Klarna Void Error: Failure During Part-Tender Cancellation | P3 |
Vulnerability Report
Please see the vulnerability analysis report for the 2.7.1784 release: External - Platform Vulnerability Analysis Report - 2.7.1784 (available on the customer release SharePoint).
BIRT Report Upgrade
The BIRT report runtime has been upgraded from 4.4.2 to 4.20.0-202506110821.
Localization and Internationalization
Improvements have been made to display messages as per the POS locale. Below are the countries supported in this release.
| Code | Country | Primary Language(s) |
|---|---|---|
| AT | Austria | German |
| BE | Belgium | Dutch (Flemish), French, German |
| BG | Bulgaria | Bulgarian |
| CY | Cyprus | Greek, Turkish |
| DE | Germany | German |
| DK | Denmark | Danish |
| ES | Spain | Spanish |
| FI | Finland | Finnish, Swedish |
| FR | France | French |
| GR | Greece | Greek |
| IS | Iceland | Icelandic |
| IT | Italy | Italian |
| LT | Lithuania | Lithuanian |
| NL | Netherlands | Dutch |
| NO | Norway | Norwegian |
| PL | Poland | Polish |
| PT | Portugal | Portuguese |
| RO | Romania | Romanian |
| SE | Sweden | Swedish |
| SI | Slovenia | Slovenian |
| UA | Ukraine | Ukrainian |
Application Files
This release contains updates to 88 message keys across 12 message files, covering POS Additional Themes, SCO General Messages, SCO Tender Messages, POS Promotion Messages, Customer View Messages, POS Error and General Messages, Serial Capture Messages, Exchange Item Messages, Payment Service Messages, Tender Messages, Receipt Messages, Task Maintenance Prompt Messages, Order Messages, Estate Director Received Transaction Number Messages, and Task Client Messages.
The full message-key inventory is preserved in the source release note (Confluence) and the customer release SharePoint.
Schema Changes from previous release
21 database tables changed schema versions from 2.7.1331.267 to 2.7.1784.39. See Schema Changes - Q1 26 for the full breakdown.