FS-Con-101 Sample Questions Answers

two Service Appointments assigned to two different resources is the appropriate Field Service design. Because the technicians can arrive at different times, their work must be independently schedulable. Separate Service Appointments allow each technician to have independent timing, travel, and assignment while still supporting the same overall job.

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 single appointment with two resources is more appropriate for a crew-style simultaneous visit, and Required Resources on one appointment would not provide separate scheduling windows.

This approach keeps the implementation aligned with the standard Field Service data model and avoids unnecessary customization. Study Guide reference: Managing Scheduling and Optimization — Multiple Service Appointments; independent resource scheduling.

The correct configuration is a parent Work Order with Asset-specific Work Order Line Items. Work Order Line Items are the standard way to represent individual components, Assets, or tasks under one service engagement. Each line item can carry its own Asset, status, Work Type, products, skills, pricing, and appointment when needed.

The Field Service data model separates the service requirement from its individual tasks and visits. A Work Order represents the overall job, Work Order Line Items represent component-level or task-level work, and Service Appointments represent the scheduled field visits used to execute that work. Choosing the correct level preserves accurate history, pricing, inventory, and scheduling.

The alternatives address different parts of the Field Service model. Separate parent Work Orders are only necessary when the work must have independent job lifecycles; Products Consumed records materials used, not the component-level work structure.

This approach keeps the implementation aligned with the standard Field Service data model and avoids unnecessary customization. Study Guide reference: Managing Work Orders — Work Orders; Work Order Line Items; Asset-level service tracking.

For this scenario, Salesforce Field Service should use Service Territory and Scheduling Policy. The Service Territory defines the population of resources and appointments being optimized, while the Scheduling Policy supplies the Work Rules and Service Objectives used to evaluate and rank scheduling alternatives.

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. Work Types affect job requirements but are not required optimization-job objects, and polygons help with geography but do not replace the optimization scope or policy.

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 jobs; Service Territories; Scheduling Policies.

The requirement is best implemented with a monthly Maintenance Plan with a 12-month generation timeframe and automatic generation disabled. Frequency of one month models the twelve monthly checkups, while a 12-month generation timeframe represents the annual horizon. Because the customer calls to initiate each visit, automatic Work Order generation should remain disabled and work can be generated manually when appropriate.

The consultant should distinguish recurrence from job definition. A Work Type describes how a recurring job is performed, while the Maintenance Plan determines when and how future work is generated. Work Order and Service Appointment generation methods then determine whether Assets are consolidated into one visit or separated into multiple jobs.

The alternatives address different parts of the Field Service model. Automatically generating each month would remove the intended customer-driven control, while a one-month generation timeframe would not represent the planned annual set as efficiently.

This approach keeps the implementation aligned with the standard Field Service data model and avoids unnecessary customization. Study Guide reference: Configuring Maintenance Plans — Maintenance Plans; Frequency; Generation Timeframe; Auto-generate Work Orders.

The correct configuration is a new Service Appointment on the original Work Order or a new Work Order plus Service Appointment. Each physical return visit should be represented separately so the first visit remains part of the historical record. Continuing the same job can use another appointment on the existing Work Order; separately managed follow-up work can use a new Work Order and appointment.

The Field Service data model separates the service requirement from its individual tasks and visits. A Work Order represents the overall job, Work Order Line Items represent component-level or task-level work, and Service Appointments represent the scheduled field visits used to execute that work. Choosing the correct level preserves accurate history, pricing, inventory, and scheduling.

The alternatives address different parts of the Field Service model. Rescheduling the original appointment would overwrite the timing representation of the first visit and reduce the accuracy of visit-history reporting.

This approach keeps the implementation aligned with the standard Field Service data model and avoids unnecessary customization. Study Guide reference: Managing Work Orders — Return visits; multiple Service Appointments; service history.

For this scenario, Salesforce Field Service should use custom Asset reports using Parent Asset and Root Asset. Parent Asset and Root Asset expose the hierarchical position of an installed component. Custom reporting can reference these fields to analyze Assets while preserving hierarchy context.

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. The interactive View Asset Hierarchy action is useful for navigation but is not the requested reporting solution, and standard Asset reports do not expose all hierarchy fields in the same way.

This approach keeps the implementation aligned with the standard Field Service data model and avoids unnecessary customization. Study Guide reference: Managing Assets — Asset hierarchy reporting; Parent Asset; Root Asset.

Work Order Line Items for operations and one Service Appointment for the visit is the appropriate Field Service design. Each SOP operation should be represented as a task-level line item so it can have its own status and notes. The single Service Appointment represents the one onsite visit during which all operations are completed.

Reusable configuration should be preferred over duplicating records or custom objects. Work Types can standardize duration, required skills, required products, and Knowledge, while the Work Order hierarchy and Work Order Line Item hierarchy are available when genuinely separate but related work must be represented.

The alternatives address different parts of the Field Service model. Using multiple appointments would imply multiple visits, while using Work Orders for each operation would fragment one preventive-maintenance job into unnecessarily separate service records.

This approach keeps the implementation aligned with the standard Field Service data model and avoids unnecessary customization. Study Guide reference: Managing Work Orders — Work Order Line Items; Service Appointments; SOP execution.

For this scenario, Salesforce Field Service should use the standard Asset Install Date. An Asset represents the customer-installed product instance, and its standard Install Date records when that instance was installed. Reporting on this field directly answers how many products were installed during a selected period.

This distinction is important for reporting and maintenance because the organization often needs to know not merely what type of product was sold, but which serialized or installed unit changed status, location, parentage, or replacement state and which service work was performed against it.

The alternatives address different parts of the Field Service model. Field History Tracking audits changes rather than providing the primary installation date, Work Orders represent service activity, and a custom field on Products Consumed would duplicate a standard Asset capability.

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

For this scenario, Salesforce Field Service should use the crew-specific scheduling behavior that ignores individual Preferred Resource scoring for active crew members. When a technician is an active member of a Service Crew, scheduling evaluates the crew as the schedulable unit rather than independently applying individual preferred-resource scoring to that member. This is an important design consideration when crew membership is used.

The Field Service resource model separates the person or workforce unit from the qualifications, territory memberships, capacity, absences, and crew relationships used by scheduling. A Service Resource can therefore be evaluated consistently by the scheduling engine without embedding workforce logic directly in Work Orders or Service Appointments.

The alternatives address different parts of the Field Service model. Capacity-based scheduling and recommended crew size are different concepts, and a resource may participate in different crews at different nonoverlapping times.

This approach keeps the implementation aligned with the standard Field Service data model and avoids unnecessary customization. Study Guide reference: Managing Resources — Service Crews; active Crew Members; resource preferences.

Service Territories sized to fewer than about 50 resources is the appropriate Field Service design. Scheduling and optimization quality improves when territories are kept within practical resource and appointment volumes. Splitting 140 resources into three territories yields roughly 46–47 resources per territory and approximately 800 appointments per day if demand is balanced.

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. Two territories would leave about 70 resources in each, while polygons inside one very large territory do not reduce the number of resources the scheduling engine must consider.

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 Territory design; optimization scalability; dispatcher performance.

The requirement is best implemented with one Service Appointment per Work Order Line Item with bulk scheduling. Each server-installation step has independent skill requirements, so each line item should have its own appointment. Bulk scheduling can then assign the same or different resources according to qualification and availability.

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. A single Work Order-level appointment would force both tasks into one scheduling unit, while a Same Start dependency introduces a simultaneity requirement that the scenario does not state.

This approach keeps the implementation aligned with the standard Field Service data model and avoids unnecessary customization. Study Guide reference: Managing Scheduling and Optimization — Work Order Line Item appointments; bulk scheduling; skill-based assignment.

the Exclude Technician from Geolocation Tracking permission is the appropriate Field Service design. A dedicated system permission can be placed in a permission set and assigned only to contractors who should not be tracked. This keeps the organization-wide mobile tracking configuration enabled for full-time technicians.

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. Turning off the global tracking setting affects everyone, and profile geocoding or a zero frequency is not the supported per-user exclusion control.

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 geolocation; exclusion permission.

For this scenario, Salesforce Field Service should use a Return Order with Return Order Line Items. A Return Order represents the overall return transaction and Return Order Line Items identify the individual products or Assets being returned. This is the standard Field Service inventory model when the customer sends a defective item back instead of scheduling onsite work.

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. Work Orders represent work to be performed, while Product Requests are used to obtain inventory rather than to record customer returns.

This approach keeps the implementation aligned with the standard Field Service data model and avoids unnecessary customization. Study Guide reference: Managing Inventory — Return Orders; Return Order Line Items; inventory returns.

The correct configuration is Customer First and Soft Boundaries. Customer First emphasizes preferred resources and prompt service while still considering efficiency. Soft Boundaries applies similar customer-oriented objectives but permits appropriate resource sharing across territory boundaries, which can improve coverage.

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. High Intensity prioritizes throughput during heavy demand, and Emergency Policy is designed for urgent emergency work rather than normal preferred-resource commitments.

This approach keeps the implementation aligned with the standard Field Service data model and avoids unnecessary customization. Study Guide reference: Managing Scheduling and Optimization — Standard Scheduling Policies; Customer First; Soft Boundaries.

For this scenario, Salesforce Field Service should use Resource Preferences together with Required and Excluded Resource Work Rules. Customer feedback can be translated into Resource Preferences on Accounts or Work Orders. Required and Excluded preferences are then enforced by the corresponding Work Rules in the Scheduling Policy so unsuitable technicians are filtered and required technicians are honored.

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. Business objectives rank otherwise valid candidates; they are not substitutes for Required/Excluded filtering. Preferences also belong on customer/work records rather than on the Service Resource itself.

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 Preferences; Required Resources; Excluded Resources.

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.

For this scenario, Salesforce Field Service should use one Product Item with serialized units in the related list. The locks are serialized inventory because every physical unit has a unique identifier. The Product Item represents the stock at the technician ' s van Location, and the Serialized Products related list stores each individual serial number.

Inventory design should also preserve pricing and traceability. Price Books and Price Book Entries supply commercial pricing, while serialized inventory gives unit-level identity when individual items must be tracked. Product Requests and Product Transfers manage replenishment and movement rather than the underlying job structure.

The alternatives address different parts of the Field Service model. A quantity-only Product Item would lose individual traceability, and serial numbers in Notes are unstructured and cannot participate properly in serialized-inventory transactions.

This approach keeps the implementation aligned with the standard Field Service data model and avoids unnecessary customization. Study Guide reference: Managing Inventory — Serialized Products; Product Items; van stock; serial-number tracking.

The requirement is best implemented with Field Service automatic sharing for dispatched Service Appointments. With private OWD, enabling the Field Service setting to share dispatched appointments with assigned resources grants the technician access based on the Assigned Resource relationship and appointment lifecycle.

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. Changing ownership or maintaining custom sharing rules adds unnecessary automation, while User Territories are mainly used to give dispatchers and call-center users access to territory records.

This approach keeps the implementation aligned with the standard Field Service data model and avoids unnecessary customization. Study Guide reference: Permissions and Sharing — Private OWD; automatic sharing; Assigned Resources.

For this scenario, Salesforce Field Service should use Soft Boundaries. Soft Boundaries is designed for customer-oriented scheduling while allowing resources to be shared across territory borders. That flexibility is useful when one territory has backlog but customer preferences still need to influence the scheduling score.

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. Customer First does not provide the same cross-territory flexibility, High Intensity prioritizes throughput, and Emergency is intended for urgent incidents.

This approach keeps the implementation aligned with the standard Field Service data model and avoids unnecessary customization. Study Guide reference: Managing Scheduling and Optimization — Soft Boundaries Scheduling Policy; cross-territory resource sharing.

The requirement is best implemented with Company colors. Field Service Mobile supports native branding through configurable UI colors in Field Service Mobile Settings. This allows the mobile experience to reflect the organization ' s visual identity without unsupported stylesheet customization.

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. Company address is informational, arbitrary style sheets are not the native branding mechanism, and the standard configuration represented by the available choices is company color customization.

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 branding; mobile settings; UI colors.

The requirement is best implemented with Products Required and Skill Requirements. A first-time fix depends on sending a technician who has both the required expertise and the expected parts. Skill Requirements filter or rank qualified resources, while Products Required communicate the material expected for the job.

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. Products Consumed records what was actually used after execution; estimated duration and SLA information do not ensure that the technician has the required competence and inventory.

This approach keeps the implementation aligned with the standard Field Service data model and avoids unnecessary customization. Study Guide reference: Managing Work Orders — Work Orders; Products Required; Skill Requirements; first-time fix.

The correct configuration is an Excluded Resource preference on the Account. An Account-level Excluded Resource preference records that the customer should not receive that technician on future work. The Scheduling Policy ' s Excluded Resources rule can then prevent the technician from being considered.

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. Simply removing Preferred status would stop favoring the technician but would not prohibit assignment, and moving territories would affect unrelated customers.

The recommended choice also keeps the decision inside the native scheduling framework, so future optimization and dispatcher actions evaluate the same constraints consistently instead of relying on manual workarounds.

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 Preferences; Excluded Resources; Account-level preferences.

The correct configuration is Gantt Palettes. Palettes color-code Service Appointments according to selected field values, including numeric and currency values. A revenue field can therefore be mapped to a palette so dispatchers immediately see high-value appointments on the Gantt.

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. Field Sets control which data is displayed, Map Report Layers add geographic overlays, and Gantt Actions perform operations rather than continuously color-coding appointment value.

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 Palettes; appointment visualization.

The requirement is best implemented with Products Consumed on Work Orders and Work Order Line Items. Products Consumed records the parts actually used during service. Reporting at the Work Order level gives job-level usage, while reporting on Work Order Line Items provides task-level consumption detail.

Inventory design should also preserve pricing and traceability. Price Books and Price Book Entries supply commercial pricing, while serialized inventory gives unit-level identity when individual items must be tracked. Product Requests and Product Transfers manage replenishment and movement rather than the underlying job structure.

The alternatives address different parts of the Field Service model. Service Appointment inventory and Work Order inventory are not the standard consumption records used to measure actual part usage.

This approach keeps the implementation aligned with the standard Field Service data model and avoids unnecessary customization. Study Guide reference: Managing Inventory — Products Consumed; Work Orders; Work Order Line Items; inventory reporting.

For this scenario, Salesforce Field Service should use Territory and Resources filters. Filtering by Territory isolates the geographic operating area and its local scheduling context, while filtering by Resources narrows the Gantt to the technicians the dispatcher is actively managing.

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. Hours changes the visible time range but does not isolate the multi-time-zone workforce, and Skills filtering serves qualification searches rather than general console simplification.

The recommended choice also keeps the decision inside the native scheduling framework, so future optimization and dispatcher actions evaluate the same constraints consistently instead of relying on manual workarounds.

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 filters; Territory; Resources.

The correct configuration is a Preferred Resource preference on the Account plus the Preferred Resource Service Objective. The Account-level preference establishes an ongoing customer-technician preference that can influence future work, while the Scheduling Policy objective gives that preference weight when ranking otherwise valid candidates.

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. Making the technician Required on one appointment is a one-off hard constraint and does not create the reusable customer preference required for subsequent service calls.

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 Preferences; Preferred Resource objective; Account inheritance.

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.

For this scenario, Salesforce Field Service should use Time Sheet Entries related to the Work Order Line Item. The complex repair steps are represented by line items, so linking individual Time Sheet Entries to each line item provides the granularity needed to total travel, preparation, and onsite time for that specific step.

Salesforce favors reusable resource metadata over one-off record manipulation. When resource qualifications and availability are modeled correctly, the same information can support candidate selection, optimization, dispatching, reporting, and mobile execution without duplicating logic on individual jobs.

The alternatives address different parts of the Field Service model. Relating the parent Time Sheet instead of the entries would lose activity-level detail, and the Service Appointment is a scheduling record rather than the standard task-level labor association requested.

This approach keeps the implementation aligned with the standard Field Service data model and avoids unnecessary customization. Study Guide reference: Managing Resources — Time Sheets; Time Sheet Entries; Work Order Line Items.

For this scenario, Salesforce Field Service should use Time Sheet Entries related to Work Orders and Work Order Line Items. Time Sheets represent a resource ' s reporting period, while Time Sheet Entries capture individual blocks of labor. Standard associations let those entries be attributed to an overall Work Order or to a specific Work Order Line Item for task-level costing and reporting.

Salesforce favors reusable resource metadata over one-off record manipulation. When resource qualifications and availability are modeled correctly, the same information can support candidate selection, optimization, dispatching, reporting, and mobile execution without duplicating logic on individual jobs.

The alternatives address different parts of the Field Service model. Assigned Resource belongs to the broader time-sheet/resource relationship, and Service Appointment is not one of the two standard work associations requested here.

This approach keeps the implementation aligned with the standard Field Service data model and avoids unnecessary customization. Study Guide reference: Managing Resources — Time Sheets; Time Sheet Entries; Work Orders; Work Order Line Items.

For this scenario, Salesforce Field Service should use the required Salesforce Classic Publisher action placement. For the action type described, Field Service Mobile depends on the action being present in the appropriate publisher-action section of the assigned page layout. An action can therefore appear in Salesforce Mobile yet remain unavailable in Field Service Mobile if it is placed incorrectly.

Mobile configuration should reduce technician data entry and expose only the actions and information needed at the point of service. The strongest designs reuse the Work Order and Service Appointment data model, launch guided actions from the appropriate parent record, and keep customer-facing outputs such as signatures and Service Reports within the native Field Service workflow.

The alternatives address different parts of the Field Service model. Create-a-Record actions are supported, and App Extensions are a different extension mechanism rather than the cause of a standard page-layout quick action being absent.

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 actions; Classic Publisher Quick Actions.

The correct configuration is Work Order-specific Entitlement Processes and reusable Milestones. An Entitlement Process is created for one process type, such as Case or Work Order, and Work Order milestones can be configured in Setup. A Milestone definition can be reused in more than one entitlement process even though the processes themselves remain object-specific.

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. A single process does not simultaneously apply to both Cases and Work Orders simply because the same Milestone is used.

This approach keeps the implementation aligned with the standard Field Service data model and avoids unnecessary customization. Study Guide reference: Managing Work Orders — Work Order SLAs; Entitlement Process Type; Milestones.

the Reshuffle action is the appropriate Field Service design. 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 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.

The correct configuration is Multi-Day Service Appointments. Use them when one body of work exceeds a resource ' s available working hours in a day or must continue across consecutive days, including nonworking periods such as weekends. The scheduler distributes the duration across eligible working periods.

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. Jobs requiring separate stages by different resources are better represented as separate appointments with dependencies, while a recurring same-day pattern is not a multi-day appointment.

This approach keeps the implementation aligned with the standard Field Service data model and avoids unnecessary customization. Study Guide reference: Managing Scheduling and Optimization — Multi-Day Service Appointments; resource availability; complex work.

the standard Service Report is the appropriate Field Service design. Service Reports are designed to summarize completed field work, include customer-facing details, capture signatures, generate a PDF, and be sent electronically. They are integrated directly into Field Service Mobile and the Work Order/Service Appointment lifecycle.

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. A generic Work Order email template or analytical report does not provide the structured service-document and signature workflow, and custom automation is unnecessary.

This approach keeps the implementation aligned with the standard Field Service data model and avoids unnecessary customization. Study Guide reference: Configuring Mobility — Service Reports; Service Report Templates; signatures; electronic delivery.

The correct configuration is Assets with a parent-child hierarchy. Serialized customer components should be represented as individual Assets related in an Asset hierarchy. Work Orders and Work Order Line Items can then reference the exact component that needs service while still preserving its relationship to the overall installed product.

This distinction is important for reporting and maintenance because the organization often needs to know not merely what type of product was sold, but which serialized or installed unit changed status, location, parentage, or replacement state and which service work was performed against it.

The alternatives address different parts of the Field Service model. Products describe catalog definitions, Orders describe commercial transactions, and Work Order hierarchies organize service activity rather than the physical installed-product structure.

This approach keeps the implementation aligned with the standard Field Service data model and avoids unnecessary customization. Study Guide reference: Managing Assets — Assets; Asset hierarchies; serialized components.