Set Up Geolocation-Based Actions for Field Service Mobile Workers

Give Mobile Workers Permissions

1. From Setup, in the Quick Find box, enter Users, and then select Profiles.
2. Edit the required profile.
3. From the General User Permissions section, select Run Flows.
4. From the Standard Object Permissions section, give Read and Edit permissions for the Geolocation Based Actions object.

Add the Related List

1. From the object management settings for service appointments, go to Page Layouts.
2. Open the mobile worker’s page layout.
3. Drag Geolocation Based Actions into the Related Lists section.
4. For validation purposes, repeat steps 1 to 3 for the Salesforce admin’s page layout.
5. In the mobile app and in the desktop application, open a service appointment record and verify that you can see the related list.

Create a Geolocation-Based Action

You can manually create a specific action for a mobile worker.

To set up an automation that lets you create actions at scale for all of your mobile workers, see Automate Geolocation-Based Actions.

Note

If you manually create a geolocation-based action for a specific service appointment instead of using a flow, make sure you set the owner as the assigned service resource’s user.

Geolocation-based action supports service territory and service territory members. You can assign geolocation-based action objects to service territory members linked to the service resource. You can also directly assign the objects to service territories associated with those members. In either case, the location-based actions will function just as they do for service appointments.

1. From the App Launcher, find and select Service Resources.
2. Select the required service resource.
3. In the Geolocation-Based Actions related list, click New.
4. Enter a name and a description.
5. For Action Type, select one of these options.
   • Platform Alerts: Silently logs a timestamp based on the mobile worker’s location when they arrive or leave a job site.
   • View Records: When the mobile worker arrives or leaves a jobsite, a record opens.
   • Quick Actions: When the mobile worker arrives or leaves a jobsite, a quick action pops up.
6. For Action Data, provide the JSON format according to the selected action type.
   • For the Platform Alert action type, if you leave this field empty the invocation timestamp is updated or you can enter the JSON format of the API name of the quick action, for example, {"quickAction": "quick_action_name"}. Your mobile screen flow runs automatically when you open the app, based on your input.
   • For the View Record action type, enter the JSON format of the ID of the record. For example, {"viewRecord": "1WLxx000000003FGAQ"}.
   • For the Quick Action action type, enter the JSON format of the API name of the quick action as it’s shown in the page layout. For example, {"quickAction": "Global.LogACall"}.

     Quick actions must be of type Flow, Lightning Web Component, or Create and Update Record.

     To find the API name of a quick action in Object Manager, open the Service Appointment object and click Page Layouts. Open the mobile worker’s page layout and hover over the required quick action. The API name is shown as the Name of the action in the tooltip. In this example, the API name is ServiceAppointment.SendEmail.

     
7. For Radius, enter the distance in meters from the location of the associated object that triggers the action. The minimum radius is 100 meters.
8. To determine whether this action is triggered when the mobile worker arrives or leaves the jobsite, for Trigger Type, select Enter or Exit.
9. To see the Geolocation Based Actions records, from the App Launcher, find and select Geolocation Based Actions.
   If you can’t see Geolocation Based Actions in the App Launcher, review the tab settings.
   1. From Setup, in the Quick Find box, enter Users, and then select Profiles.
   2. Edit the required profile.
   3. Click Object Settings.
      If you can’t see this option, follow the instructions in Enable the Enhanced Profile User Interface.
   4. Set the Tab Settings of Geolocation Based Actions to Default On.