Submit Order Action

Submit an order to Dynamic Revenue Orchestrator (DRO) for fulfillment.

By using the Submit Order action, you can perform:

Order decomposition
Fulfillment orchestration that’s driven through message queues
Dynamic plan composition that’s based on the incoming order

This action is available in API version 61.0 and later.

Special Access Rules

The Submit Order action is available in Enterprise, Unlimited, and Developer Editions of Revenue Cloud. See the required permissions to access and call this invocable action.

Supported REST HTTP Methods

URI: /services/data/v64.0/actions/standard/submitOrder
Formats: JSON, XML
HTTP Methods: POST
Authentication: Authorization: Bearer token

Inputs

Input	Details
orderId	Type string Description Required. ID of the order to submit to DRO.
callType	Type string Description Optional. Mode that the order intake must be processed in. Valid values are: `Synchronous` `Asynchronous` The default value is `Asynchronous`.
contextId	Type string Description Optional. ID of the hydrated context. See Context Service.

Outputs

Output	Details
errorCode	Type string Description Error code for the failed request, if any.
fulfillmentPlanId	Type string Description ID of the orchestrated fulfillment plan that’s generated. Returned only if the callType value is `Synchronous`.
requestId	Type string Description Unique ID of the invocation request that helps identify a single request.
submitStatus	Type string Description Submit status of the invocation request. Valid values are: `SUCCESS` `ERROR` `SUBMITTED` `REJECTED`
usedContextId	Type string Description Hydrated context ID that’s used in this request, which can be different from the contextId input.

Example

POST

This example shows a sample request.

{
    "inputs": [
        {
            "orderId": "801RM0000007yGaYAI",
            "callType": "Synchronous"
        }
    ]
}

This example shows a sample response when the call type is synchronous.

[
    {
   "actionName":"submitOrder"
   "errors":NULL
   "invocationId":NULL
   "isSuccess":true
   "outputValues":{
   "requestId":"a161cfda-868c-41d2-b589-7c7d7ff2d4c1"
   "submitStatus":"SUCCESS"
   "usedContextId":"e275e930923106ee7e39cbfa232e38252bd4d63f4ea2dd956b7301e243554134"
   "fulfillmentPlanId":"13VZM00000000062AA"
}
]

This example shows a sample response when the call type is asynchronous or isn’t specified.

[
{
    "actionName": "submitOrder",
    "errors": null,
    "isSuccess": true,
    "outputValues": {
    "submitStatus": "SUBMITTED"
    "requestId": "a161cfda-868c-41d2-b589-7c7d7ff2d4c1"
}
}
]

This example shows a sample response when a validation error occurs.

[
    {
    "actionName": "submitOrder",
    "errors": [
    {
        "statusCode": "UNKNOWN_EXCEPTION",
        "message": "Missing required input parameter: orderId",
        "fields": []
     }
  ],
        "invocationId": null,
        "isSuccess": false,
        "outputValues": {
          "requestId": "4c7d8ebb-6b0b-4852-a8a0-b67e0d36a73e",
          "errorCode": "DRO_INTERNAL_ERROR"
        },
    }
]

Explainability Action Logs

To troubleshoot or debug errors, retrieve a list of explainability action logs. See Action Logs.

Get logs for order intake

This resource example includes sample query parameters to retrieve the action logs for an order intake.

https://yourInstance.salesforce.com/services/data/v64.0/connect/decision-explainer/action-logs?applicationSubType=DroSubmit&applicationType=7&processType=DroSubmit&primaryFilter=801xx000003GYzvAAG