You are here:
Get Service Process Details Action
This action retrieves custom attribute values and related product requests from a submitted service process for use in its fulfillment flow.
You are here:
This action retrieves custom attribute values and related product requests from a submitted service process for use in its fulfillment flow.
In Flow Builder, add an Action element to your flow. In the New Action window, search for your service process name or Service Process Details, and then select the Get Service Process Details action for the service process you want. The action name in the catalog can include the service process name and product ID.
Unified
Catalog generates a distinct Get Service Process Details action for each service process. The
action name uses the format {ServiceProcessName}-{ProductId18}.
Use values from earlier in the flow to set the inputs for the action.
| field | description |
|---|---|
| Process Type ID | Required. The ID of the Case, Incident, or Service Request record associated with the service process. |
Each attribute defined for the service process appears as its own output parameter. The label and API name of each output match the attribute configuration for that service process. Dynamically generated attribute outputs aren’t listed individually.
| field | description |
|---|---|
| Related Product Requests | The collection of related product requests associated with the service request. Each item includes identifiers and names for the related product request, parent catalog request, and related child product. |
The Get Service Process Details action runs only in flows. You can’t invoke it through Apex,
REST API, Agentforce, Prompt Studio, Einstein Bots, or frameworks such as
InvocableActionService.

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 are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security 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 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.