Industries Common Resources Developer Guide

Industries Common Resources
AI Accelerator and Scoring Framework
Action Launcher
Actionable List Members
Actionable Segmentation
AI Relationship Research
Business Rules Engine
Collections and Recovery
Context Service
Criteria-Based Search and Filter
Data Processing Engine, Batch Management, and Monitor Workflow Services
Digital Lending
Discovery Framework
Decision Explainer
Einstein Relationship Insights
Einstein Standard Invocable Actions
Engagement
Group Membership and Households
Identity Verification
Intelligent Document Reader
Intelligent Form Reader
Interest Tagging
Omnistudio
Outcome Management Developer Guide
Outreach List
Process Compliance Navigator
Record Alerts
Record Rollup Definitions
Scheduled Reminders
Sentiment Insights
Service Process Studio
Stage Management
Timeline
Unified Catalog
Unified Catalog Business APIs
Salesforce Service Automation CLI Plugin Command Reference
sf
service-process Commands
service-process deploy
service-process list
service-process retrieve
Help for sf Commands
Unified Catalog Apex Reference
Virtual Calls
Associated Objects
IndustriesSettings
Industries Object Access by Community License
Access Industries Features Deployed Using Managed Packages
PDF

Note: This release is in preview. Features described here don’t become generally available until the latest general availability date that Salesforce announces for this release. Before then, and where features are noted as beta, pilot, or developer preview, we can’t guarantee general availability within any particular time frame or at all. Make your purchase decisions only on the basis of generally available products and features.

service-process Commands

Deploy, retrieve, and list Unified Catalog Service Processes in an org. A Unified Catalog Service Process defines a service automation workflow consisting of attributes, intake flows, fulfillment flows, and preprocessors.

service-process deploy

Deploy the Unified Catalog service process packaged as a ZIP file (typically generated by the `service-process retrieve` CLI command) into a target Salesforce org.

This command deploys supported Service Process metadata, including:

  • Service Process Attributes (anchor, custom, context)
  • Intake flow
  • Fulfillment flow
  • Preprocessor reference

All other dependencies must already exist in the target org. Examples of these dependencies include:

  • Apex classes used in flows
  • Apex classes referenced by the preprocessor
  • Unified Catalog context definition allowlisting

If any required dependency is missing in the org, the deployment fails.

Examples for service-process deploy

Deploy a Service Process from a ZIP file to an org with alias "prod":

1sf service-process deploy --input-zip ./service-process.zip --target-org prod

Deploy while linking an existing intake flow:

1sf service-process deploy --input-zip ./service-process.zip --target-org prod --link-intake

Deploy while linking existing intake and fulfillment artifacts:

1sf service-process deploy --input-zip ./service-process.zip --target-org prod --link-intake --link-fulfillment

Parameters

--json
Optional

Format output as json.

Type: boolean
--flags-dir FLAGS-DIR
Optional

Import flag values from a directory.

Type: option
-o | --target-org TARGET-ORG
Required

Username or alias of the target org. Not required if the `target-org` configuration variable is already set.

Type: option
--api-version API-VERSION
Optional

Override the api version used for api requests made by this command

Type: option
-z | --input-zip INPUT-ZIP
Required

Path to the ZIP file that contains the Service Process metadata to deploy.

You typically generate this ZIP file with the `service-process retrieve` CLI command. The ZIP file contains the Service Process definition and supported metadata.

Type: option
--link-intake
Optional

Link an existing intake flow instead of deploying a new one.

When specified, the command links the existing intake flow in the target org instead of deploying the intake flow from the ZIP file.

Type: boolean
--link-fulfillment
Optional

Link an existing fulfillment artifact instead of deploying one.

When specified, the command links an existing fulfillment artifact (flow or flow orchestrator) in the target org instead of deploying the fulfillment flow from the ZIP file.

Type: boolean

service-process list

List the Unified Catalog Service Process records from the specified org and display their **Name** and **Id** in a human-readable table.

To ensure predictable performance and avoid excessively large output, the command limits the number of records returned. If the maximum limit is reached, the results are truncated and a warning is displayed.

Use the `--limit` flag to control the maximum number of Service Processes returned.

Examples for service-process list

List the available Service Processes in the org with alias "devSandbox"; use the default limit:

1sf service-process list --target-org devSandbox

List up to 100 Service Processes:

1sf service-process list --target-org devSandbox --limit 100

Parameters

--json
Optional

Format output as json.

Type: boolean
--flags-dir FLAGS-DIR
Optional

Import flag values from a directory.

Type: option
-o | --target-org TARGET-ORG
Required

Username or alias of the target org. Not required if the `target-org` configuration variable is already set.

Type: option
--api-version API-VERSION
Optional

Override the api version used for api requests made by this command

Type: option
--limit LIMIT
Optional

Maximum number of Service Processes to return.

Allowed range is 1–2000. Default is 1000.

Type: option
Default value: 1000

service-process retrieve

Retrieve a Unified Catalog Service Process from the specified Salesforce org and package it into a ZIP file. You can then deploy this ZIP file into another org.

The command downloads the Service Process definition, identifies supported dependent metadata, retrieves those components, and bundles everything into a deployable artifact.

Supported metadata retrieved by this command includes:

  • Service Process Attributes (anchor, custom, context)\
  • Intake flow
  • Fulfillment flow
  • Preprocessor reference

Other dependencies, such as Apex classes used by flows or preprocessors, aren't retrieved and must already exist in the target org before deployment.

Examples for service-process retrieve

Retrieve a Service Process using its ID from the org with alias "devSandbox":

1sf service-process retrieve --service-process-id 0SPxx0000008ABC --target-org devSandbox

Retrieve a Service Process and write the artifacts to a custom directory:

1sf service-process retrieve --service-process-id 0SPxx0000008ABC --target-org devSandbox --output-dir ./sp-artifacts

Parameters

--json
Optional

Format output as json.

Type: boolean
--flags-dir FLAGS-DIR
Optional

Import flag values from a directory.

Type: option
-i | --service-process-id SERVICE-PROCESS-ID
Required

ID of the Unified Catalog Service Process to retrieve from the source org.

Type: option
-d | --output-dir OUTPUT-DIR
Optional

Directory where the retrieved Service Process artifacts and the generated ZIP file are written. If not specified, artifacts are written to `./service-process`.

Type: option
-o | --target-org TARGET-ORG
Required

Username or alias of the target org. Not required if the `target-org` configuration variable is already set.

Type: option
--api-version API-VERSION
Optional

Override the api version used for api requests made by this command

Type: option