ServiceProcess
Parent Type
File Suffix and Directory Location
ServiceProcess components have the suffix .serviceprocess and are stored in the .serviceprocess folder.
Version
ServiceProcess components are available in API version 57.0 and later.
Special Access Rules
Access to the ServiceProcess type requires the AccessToServiceProcess permission.
Fields
| Field Name | Description |
|---|---|
| description |
|
| processLabel |
|
| serviceProcessAttributes |
|
| serviceProcessDependencies |
|
| serviceProcessItemGroups |
|
| shortDescription |
|
| usageType |
|
ServiceProcessAttribute
A custom attribute that stores data associated with a service process. For example, a service process that reverses a fee can have a Fee Type attribute.
| Field Name | Description |
|---|---|
| attributeType |
|
| dataType |
|
| description |
|
| developerName |
|
| fieldIdentifier |
|
| groupApiName |
|
| inputVariableValue |
|
| isRequired |
|
| label |
|
| parentAttribute |
|
| sortOrder |
|
ServiceProcessDependency
A dependent component of the service process, which can be a flow, an OmniScript, an Integration Definition, or a preprocessor Apex class.
| Field Name | Description |
|---|---|
| dependencyReference |
|
| processStepName |
|
| type |
|
ServiceProcessItemGroup
A group of related ServiceProcessAttribute records.
| Field Name | Description |
|---|---|
| apiName |
|
| groupName |
|
| sortOrder |
|
Declarative Metadata Sample Definition
The following is an example of a ServiceProcess component.
1<?xml version="1.0" encoding="UTF-8"?>
2<ServiceProcess xmlns="http://soap.sforce.com/2006/04/metadata">
3 <processLabel>EmailUpdate</processLabel>
4 <usageType>FinancialServices</usageType>
5 <serviceProcessAttributes>
6 <label>EmailAddress</label>
7 <developerName>EmailAddress</developerName>
8 <dataType>Text</dataType>
9 <groupApiName>Info</groupApiName>
10 </serviceProcessAttributes>
11 <serviceProcessDependencies>
12 <dependencyReference>EmailPreprocessor</dependencyReference>
13 <type>PreprocessorApexClass</type>
14 </serviceProcessDependencies>
15 <serviceProcessItemGroups>
16 <apiName>Info</apiName>
17 <groupName>Info</groupName>
18 <sortOrder>1</sortOrder>
19 </serviceProcessItemGroups>
20</ServiceProcess>The following is an example package.xml that references the previous definition.
1<?xml version="1.0" encoding="UTF-8"?>
2<Package xmlns="http://soap.sforce.com/2006/04/metadata">
3 <types>
4 <members>*</members>
5 <name>ServiceProcess</name>
6 </types>
7 <version>57.0</version>
8</Package>Wildcard Support in the Manifest File
This metadata type supports the wildcard character * (asterisk) in the package.xml manifest file. For information about using the manifest file, see Deploying and Retrieving Metadata with the Zip File.
Usage Type
We recommend that you review these considerations before you retrieve or deploy service process metadata.
- If you deploy metadata with the same name as the definition when your service process definition is active, you get an error message. Deactivate the service process definition and try again.
- When your service process definition is inactive, consider these guidelines.
- If a service process definition contains service catalog requests and service catalog request extended attribute values and you deploy metadata with the same name as the definition, you get an error message. You can’t delete or change a service process that has service catalog requests with attribute values in it. Make sure that all records are deleted in service catalog requests and service catalog request extended attribute values before you deploy the metadata.
- If a service process definition contains service catalog requests but doesn’t contain service catalog request extended attribute values and you deploy the metadata with the same name, the deployment works as expected.
- If a service process definition doesn’t contain service catalog requests and you deploy the metadata with the same name, the deployment works as expected.