Quick Actions

Quick Action Locations

Configure quick actions to appear in these locations.

• Home Page. Actions appear on the mobile app home page.
• Next Best Customer. Actions show in the Next Best Customer window, under the account details.
• Calendar. Actions show in the visit preview window.
• Search. Actions appear in the accounts list after tapping the ellipsis button.
• Visit. Actions appear on the Visit Engagement page. This page currently supports only the Report Compliance Activity action.

Home Page

To configure home page actions in the Admin Console, use quick actions or custom actions because they don't use a page layout. Home page actions don't require a standard action.

Supported home page actions:

• New Visit
• Inquiry
• Share Content
• Email
• Create Medical Insight (requires turning on InsightCaptureFromAccount in Insight Settings)
• Custom Actions: URL, App, Utterance

Note GoTo Visit Actions aren't supported on the home page.

The app fetches the home page quick actions when:

• Set Location to Home.
• Set Entity to HomePage.
• Specify a profile or permission set.

Important If both Profiles and Permission Sets are empty, the action doesn't appear on the home page.

The app fetches the home page Custom Actions when:

• Set Location to HomePage.
• Set Entity Type to HomePage.

Visit and Visit Engagement

To add Visit Record Page actions, use the Visit page layout or the Visit Lightning Record Page, depending on whether dynamic actions are turned on.

The app gets Visit Engagement actions from the actions configured on the account object. Only a small subset of actions appear on the Visit Engagement page. See Supported Actions on Mobile for the supported actions.

To configure quick actions on the Visit Engagement page, set the Location to Visit.

How Quick Actions Are Filtered

The app uses these steps to filter quick actions:

• Gets actions based on the location from which the user opens them.
• Creates a list of actions by matching the mobile user's Salesforce profile name to the Profiles field. If the Profiles field is empty, the app doesn't return actions for this criteria.
• Keeps actions where at least one of the user's assigned permission sets matches the Permission Sets field. If the Permission Sets field is empty, the app doesn't return actions for this criteria.
• Combines the profile and permission set lists using OR logic, and includes the action if there's a match on either list.
• Removes duplicate actions. The unique key is a combination of Action Name, SObject, and Record Types. The app treats two records with the same action name and object but different record types as distinct.
• Applies action sorting using the Sort field in ascending order.

Note The list view and floating action wheel match the action order on your page layout. If you use dynamic actions, they match the Lightning record page instead. For Quick Actions, the app follows the Sort field in ascending order, so lower numbers appear at the top of the action wheel.

Rendering Rules

The rendering rules for Quick Actions differ depending on the location.

Known Considerations

• Configuration mismatch across UIs: A Quick Action configured for a custom component can appear there but not on the account record page if it's missing from the account page layout. For example, a New Visit action configured for Next Best Customer appears in that component, but doesn't appear on the account record page unless you add it to the account page layout.
• Duplicate actions: The app filters duplicate quick actions that use the action name and object. If you leave the object field blank on an action, the system treats it as distinct from other actions with the same name, which can result in duplicate actions.
• Hardcoded action type variants: All actions have multiple hardcoded name variants (for example, Namespace_survey and survey) to support both namespaced and non-namespaced orgs. Both variants open the same custom component.