Salesforce FS-Con-101 - Agentforce Field Service and Operations Consultant

For this scenario, Salesforce Field Service should use a Resource Absence plus Fix Overlaps. Recording the sickness as a Resource Absence accurately removes the technician ' s availability. Fix Overlaps can then identify appointments that conflict with the absence and attempt to reschedule them to suitable resources under scheduling rules.

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. Changing the global policy to High Intensity does not model the absence, and manually dragging or calling customers creates avoidable administrative work before the scheduling engine is given a chance to resolve the disruption.

This approach keeps the implementation aligned with the standard Field Service data model and avoids unnecessary customization. Study Guide reference: Managing Scheduling and Optimization — Resource Absence; Fix Overlaps; disruption management.

The correct configuration is Drip Feed dispatch. Drip Feed controls how many future Service Appointments are released to each technician. Setting the quantity to the required number keeps the technician queue small and automatically dispatches the next eligible appointment as current work is completed, canceled, or cannot be completed.

Field Service Mobile is designed for technicians working in changing connectivity conditions. Standard page layouts, quick actions, flows, Service Reports, Knowledge, and supported mobile extensions should be used before introducing custom Visualforce or bespoke components because the native features participate in synchronization, offline behavior, and the Field Service security model.

The alternatives address different parts of the Field Service model. Manual dispatch creates avoidable administrative work, while ordinary auto-dispatch does not by itself provide the same controlled queue depth and protection from frequent schedule changes.

This approach keeps the implementation aligned with the standard Field Service data model and avoids unnecessary customization. Study Guide reference: Configuring Mobility — Drip Feed; automated dispatch; mobile appointment visibility.

The correct configuration is Territory Timezone in the Dispatcher Console. Displaying the Gantt in Territory Timezone lets dispatchers interpret appointments according to the local time where the work is being performed, which is essential when one dispatcher manages multiple time zones.

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. Changing the dispatcher ' s user time zone works for only one locale at a time, and a formula field does not change the time scale used by the scheduling interface.

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; Gantt timezone; Territory Timezone.

Knowledge Articles associated with Work Types, Work Orders, or Work Order Line Items is the appropriate Field Service design. Linking relevant Knowledge to the work context gives technicians job-specific procedures, specifications, and troubleshooting guidance. Work Types are especially useful because their associated articles can flow to recurring Work Orders and line items and be available in the Field Service mobile experience.

Field Service Mobile is designed for technicians working in changing connectivity conditions. Standard page layouts, quick actions, flows, Service Reports, Knowledge, and supported mobile extensions should be used before introducing custom Visualforce or bespoke components because the native features participate in synchronization, offline behavior, and the Field Service security model.

The alternatives address different parts of the Field Service model. A generic Knowledge component or custom search action is less targeted, and deep linking between mobile apps does not solve offline contextual availability.

This approach keeps the implementation aligned with the standard Field Service data model and avoids unnecessary customization. Study Guide reference: Configuring Mobility — Knowledge in Field Service; Work Types; mobile/offline access.

Street Level Routing and Default Travel Speed is the appropriate Field Service design. Street Level Routing uses road-network information to produce more realistic point-to-point travel estimates. Default Travel Speed is also important for aerial routing and acts as the fallback when a resource-specific speed is not configured.

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. Actual Travel Time records what happened after travel, while Minimize Travel is an objective and does not correct an unrealistic underlying estimate.

This approach keeps the implementation aligned with the standard Field Service data model and avoids unnecessary customization. Study Guide reference: Managing Scheduling and Optimization — Street Level Routing; Default Travel Speed; travel-time accuracy.

Status Transition restrictions based on Profile is the appropriate Field Service design. Field Service Status Transitions can be configured so only selected user profiles are allowed to move an appointment into a particular status such as Canceled. This supports the requirement that managers, but not technicians, perform the cancellation.

With private organization-wide defaults, Field Service can use automatic sharing, User Territories, territory public groups, and assignment relationships to expose the operational records needed by technicians and dispatchers. These sharing mechanisms are distinct from the permissions that control whether a user can configure Field Service or use a particular application capability.

The alternatives address different parts of the Field Service model. Resource Type and Role describe other aspects of the user/resource model, and permission sets do not replace the profile-based restriction available in the status-transition configuration.

This approach keeps the implementation aligned with the standard Field Service data model and avoids unnecessary customization. Study Guide reference: Permissions and Sharing — Service Appointment Status Transitions; profile restrictions.

The correct configuration is Quantity Unit of Measure configured for meters. Field Service inventory supports units of measure on products and downstream inventory records. Adding or using Meters as the Quantity Unit of Measure lets technicians record cable requirements and consumption in the metric unit consistently.

Field Service inventory distinguishes the product catalog from stock at a location and from inventory movement or consumption. Products define what the item is, Product Items represent how much of that Product is at a specific Location, Products Required describe planned needs, and Products Consumed record what was actually used during execution.

The alternatives address different parts of the Field Service model. Price Book configuration governs commercial pricing and organization locale governs regional formatting; neither changes the physical inventory measurement unit.

This approach keeps the implementation aligned with the standard Field Service data model and avoids unnecessary customization. Study Guide reference: Managing Inventory — Quantity Unit of Measure; Products; Product Items; consumed quantities.

For this scenario, Salesforce Field Service should use Page Layouts. Field Service Mobile uses assigned layouts to determine which Work Order and Service Appointment fields and related information technicians see. Appropriate profile/record-type layout assignments therefore provide the standard way to simplify the mobile record view.

Field Service Mobile is designed for technicians working in changing connectivity conditions. Standard page layouts, quick actions, flows, Service Reports, Knowledge, and supported mobile extensions should be used before introducing custom Visualforce or bespoke components because the native features participate in synchronization, offline behavior, and the Field Service security model.

The alternatives address different parts of the Field Service model. Field Sets apply to specific configurable surfaces, Visualforce is custom development, and Mini-Page Layouts do not drive the normal Field Service Mobile record experience.

This approach keeps the implementation aligned with the standard Field Service data model and avoids unnecessary customization. Study Guide reference: Configuring Mobility — Field Service Mobile; Page Layouts; technician record views.

The requirement is best implemented with High optimization runtime when priorities are similar and candidate counts are large. A longer runtime gives the optimizer more time to evaluate combinations. When many appointments have the same priority and each appointment has many qualifying resources, the search space expands and a higher runtime can improve schedule quality.

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 blank Scheduling Policy is a configuration issue rather than a reason to spend more optimization time, and disabling travel/break calculations changes the model rather than increasing optimization complexity in the way described.

This approach keeps the implementation aligned with the standard Field Service data model and avoids unnecessary customization. Study Guide reference: Managing Scheduling and Optimization — Optimization runtime; candidate volume; appointment priority.