For this scenario, Salesforce Field Service should use the Reshuffle action. Reshuffle is designed to insert important work into an already populated schedule by moving lower-priority appointments to other times, days, or resources as allowed by the Scheduling Policy.

Salesforce Field Service treats the Service Appointment as the primary unit of scheduling. Scheduling Policies combine Work Rules, which determine whether a resource or time slot is valid, with Service Objectives, which score valid alternatives against business priorities. The selected configuration therefore has to operate at the scheduling layer rather than merely changing descriptive fields on the parent Work Order.

The alternatives address different parts of the Field Service model. A normal reschedule changes a selected appointment but does not provide the same schedule-wide rearrangement around the incoming high-priority work; custom Apex is unnecessary.

This approach keeps the implementation aligned with the standard Field Service data model and avoids unnecessary customization. Study Guide reference: Managing Scheduling and Optimization — Reshuffle; appointment priority; in-day schedule adjustment.

The requirement is best implemented with Arrival Window Start and Arrival Window End. Arrival windows are the customer-facing expectation for when a technician is expected to arrive. They provide a practical range while allowing dispatchers operational flexibility if travel or earlier appointments change during the day.

Operationally, the goal is to preserve schedule integrity while minimizing manual intervention. Field Service should be allowed to use the standard scheduling engine wherever possible so that resource availability, travel, appointment constraints, priorities, and territory context remain consistent across manual and automated scheduling actions.

The alternatives address different parts of the Field Service model. Scheduled Start and Scheduled End are internal scheduling values and may move as the schedule is optimized, so sharing them as hard customer commitments is usually inappropriate.

This approach keeps the implementation aligned with the standard Field Service data model and avoids unnecessary customization. Study Guide reference: Managing Scheduling and Optimization — Service Appointment arrival windows; customer communications.

For this scenario, Salesforce Field Service should use Products and Price Books. The consumed part is a Product, and pricing is supplied through Price Book Entries so the Product Consumed record can carry list price, unit price, discounts, and billing context.

Using the standard inventory objects keeps quantity, location, serial number, price, and service history aligned. Custom fields or improvised notes may capture text, but they do not participate in the native stock, fulfillment, consumption, and reporting processes that Field Service provides.

The alternatives address different parts of the Field Service model. Assets identify installed customer equipment, while Opportunity Line Items belong to the sales process and custom objects are unnecessary for standard Field Service part pricing.

The standard inventory model also keeps planned demand, stock position, movement, actual consumption, and pricing available for reporting without duplicating the same information in custom records.

This approach keeps the implementation aligned with the standard Field Service data model and avoids unnecessary customization. Study Guide reference: Managing Inventory — Products Consumed; Products; Price Books; pricing.

The correct configuration is the Match Territory Work Rule. Match Territory filters candidate Service Resources so that only members of the Service Appointment ' s Service Territory qualify. It should be included in the Scheduling Policy when work must remain within territory membership.

In scheduling design, it is important to distinguish eligibility from preference. Work Rules filter candidates that do not satisfy hard constraints such as territory, availability, skills, or boolean conditions, while Service Objectives rank the remaining options. Dispatcher Console actions then use that policy logic to place, move, or dispatch appointments in a controlled way.

The alternatives address different parts of the Field Service model. Resource Availability checks whether a candidate can work at the required time; it does not establish that the resource belongs to the same territory.

This approach keeps the implementation aligned with the standard Field Service data model and avoids unnecessary customization. Study Guide reference: Managing Scheduling and Optimization — Scheduling Policies; Match Territory Work Rule; candidate eligibility.

The requirement is best implemented with a separate Work Type and Work Order Line Item for each installation step. Each installation step has different skills and parts, so each line item should use the Work Type that defines the requirements for that specific step. This keeps one overall Work Order while preserving task-level qualification and material needs.

Good Work Order design also preserves the distinction between planned work and execution results. Products Required, requirements, and task structure should be established before service; Products Consumed, actual times, signatures, and completion statuses then record what actually happened in the field.

The alternatives address different parts of the Field Service model. One Work Type on the parent would not differentiate the three steps, while separate Work Orders or a hierarchy would over-fragment a single installation project.

This approach keeps the implementation aligned with the standard Field Service data model and avoids unnecessary customization. Study Guide reference: Managing Work Orders — Work Types; Work Order Line Items; step-specific skills and products.

Candidates/Get Candidates, Bulk Schedule, and Schedule is the appropriate Field Service design. These actions use the Scheduling Policy to evaluate resource eligibility and scheduling quality. Candidates exposes options, Bulk Schedule handles multiple selected appointments, and Schedule automatically places an individual appointment under policy logic.

In scheduling design, it is important to distinguish eligibility from preference. Work Rules filter candidates that do not satisfy hard constraints such as territory, availability, skills, or boolean conditions, while Service Objectives rank the remaining options. Dispatcher Console actions then use that policy logic to place, move, or dispatch appointments in a controlled way.

The alternatives address different parts of the Field Service model. Change Status to Dispatch does not perform policy-based scheduling, and manually editing a resource assignment bypasses the scheduling engine ' s candidate evaluation.

This approach keeps the implementation aligned with the standard Field Service data model and avoids unnecessary customization. Study Guide reference: Managing Scheduling and Optimization — Dispatcher Console scheduling actions; Scheduling Policies.

For this scenario, Salesforce Field Service should use the Work Order-to-Asset relationship. Assets represent specific customer-installed products. Relating a Work Order to the Asset records the service history against the exact installed unit and supports lifecycle, maintenance, and reliability analysis.

An Asset represents a customer-specific installed instance of a Product, which is why lifecycle, service history, hierarchy, installation dates, replacements, and component relationships should be modeled on Assets rather than on generic Product records. Work Orders can then reference the exact installed equipment being serviced.

The alternatives address different parts of the Field Service model. Products are catalog definitions rather than the customer-specific installed instances that need a service history.

This keeps the installed-base history tied to the exact customer equipment rather than only to the generic product definition, which is essential for maintenance and lifecycle reporting.

This approach keeps the implementation aligned with the standard Field Service data model and avoids unnecessary customization. Study Guide reference: Managing Assets — Assets; Work Orders; installed-base service history.

The correct configuration is Service Territory Member. The Service Territory Member record links a Service Resource to the territory in which the resource works. That relationship is fundamental to territory-based scheduling and sharing calculations for appointments assigned to the resource.

Field Service access combines Salesforce object permissions with Field Service permission-set licenses and managed sharing. The correct design applies least privilege: technicians, agents, dispatchers, contractors, and administrators should receive only the capabilities required for their operational persona.

The alternatives address different parts of the Field Service model. User Territory links users such as dispatchers to territory access groups; it serves a different persona and sharing purpose than the resource-territory membership relationship.

This approach follows least-privilege design and keeps access changes maintainable as resources, territories, assignments, or user responsibilities change.

This approach keeps the implementation aligned with the standard Field Service data model and avoids unnecessary customization. Study Guide reference: Permissions and Sharing — Service Territory Members; resource-territory sharing.

a Product Request related to the Work Order is the appropriate Field Service design. When damaged van stock must be replaced for an upcoming job, the Product Request should be tied to the Work Order (or a line item where appropriate) so inventory personnel can see the job dependency and fulfill the required part.

Using the standard inventory objects keeps quantity, location, serial number, price, and service history aligned. Custom fields or improvised notes may capture text, but they do not participate in the native stock, fulfillment, consumption, and reporting processes that Field Service provides.

The alternatives address different parts of the Field Service model. Work Types are templates, Service Reports document completed work, and Service Appointments represent the visit rather than the primary transaction for requesting job inventory.

This approach keeps the implementation aligned with the standard Field Service data model and avoids unnecessary customization. Study Guide reference: Managing Inventory — Product Requests; Work Orders; van-stock replenishment.

The correct configuration is Signature Types and Signature Blocks on the Service Report Template. For multiple signatures, define the relevant Signature Types and place a separate Signature Block for each type on the Service Report Template. The technician can then collect the required approvals when the report is generated in Field Service Mobile.

When comparing Salesforce Mobile with Field Service Mobile, the latter should be treated as an operational field-work client rather than a generic CRM client. Its offline capabilities, appointment-centric experience, signature/report functions, geolocation controls, and technician-specific actions are the features that should drive the configuration decision.

The alternatives address different parts of the Field Service model. Separate Service Reports, custom fields, or a custom Flow are unnecessary when the native Service Report signature model already supports multiple signature roles.

This approach keeps the implementation aligned with the standard Field Service data model and avoids unnecessary customization. Study Guide reference: Configuring Mobility — Service Reports; Signature Types; Signature Blocks.