1 Feature Summary
This chapter describes the feature enhancements in this release.
Noteworthy Enhancements
This guide outlines the information you need to know about new or improved functionality in the Oracle Retail Xstore Office Cloud Service update and describes any tasks you might need to perform for the update. Each section includes a brief description of the feature, the steps you need to take to enable or begin using the feature, any tips or considerations that you should keep in mind, and the resources available to help you.
Note:
Where new fields, User Interface (UI) changes, or glossary entries are introduced as part of a change, the portal owner may need to apply their own translations of the core system text.Column Definitions
-
Feature: Provides a description of the feature being delivered.
-
Module Impacted: Identifies the module impacted associated with the feature, if any.
-
Scale: Identifies the size of the feature. Options are:
-
Small: These UI or process-based features are typically comprised of minor field, validation, or program changes. Therefore, the potential impact to users is minimal.
-
Large: These UI or process-based features have more complex designs. Therefore, the potential impact to users is higher.
-
-
Delivered: Is the new feature available for use immediately after upgrade or must the feature be enabled or configured? If no, the feature is non-disruptive to end users and action is required (detailed steps below) to make the feature ready to use.
- Customer Action Required: You must take action before these features can be used. These features are delivered disabled and you choose if and when to enable them.
Table 1-1 Noteworthy Enhancements
| Feature | Module Impacted | Scale | Delivered | Customer Action Required? |
|---|---|---|---|---|
|
Xadmin Settings/Deployment |
Medium |
No |
Yes |
|
|
Deployments/File Upload |
Medium |
No |
Yes |
|
|
Xadmin Settings/Purge |
Small |
Yes |
No |
|
|
Replication |
Medium |
Yes |
No |
|
|
Support Dashboard and Tools/Logs |
Small |
Yes |
No |
|
|
Xadmin UI/Home Screen |
Medium |
Yes |
No |
|
|
Store Maintenance/Payments Integration |
Medium |
No |
Yes |
|
|
XOCS / RDS Replication |
Small |
Yes |
No |
|
|
RTLog Generator (Through REST, SFTP or FTS) |
Small |
Yes |
No |
New and Updated Options
This section describes the new and updated options.
Functional Enhancements
This section describes the functional enhancements for this release.
Deployment Download Read-Timeout Configuration
A new Xadmin setting is introduced for the Xenvironment deployment download read timeout. Administrators can use this setting to adjust the timeout value in milliseconds when store-side deployment downloads or polling operations need more time due to network or service response delays.
Customers should review the default value and adjust the setting only when their deployment download behavior requires a longer timeout.
AutoJoin Endpoint for File Upload Processing
This release introduces an AutoJoin upload endpoint for Oracle Retail Xstore Office Cloud Service file processing. The endpoint supports automated staging, grouping, and combining of smaller files that share scheduling attributes before handoff to AutoDeploy.
Customers or integrations that generate many small files for the same destination can evaluate this endpoint to improve batch handling and processing efficiency.
File Transfer Archive and Upload Retention Wording Updates
Xadmin purge setting wording is updated for clarity. The Number of Days to Keep File Transfer Archives description is clarified to remove ambiguous references and better describe archive retention behavior. The Number of Days to Keep File Uploads label is renamed to Number of Days to Keep Xadmin File Uploads.
No customer action is required. Existing configuration behavior and values are not expected to change.
Duplicate Replication Record Handling and Purge Support
Replication processing is enhanced to identify benign duplicate records caused by primary key constraint violations. These records can be marked with a duplicate status and purged through maintenance processing, helping reduce non-actionable replication queue buildup.
No customer action is expected unless customers monitor replication statuses and want to update operational procedures to recognize the new duplicate status.
Plain-Text Log Message Search Improvements
The Xadmin System Management Logs search is enhanced so users can search log messages with plain text rather than manually adding SQL wildcard characters. The system handles wildcard matching during query execution, improving the usability of log searches.
No customer action is required.
Xadmin Home Screen Tab Image and Label Updates
This release updates the images, labels, and descriptions for the New Xstore home screen tabs within Xadmin. The preview panel is enlarged and tab images are centered to make home screen tab visuals easier to review. The tab context drop-down options are renamed to align with current Xstore home screen and transaction panel terminology, and the obsolete Tender tab option is removed.
No customer action is required. Customers may optionally review home screen tab configuration after upgrade to confirm the updated labels and preview images align with their store operations.
Shopper Statement Field for Store Maintenance
A new optional, configurable Shopper Statement field is available on the Xadmin Store Maintenance pages. The value can be maintained at the store level and passed to the Oracle Payments Cloud Service (OPCS) integration so the configured text can appear on the shopper's banking or credit card statement.
Customers who use OPCS integration should decide whether they need to populate this field for stores after upgrade.
RDS Replication of the Xcenter Security Activity Log
The Xcenter sec_activity_log table is now replicated to Retail Data Store (RDS). This allows customers to access Xstore security activity log data through RDS for reporting, analysis, and downstream data consumption. Customers can also purge security activity log data according to their data retention and operational requirements.
RTLog File Naming Convention Update
RTLog file names now use a stable pod suffix for the RTLog generator process. For example, file names may end with node_rtlog-generator-0.DAT or node_rtlog-generator-1.DAT. Previously, RTLog file names could include a generated pod identifier, such as node_rtlog-generator-6b777f57c-vmrcc.DAT.
Customers that use automated file monitoring, file-name parsing, or downstream integrations based on RTLog file-name patterns should review those processes and update them as needed to account for the revised naming convention.