Quick Actions Card Localization and Modeling Considerations
Before you model the Quick Actions card, review the use of custom icons, access rights, and UI elements. Understand the user profile language and locale settings, custom labels, and message settings to use for the Quick Actions card.
Required Editions
Available in: Lightning Experience Available in: Enterprise and Unlimited Editions that have Consumer Goods Cloud enabled |
Locale and Translation
- Label translation:
- You can translate the label to any language supported by Salesforce. Right-to-left (RTL) languages aren’t currently supported.
- Use the Custom Labels setting in Salesforce to add translations for the quick action labels, card title, LWCs, and the overlay message when the app is offline. Ensure that the language settings in Salesforce and the CG Cloud mobile app are the same.
- The
CGCLOUD_MOBILE_QUICKACTIONS_TITLEcustom label localizes the QA card title. The custom labelsCGCLOUD_MOBILE_QUICKACTIONS_OFFLINE_HEADERandCGCLOUD_MOBILE_QUICKACTIONS_OFFLINE_SUBTEXTshow the localized offline message title and subtext when the device is offline. - If a translated label for a quick action doesn’t exist in the Custom Labels settings, the app uses the label set in Salesforce. If there’s no label set in Salesforce, the mobile app defaults to Quick Actions.
- The Quick Actions card's title and offline messages are shown in the language you set in the mobile app. When you open an LWC page in the mobile app, its content is also rendered in the mobile app locale. The Quick Actions card renders the global quick action labels in the language that is set in the user profile in CG Cloud. The LWC page content is rendered only if LWC supports the configured language.
- Variations in device and Salesforce user settings such as, locale, time zone, language, and date format differences might cause unexpected outcomes. Additionally, incorrect form factor detection could lead to improper rendering of certain LWCs. LWC developers are responsible for managing such potential inconsistencies.
Modeling Considerations
- The Quick Actions card is a default card and appears when the predefined setup criteria are met. This card can't be hidden or customized.
- The Quick Actions card doesn’t support the action bar, link bar, status color, and info text UI elements.
- You can’t modify edit and access rights on the Quick Actions card.
- The Quick Actions card doesn't support custom icons for global quick actions.
- If you use SVG images as background images from a theme for the Quick Actions card container, those images aren't rendered in the mobile app. The app replaces SVG images with the default mobile framework image.
Did this article solve your issue?
Let us know so we can improve!

