In Salesforce Order Management, release held fulfillment order capacity at one or more
locations. This action decreases the held capacity of a location without increasing the assigned
fulfillment order count. Use this action when canceling a fulfillment order assignment to free
up capacity at one or more locations.
allOrNothing —(Optional) Controls whether a single failed
request cancels all other requests in the list (true) or
whether some requests can succeed if others fail (false).
The default value is false.
capacityRequests —This field is a list of Apex-defined
variables of class ConnectApi.CapacityRequestInputRepresentation. Each of the variables
represents a request to release capacity for one fulfillment order at one
location, and includes these fields:
actionRequestId —Unique string that identifies the
request. Can be a UUID. Use the action request IDs in response data to
identify which requests succeeded or failed.
locationId —ID of the location associated with the
request.
Store Output Values
Use output values later in the flow. The values are
assigned when the capacity properties are updated.
Output Parameter
Description
Fulfillment Order Location Release Held Capacity
Output
actionRequestId —Unique string that identifies the
original capacity request.
error —This field is an Apex-defined variable of
class ConnectApi.ErrorResponse, which includes these fields:
errorCode —Error code, if the request returned an
error.
message —More error detail, if available.
success —Indicates whether the request was successful
(true) or not (false).
Did this article solve your issue?
Let us know so we can improve!
Loading
Salesforce Help | Article
Cookie Consent Manager
General Information
Required Cookies
Functional Cookies
Advertising Cookies
General Information
We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required Cookies
Always Active
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional Cookies
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising Cookies
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.