The Match Fields work rule type matches a service appointment field with a service
resource field. It’s a great way to enforce requirements based on custom fields. If you're using
Enhanced Scheduling and Optimization, the Match Fields work rule is a Field Service database
work rule type. If you're not using Enhanced Scheduling and Optimization, this is an Apex work
rule type.
Required Editions
Available in: both Salesforce Classic (not available in all orgs) and Lightning
Experience
The Agentforce Field Service and Operations core features, managed package, and
mobile app are available in Enterprise, Unlimited, and Developer
Editions.
This is a Field Service managed package feature.
Note Use the Match Fields work rule for direct one-to-one field comparisons between a service
appointment and a service resource, for example, matching required skills. If you must compare a
field from the service appointment to multiple properties on the service resource, we recommend
you use the Extended Match work rule type, which provides enhanced
flexibility and performance.
Work rules of this type contain three key settings.
Field Name
Description
Service Property
The API name of the field on service appointments that helps define the scheduling
requirement. All primitive data types are supported. When using Enhanced Scheduling and
Optimization, if the service appointment matching field is empty, all service resources are
considered valid.
Boolean Operator
The required relationship between the Service Property and the Resource Property. For
example, if =, a service appointment’s Service Property value must
equal a service resource’s Resource Property value for the resource to be assigned to the
appointment.
Resource Property
The API name of the field on service resources that helps define the scheduling
requirement. All primitive data types are supported. When using Enhanced Scheduling and
Optimization, if the resource matching field is empty, then the service resource isn’t a
valid candidate for any service appointment with matching field requirements.
To control which fields are available as resource and service properties:
Add the API name of any field as a picklist value in the Resource Property or Service
Property fields on the Work Rule custom object in Setup.
Make sure that the value has been enabled for the record type.
NoteMatch Fields work rules are supported for global, in-day, and
resource optimization only when you're using Enhanced Scheduling and Optimization.
Create work rules from the Work Rules tab. To view or add work rule
fields open the Object Manager in Setup and select the
Work Rule custom object. Add work rules to a scheduling policy from
the Customize Scheduling Policies page in Guided Setup or from the
Scheduling Policy Work Rules related list on a scheduling policy.
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.