Previous What's new in the platform

Sterling Order Management System integration with Sterling Inventory Visibility (inventory management system (phase 2)) now uses Availability by date breakup and Reservations by date breakup features that are available in Sterling Inventory Visibility, which improves inventory allocation for future inventory and time sensitive items.

For more information, see Order fulfillment by using Availability by date breakup.

The YFS_CHARGE_CATEGORY table is now extensible so that you can add new columns and update values in the database.

A new getExportDataDetails API is added to retrieve data from the YFS_EXPORT table. For more information, see Javadoc.

Some third-party libraries with high and critical vulnerabilities are removed as they are not used in the Sterling Order Management System application. If you need any further information, contact IBM product support.

• Enabling data compression for columns

  Sterling Order Management System is enhanced to provide a configuration to compress data of compression supported columns. By using the configuration, you can compress the column data anytime without having to customize, rebuild, and redeploy Sterling Order Management System. For more information, see Guidelines to add support for data compression of columns.

• History data compression support

  A new property is introduced to enable data compression on all the compression supported columns when data is written to history tables. The property ensures that the data that is written in history tables is compressed even if compression is not enabled for the compression supported columns in transaction table. For more information, see history compression properties.

• YFS_IMPORT and YFS_EXPORT tables compression support

  Sterling Order Management System is enhanced to support compression for MESSAGE column of YFS_IMPORT and YFS_EXPORT tables.

• Order Audit Delete Purge agent

  The new Order Audit Delete Purge agent extends the capability of Order Purge agent by deleting the order audit records from Sterling Order Management System before the Order Purge agent purges the order. For more information, see Order audit delete purge.

• Order Purge agent

  The behavior of the Order Purge agent is enhanced to support configuration to delete the order audit data rather than moving it to history table, and publish the order audit data through a user exit. For more information about configuring delete of order audit, see Order purge agent.

For Order Audit Delete Purge and Order Purge agents, the Sterling Order Management System provides YFSBeforeOrderAuditPurgeUE user exit that publishes the order audit records being deleted from the application on purge of an order. Implement the user exit, if you want to store order audit records outside of Sterling Order Management System for future reference. For more information, see Javadoc.

• A new criteria parameter is added to the YFS_EXPORT purge agent to ignore the status value and purge all records. For more information, see Export table purge.
• A new getExportDataList API is added to retrieve data from the YFS_EXPORT table. For more information, see Javadoc.

If the database contains any compressed data, the DB Query Client decompresses the compressed data and displays in the result or exports the data.

• A new property is added to monitor the available free space in the SFTP server that is required to run the data extract agent. For more information, see Configuring the data extract.
• Additional monitoring to verify that the duplicate agent criteria are not running the data extract agent simultaneously. For more information, see Data extract agent.
• All tables in Sterling Order Management System are now valid tables by default and you do not have to add any tables manually as a data extract valid table. For more information, see Data extract configuration service.

The traceable components now come with a time to live configuration and the tracing would no more happen indefinitely. While creating the traceable component configuration, you can pass the time to live (TraceTTL) attribute as part of the modifyTraces API. If this TTL configuration is not passed, it is defaulted to 10 minutes. For more information, see Extending trace expiry time for logs.

When you deploy the 22.3 version of Sterling Order Management System, all your active trace components might stop because the default TTL to retain the trace is 10 minutes. You can enable the trace again. For more information, see Enabling or disabling trace for logs.

The performance of Sterling Order Management System is improved in providing real-time updates to data-tier of the Order Hub metrics and the Store Manager dashboard. This update also improves the upkeep of backend database tables that are used for real-time dashboards in the Sterling Order Management System user interfaces - Order Hub and IBM Sterling Store Engagement.

You can now configure the application to support OIDC provider login from the developer toolkit environment. For more information, see Supporting OIDC provider login in developer toolkit environment.

Some third-party libraries are upgraded to mitigate high and critical vulnerabilities. If you need any further information about these upgrades, contact IBM product support.

The workload segregation feature is now available for task queue agents to segregate workload by creating jobs with different segregation patterns. You can configure segregation patterns in the agent criteria of the task queue agents to process matching jobs.

The workflow segregation feature helps you process jobs with different workload and separate business flows in separate agent servers. You also have a flexibility to prioritize and run a particular type of workload with required resources to scale up the agent processing.

For more information, see Workload segregation for task queue agents.

New attributes are made available to apply different business flows for order processing.

These indicators are also available as condition builder attributes so that you can easily add conditions in your order processing model. For more information about these attributes, see Condition builder attributes.

When Sterling Order Management System APIs are called through the REST framework, if the input is in the JSON format, the output is automatically converted to JSON. In some such scenarios, it cannot be determined whether a child element in the XML is an array item or a child object. To avoid these inconsistencies, the REST framework is enhanced so that you can now enforce an XPath in the XML to define whether the child element is an array item or a child object.

For more information, see Specifying output format for JSON.

• Occurs within first 30 minutes of upgrade in Development, QA, MC, and Pre-production environments
• No outage in Production

• Occurs within first 30 minutes of upgrade
• No outage in other environments such as Development, QA, MC, and Production

The application uses the log4j2 (2.17.1) utility for logging. The log4j2 utility writes trace and debug information to a log file. You can modify the logging parameters in the log4j2 configuration file to control the location and level of the log files. For more information, see Migrating to log4j2 and Customizing log4j2 configuration.

Sterling Order Management System is the master for ship nodes, which includes distribution centers, warehouses, stores, and drop ship nodes. To manage the inventory in Adobe Commerce as part of the integration, ship nodes in Sterling Order Management System must be synced with Adobe Commerce. For more information, see Synchronizing ship nodes.

Improved the data extract for handling backup database while syncing data during the database maintenance and long running reorganizations.

Orders that placed in Adobe Commerce are created in Sterling Order Management System. For orders that are marked as pickup from store, Adobe Commerce notifies the customer when the order is ready for pickup. When the order is picked by customer and the order is fulfilled by IBM Sterling Store Engagement, the order is marked as shipped in Sterling Order Management System. A notification is sent to Adobe Commerce, which marks the order as complete and an invoice is triggered in Adobe Commerce. For more information, see In-store order pickup update.

Orders that are returned by the Adobe Commerce customers are authorized in Adobe Commerce. The return order authorization in Adobe Commerce is called Return Merchandise Authorization (RMA). The authorized returns are sent from Adobe Commerce to Sterling Order Management System over a synchronous call. For more information, see Returning orders.

The inventory synchronization is enhanced to support Sterling Inventory Visibility events for enabling more frequent inventory updates to Adobe Commerce. For more information, see Activity-based sync mode.

Use the developer toolkit to easily customize Order Hub by creating new applications or modifying existing applications. The toolkit provides all the source code that renders the Order Hub application menus and scripts to automate processes for a quick set up. You can use the source code as a starting point for your customizations. For more information about how to set up Order Hub in the toolkit, see Overriding the default Docker Compose properties. For more information about customization, see Customizing Order Hub.