---
schema_version: "1"
id: fe43dfa0f8132515d0dd36783084c1489b551e8123ac16a4699946aa2f64bae3
title: SalesWorkQueueSettings
collection: legacydeveloper
version: current
locale: en-us
portal_url: https://docs.salesforce.com/legacydeveloper/current/en-us/api_meta/meta_salesworkqueuesettings.md
canonical_url: https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_salesworkqueuesettings.htm
source_site: developer.salesforce.com
content_type: documentation
content_hash: e09822059d4d8a60d7ebbb6e7839953409dddc0f4b0e3312aa95c5b5336eeaf8
description: Represents settings used to customize work queue options for third-party scoring. In Sales Engagement, you can add a custom number field on person accounts, contacts, or leads. Then, use the custom number field to sort the work queue. This type extends the Metadata metadata type and inherits its fullName field.
---
# SalesWorkQueueSettings

Represents settings used to customize work queue options for third-party scoring. In Sales Engagement, you can add a custom number field on person accounts, contacts, or leads. Then, use the custom number field to sort the work queue. This type extends the Metadata metadata type and inherits its fullName field.

## File Suffix and Directory Location

SalesWorkQueueSettings components have the suffix .salesworkqueuesetting and are stored in the salesworkqueuesettings folder.

## Version

SalesWorkQueueSettings components are available in API version 49.0 and later.

## Special Access Rules

You must be a Sales Engagement customer to access this metadata type.

## Fields

<table class="featureTable sort_table" summary="">



          <thead class="thead sorted" align="left">
            <tr>
              <th class="featureTableHeader  " id="d829598e93">Field Name</th>

              <th class="featureTableHeader  " id="d829598e96">Field Type</th>

              <th class="featureTableHeader  " id="d829598e99">Description</th>

            </tr>

          </thead>

          <tbody class="tbody">
            <tr>
              <td class="entry" headers="d829598e93" data-title="Field Name"><span class="keyword parmname">featureName</span></td>

              <td class="entry" headers="d829598e96" data-title="Field Type">string</td>

              <td class="entry" headers="d829598e99" data-title="Description">The feature that the SalesWorkQueueSettings record is configuring. The allowed
                value is <samp class="codeph nolang">ThirdPartyScore</samp>.</td>

            </tr>

            <tr>
              <td class="entry" headers="d829598e93" data-title="Field Name"><span class="keyword parmname">targetEntity</span></td>

              <td class="entry" headers="d829598e96" data-title="Field Type">string</td>

              <td class="entry" headers="d829598e99" data-title="Description">The type that the SalesWorkQueueSettings record is configuring. Possible
                values are:<ul class="ul bulletList">
                  <li class="li"><samp class="codeph nolang">Contact</samp></li>

                  <li class="li"><samp class="codeph nolang">Lead</samp></li>

                  <li class="li"><samp class="codeph nolang">PersonAccount</samp></li>

                </ul>
              </td>

            </tr>

            <tr>
              <td class="entry" headers="d829598e93" data-title="Field Name"><span class="keyword parmname">targetField</span></td>

              <td class="entry" headers="d829598e96" data-title="Field Type">string</td>

              <td class="entry" headers="d829598e99" data-title="Description">The developer name or ID of the custom number field that is used to sort the
                work queue. Custom fields must have a custom number data type.<ul class="ul bulletList">
                  <li class="li">To use Einstein Intelligence Score for lead scoring, use <samp class="codeph nolang">ScoreIntelligence.Score</samp> for the developer
                    name.</li>

                  <li class="li">To remove custom number fields from the work queue, use <samp class="codeph nolang">None</samp>.</li>

                </ul>
              </td>

            </tr>

          </tbody>

        </table>

## Declarative Metadata Sample Definition

The following is an example of a SalesWorkQueueSettings component. The value for targetField is set to 00NRM000001g55D as an example of a custom field ID. Replace this value with the ID of your custom field.

<?xml version="1.0" encoding="UTF-8"?>
<SalesWorkQueueSettings xmlns="http://soap.sforce.com/2006/04/metadata">
    <featureName\>ThirdPartyScore</featureName\>
    <targetEntity\>Contact</targetEntity\>
    <targetField\>00NRM000001g55D</targetField\>
</SalesWorkQueueSettings\>

The following is an example package.xml that references the previous definition.

<?xml version="1.0" encoding="UTF-8"?>
<Package xmlns="http://soap.sforce.com/2006/04/metadata">
    <types\>
        <members\>\*</members\>
        <name\>SalesWorkQueueSettings</name\>
    </types\>
    <version\>49.0</version\>
</Package\>

## Usage

Create one SalesWorkQueueSettings record for each type. For example, suppose that you want to create a work queue to sort leads by your custom field called customLeadScore. Create a SalesWorkQueueSettings record and set featureName to ThirdPartyScore, targetEntity to Lead, and targetField to customLeadScore.

## 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](https://developer.salesforce.com/docs/atlas.en-us.264.0.api_meta.meta/api_meta/file_based_zip_file.htm).