Field Sets allow controlling which fields are displayed on the Work Order and Service Appointment cards in the Salesforce Field Service mobile app. Reference: https://help.salesforce.com/s/articleView?id=sf.fs_mobile_fields.htm&type=5

Generation Horizon is a setting that defines how far in advance work orders should be generated from maintenance plans[126]. Defining a generation horizon of 14 days would allow Universal Containers to automatically generate Work Orders 14 days before the next suggested maintenance date by creating work orders from maintenance plans within 14 days of their scheduled date[127]. Defining a generation timeframe of 14 days would not automatically generate Work Orders 14 days before the next suggested maintenance date. Generation Timeframe is a setting that defines how often work orders should be generated from maintenance plans[128]. Configuring Auto-generate Work Orders to True would not automatically generate Work Orders 14 days before the next suggested maintenance date. Auto-generate Work Orders is a setting that enables or disables the automatic generation of work orders from maintenance plans[129]. Defining a generation horizon of 20,160 minutes would not automatically generate Work Orders 14 days before the next suggested maintenance date. Generation Horizon is measured in days, not minutes[130]. Reference: https://help.salesforce.com/s/articleView?id=sf.fs_maintenance_plans_overview.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.fs_maintenance_plans_generation_horizon.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.fs_maintenance_plans_generation_timeframe.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.fs_maintenance_plans_auto_generate_work_orders.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.fs_maintenance_plans_overview.htm&type=5

These three considerations should be taken into account when implementing service level agreements for work orders, as they affect how milestones are created and applied to work orders. Reference: https://help.salesforce.com/s/articleView?id=sf.fs_milestones_for_work_orders_overview.htm&type=5

These two ways allow dispatching the appropriate technicians based on customer feedback, as they allow defining which resources are preferred or avoided by customers or accounts. Reference: https://help.salesforce.com/s/articleView?id=sf.fs_resource_preferences.htm&type=5

Service Resources are records that represent the people or equipment that perform field service tasks[53]. Permission Set Licenses are licenses that grant users access to specific features such as Field Service Dispatcher Console or Field Service Mobile App[54]. Creating one service resource and assigning the relevant permission set license would allow an employee at Universal Containers to perform both dispatcher and technician roles using one record and one license. Creating two skills records and assigning them to service resources record would not affect their roles or access to features. Skills are records that define specific abilities or qualifications that service resources have[55]. Creating two service resources and assigning them to the employee would create duplicate records and require two licenses for one employee. Creating one service resource and assigning the technician and dispatcher role would not work because roles are not fields on the service resource object. Reference: https://help.salesforce.com/s/articleView?id=sf.fs_service_resources_overview.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.fs_permission_set_licenses_overview.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.fs_skills_overview.htm&type=5