OM Standard: Request and Response Data Storage

When a callout's Request and Response fields contain too much data, database performance slows down. To avoid that issue, you can instead have Order Management store request and response data in a big object, somewhere else, or not store it at all.

In release Winter '22 and earlier, Request and Response field information is stored in the Orchestration Item fields. From release Spring '22, you can edit the OrchestrationItemLog custom setting to store request and response information in a big object, or turn off storing the data. See OM Standard: Configure Request and Response Storage in Custom Settings.

Note

The "BigObject" and "Off" settings only work if the OrchestrationMode custom setting is set to "PlatformEvents". If you've done a new a installation of Spring '22, then "PlatformEvents" is already set by default. Otherwise, you might have to change it. See High Volume Platform Events (HVPE) for OrchestrationOM Standard: Platform Events for Orchestration and Order Management Standard: Edit the OrchestrationMode Custom Setting.

Here's some important information:

• If you've done a new installation of release Spring '22 or later, the OrchestrationItemLog custom setting value is set to "Off" by default, and request and response information isn't stored.

• If you've upgraded to Spring '22, the OrchestrationItemLog custom setting is set to "OrchestrationItem" by default. In this instance, the storing of request and response information remains unchanged from previous versions (and is stored in the Orchestration Item fields, in the Interaction Details section).

• If the OrchestrationItemLog custom setting is set to "BigObject", the information is shown in the Orchestration Item Log. In this instance, the Request and Response fields of the Orchestration Item are blank. These fields continue to show data for earlier Orchestration Items (items created before changing the setting).

• You can store request and response information in a different location by overriding the behavior of the default integration adapter behavior. See the void persistOrchestrationItemLogs method in Methods Included with XOMEnhancedSystemInterface.