Queues a predefined job workflow for execution. Provide the workflow automation ID, optional concurrency scope, and any workflow-specific parameters. On success, returns a job ID you can use to check job status.
Add an Authorization header to authenticate requests originating outside of Zilliant's internal network. Set the header to Authorization: OAuth <tokenResponseBase64>.
<tokenResponseBase64> is the Base64-encoded entire JSON response body returned by the Salesforce OAuth token endpoint. Encode the full JSON payload, not only the access_token field.
For details, read Request an access token.
OAuth host for your environment. Use it for all requests that originate outside Zilliant’s internal network. For details, read X-Forwarded-Host header in Introduction.
These job workflows are defined in your customer environment by Zilliant staff. They will provide the information needed to correctly populate the JSON body.
Run the PublishListPrices workflow with a scope and one argument.
{
"descriptor": "PLATFORM_CUSTOM_WORKFLOW",
"scope": "scope2",
"parameters": {
"WORKFLOW_AUTOMATION_ID": "PublishListPrices",
"foo": "bar"
}
}Workflow descriptor identifier.
Concurrency scope for the workflow. If omitted, the job runs in a system-managed serial queue with other unscoped jobs. If provided, jobs with different scopes may run in parallel, while jobs sharing the same scope are queued. Environment configuration is required to enable parallel runs; otherwise a 409 is returned when another job with the same scope is in progress.
Workflow parameters. Must include WORKFLOW_AUTOMATION_ID. You can also include additional stored procedure arguments expected by the workflow's extension points.
Unique Automation ID of the predefined job workflow to run.
Optional stored procedure arguments (key-value pairs) used by extension points within the workflow. If provided, these override default values defined in the workflow's stored procedures.
The job workflow was queued successfully. Returns the jobId.
Unable to process the JSON body.
Authentication error, for example, invalid Authorization header or X-Forwarded-Host header value.
A job with the same scope is already in progress and the environment is not enabled for parallel runs.
Service failed to process request.