The system administrator at Ursa Major Solar creates several custom actions on the Work Order...

The correct configuration is the correct Field Service Mobile action placement and supported action type. Actions can appear in Salesforce Mobile but not Field Service Mobile when they are not placed in the required publisher-action section or when an unsupported legacy Lightning Component action type is used. Field Service Mobile has its own supported action model.

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. Mobile navigation settings do not substitute for the page-layout action configuration, and the mobile client does not automatically surface every action that appears elsewhere in Salesforce.

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; page layouts; supported quick-action types.