Loading
Salesforce now sends email only from verified domains. Read More
Set Up and Maintain Retail Execution
Table of Contents
Filter by (0)Add
Select Filters

          No results
          No results
          Here are some search tips

          Check the spelling of your keywords.
          Use more general search terms.
          Select fewer filters to broaden your search.

            Search all of Salesforce Help
            Search all of Salesforce Help
            Quick Actions Card Considerations

            You are here:

            1. Salesforce Help
            2. Docs
            3. Set Up and Maintain Retail Execution

            Quick Actions Card Considerations

            The Quick Actions card shows on all cockpit pages by default when the Consumer Goods Cloud mobile app is online. Review the limits, quick action naming convention, and visibility considerations for the Quick Actions card.

            Required Editions

            Available in: Lightning Experience

            Available in: Enterprise and Unlimited Editions that have Consumer Goods Cloud enabled
            • After you activate the LWC quick actions integration, then launch the mobile app and log in, the global and object-specific quick actions appear on the Quick Actions card. You can view them after you complete the first sync of the day.
            • The Quick Actions card shows the global quick actions of type LightningWebComponent and contains CGCloud_Mobile in the name. For exampl: CGCloud_Mobile_<quick_action_name>, <quick_action_name>_CGCloud_Mobile.
            • The global quick action labels on the Quick Actions card are sorted in ascending order by name.
            • The Quick Actions card shows up to 10 quick actions. If there are more than 10 quick actions on the card, only the first 10 quick actions are shown.
            • Quick Actions card visibility considerations:
              • The Quick Actions card shows quick actions and enables for providing real-time data, so you must be online to use the global quick actions. If the app loses network connectivity, the Quick Actions card appears blank.
              • If there are no quick actions configured for a cockpit, the Quick Actions card doesn't appear.
            • The Quick Actions card is collapsible but doesn’t maintain its collapsed state during page rotation or orientation changes on mobile devices.
            • Context passing in quick actions: When you launch global quick actions from the Quick Actions card, the mobile app includes your user ID as part of the context. For example, platform actions support recordId and objectApiName. You can fetch them using the @api decorator directly inside LWC. Therefore, the userId should be fetched from the current page reference. Here's a sample LWC to read the userId property from the passed context.
              import { LightningElement, api, wire } from 'lwc';
import { CurrentPageReference } from "lightning/navigation";
export default class <component name> extends LightningElement {
    @wire(CurrentPageReference)
    currentPageRef;
    @api userId;
    get userId() {
        return this.currentPageRef.state.userId;
      }
}
            • Quick Actions card loading considerations: The mobile app loads quick actions upon app start when the feature is activated and you log in. After a regular or First Sync of the Day (FSOD) sync, the app verifies if quick actions for the current day are retrieved (auto-fetch on day change). If not, the app loads and stores the quick action data. The quick actions don't load in these scenarios:
              • Start the mobile app in offline mode: The mobile app monitors the connectivity status and loads the quick action when the device is online.
              • Start the mobile app in online mode and skip authentication: Authentication is required when you start the app the first time. If you skip authentication, the app defers loading of quick actions until user authentication is complete.
              • Start the mobile app in offline mode and skip authentication: The mobile app defers loading the quick actions until the device is online and user authentication is complete.
             
            Loading
            Salesforce Help | Article