Default Order Fulfillment Provider
The Default Order Fulfillment Provider includes these features.
- Predefined payload with order and fulfillment order data, including attribute values
- Fixed integration parameters such as timeouts, credentials, and path
- Modified requests and responses via Omnistudio Integration Procedures
- Asynchronous interaction pattern
- Request and response logging
- Errors via fallout rules
To configure the callout settings for Default Order Fulfillment Provider, see Configuration Steps.
Error Handling
To verify if the callout request was successful, check the status value in the payload. If the status is undefined, then these HTTP codes indicate a successful response.
- 200
- 201
- 202
- 203
- 204
- 205
- 206
- 302
- 304
If the request isn't successful, then the fulfillment step state is marked as Fatally Failed.
Integration Definition Configurations
You can configure these additional features for the integration definition.
-
Select the Save the request and response as attachments to the record checkbox for the integration definition to save request and response payloads as attachments to the Integration Provider Execution record. Content publish limits apply when saving request and response payloads as attachments. Use Shield Platform Encryption for secure storage of sensitive information.
- Define Input and Output Processors for the Integration Definition for the pre-processing of the default order fulfillment request before you send the request to an external system. See Omnistudio Integration Procedures.