Use an appointment bundle restriction policy to define restriction fields so that only
service appointments with the same field values can be bundled together. Use the default policy,
or create multiple restriction policies. For automatic bundling, you must have at least one
restriction policy.
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.
User Permissions Needed
To create items:
Customize Application
If your service appointments have custom fields, make sure to give the fields read access.
See Appointment Bundling Limitations.
From Setup, in the Quick Find box, enter Users, and then select
Permission Sets.
Click Field Service Integration.
Click Object Settings.
Click Service Appointment.
For each custom field, select Read Access.
In the Appointment Bundle Policy, go to the Related tab.
In the Appointment Bundle Restriction Policies panel, click
New.
Give the policy a unique name.
For Restriction Field Name, select the bundle member service appointment field used to
apply the restriction.
Considerations:
Only service appointments with the same value can be bundled together.
The fields in the list are service appointment fields, not work order fields. The only
exception is Skill Requirements, which is a work order field.
Unsupported lookup fields don’t appear in the list of fields for selection.
To allow bundling service appointments that have an empty restriction field with service
appointments that have a value in the restriction field, select Allow
Empty.
To apply this restriction with manual bundling, select Restrict in Manual
Mode.
If the Restriction Field Name is of type Date/Time, you can restrict the bundle based on
the calendar date rather than the time of day by selecting Restrict by Date
Only.
To apply this restriction to automatic bundling, select Restrict in Automatic
Mode.
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.