Oracle® Retail Xstore Office Cloud Service Administration Guide Release 19.10 F89727-01 |
|
![]() Previous |
![]() Next |
This chapter describes customization and extension considerations.
Core application code - no customization to the core application code is permitted. No access to the database or data model is permitted.
Data model extensions are allowed. Similar to on-premises installation, extension tables (for example, trn_trans_p) can be used to add additional virtual columns to any base table.
Custom tables can be created by uploading DTX files via the Xadmin UI.
Data Model Customizations are read and applied at runtime without a server restart.
Configurations customizations – no customer specific war is produced. The following portions of the customer overlay are uploaded through the Xadmin UI:
Files to support menu configuration
MenuConfig.xml
ActionConfig.xml
File to enable use of additional extension tables (%_p)
PmTypeMappingConfig.xml
Files to enable use of system configuration
SysConfig.xml (formerly known as SystemConfig.xml)
SystemConfigMetadata.properties
Query Definition - The new query type (DTXQL) should be used for all queries customizations in XOCS.
SQL and DtxQueryHandler queries are deprecated as of 18
SQL and DtxQueryHandler queries in overlays will not work with XOCS
All customizations are preserved automatically as part of the application upgrade process.
Reports customization is not available in XOCS 18.0 and 18.1.
Starting with XOCS 19.0 any custom reports are added through the Xadmin UI. The report definitions are preserved automatically as part of the application upgrade process.
Files to support report customization that can be loaded through the Xadmin UI are:
Query configs (version1/query/*.xml)
Report configs (version1/report/*.xml)
Report definitions and layouts (*.xdt and *.rtf)
Consult the Oracle Retail Xstore Office Cloud Service User Guide for all customizations capabilities.