Catalog requests are created when a Service Catalog customer submits a request for a
catalog item. Requests let customers follow the status of a requested item and let you report on
requests.
A request is linked to other Salesforce records through CatalogReqRelatedItem records.
CatalogRequest and CatalogReqRelatedItem are data objects.
Requests are linked to other Salesforce records and are created in an open state under these
conditions.
The fulfillment is based on a screen flow.
The fulfillment provides an output variable named SvcCatalogRelatedRecordIDs.
The SvcCatalogRelatedRecordID has the type Text Collection.
Values generated from SvcCatalogRelatedRecordID are valid Salesforce record IDs of
supported objects.
Catalog requests can be tracked using the SvcCatalogRequestID input variable, which fills in
as a catalog request executes. You can reference the SvcCatalogRequestID in cases, or use it
to track the status of incomplete catalog requests. You can view the status of an initialized
request. The three statuses for an initialized catalog request are Request Created, Execution
Started, and Execution Completed.
Both standard and custom objects can support catalog requests, but the supporting object has
to be able to be the target of a custom lookup relationship. The relationship between the
request and the object is defined in the underlying screen flow of the fulfillment related to
the catalog item the request is based on.
Additional user questions with an attachment type become related to the request and its
related items via a ContentDocumentLink record.
You can share catalog requests across users in the same Salesforce org. You must have the
correct permission sets to view shared catalog requests.
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.
