Create a service process to collect request information and initiate work for a Case,
Incident, or Service Request. The process type determines how Unified Catalog tracks the
interaction, and the configured routing, fulfillment, and service-level agreement settings
determine how teams process the request.
Required Editions
Available in: Lightning Experience
Available in: Enterprise, Unlimited, and Developer editions with
Unified Catalog.
User Permissions Needed
To create service processes:
Unified Catalog Admin
From the App Launcher, search for and select Unified Catalog.
On the Home page, click New, and then select Service
Process.
Alternatively, on the Service Processes tab, click New Service
Process.
On the Create Service Process page, enter a name for the service process and complete the
remaining fields.
To add an image for the service process, click Upload Image.
Alternatively, in Add Image Link, enter the URL of a product image
from an external data source. To include external websites, add the website URLs to the Remote
Sites page and Cross-Origin Resource Sharing (CORS) page. See Configure Salesforce CORS Allowlist.
If you want requestors to use the service process immediately after you save it, mark the
service process as Active.
Select a process type to specify the object that tracks the request through resolution or
fulfillment.
To make submitted field values editable by authorized requestors and fulfillers, select
Allow editing submitted requests. See Unified Catalog Editions and
Permissions for the required permissions.
Updates to submitted service catalog requests don’t support service process attributes
that use list-of-maps attributes.
Note For an existing service process, after you turn on this option, verify the attribute
configurations, regenerate the intake form, and activate it.
Save the service process.
Migrate Service Processes: To move service processes from a sandbox to production or
another target org, use Salesforce CLI. Salesforce CLI packages a service process and its
supporting flows, transforms record IDs, and loads dependencies to preserve the
configuration in the target org. See Salesforce Service Automation CLI Plugin Command
Reference.
¿Resolvió este artículo su problema?
¡Háganos saber cómo podemos mejorar!
Cargando
Salesforce Help | Article
Cookie Consent Manager
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.