Field-Service-Consultant Exam Dumps : Salesforce Certified Field Service Consultant (FS-Con-101)

Earliest Start Permitted is a field on the Service Appointment object that defines the earliest date and time that a service appointment can start[222]. Due Date is a field on the Service Appointment object that defines the latest date and time that a service appointment must be completed by[223]. Using Earliest Start Permitted and Due Date fields on Service Appointments would help ensure that they are completed within the agreed upon Service Level Agreement (SLA) with Universal Containers’ customers by setting the boundaries for when a service appointment can start and finish according to the SLA terms[224]. Actual Start andActual End are fields on the Service Appointment object that capture the actual date and time that a service appointment started and ended[225]. Using Actual Start and Actual End fields on Service Appointments would not help ensure that they are completedwithin the agreed upon SLA with Universal Containers’ customers because they are recorded after the service appointment is performed and do not enforce any SLA terms. Arrival Window Start and Arrival Window End are fields on the Service Appointment objectthat define the expected date and time range that a resource will arrive at a service appointment[226]. Using Arrival Window Start and Arrival Window End fields on Service Appointments would not help ensure that they are completed within the agreed upon SLA with Universal Containers’ customers because they only indicate when a resource will arrive and do not enforce any SLA terms. Scheduled Start and Scheduled End are fields on the Service Appointment object that define the planned date and time range thata service appointment will take place[227]. Using Scheduled Start and Scheduled End fields on Service Appointments would not help ensure that they are completed within the agreed upon SLA with Universal Containers’ customers because they only indicate whena service appointment is scheduled and do not enforce any SLA terms. References: &type=5

Permission Sets are records that grant users access to specific features or apps such as Salesforce Field Service[214]. Scheduling licenses are records that grant users access to scheduling features such as Dispatcher Console or Optimization[215]. Creating Permission Sets and assigning the Salesforce Field Service Resource Permission Set and Scheduling license to each Technician would allow Universal Containers’ Technicians to update their own appointments’ status using the Dispatcher console Gantt chart by granting them access to Salesforce Field Service mobile app features such as updating status and granting them access to scheduling features such as viewing Gantt chart[216]. Creating Permission Sets and assigning the Salesforce Field Service Scheduling and Mobile Permission Sets to the Resource profile would not allow Technicians

Articles are records that contain information or instructions about products, services, or processes[168]. Work Orders are records that track customer requests for service such as repairs or maintenance[169]. Writing a workflow that associates Articles to Work Orders based on a picklist on the Work Order would allow Universal Containers to ensure its Technicians can access Knowledge Articles offline by creating a workflow rule that triggers when a picklist value on the work order is selected and adds the relevant articlesto the work order related list[170]. Using Work Types to assign associated Articles to Work Orders would not work because Work Types are records that define the standard tasks and duration for a specific type of work and do not have a direct relationshipwith articles[171]. Using the Salesforce mobile app with deep linking to the Salesforce Field Service mobile app would not work because deep linking is a feature that allows launching one app from another app and does not affect offline access[172]. Creating a custom mobile app that syncs articles based on Service Appointment assignments would not work because it would require additional development and maintenance and would not leverage the existing Salesforce Field Service mobile app features[173]. References: &type=5 &type=5 & &type=5 & &type=5