LWC Quick Actions Considerations

• Navigation: You can open and view an LWC related to quick actions in the mobile app. The mobile app doesn’t let you navigate to other LWCs, or the detail pages of different records and objects, or web pages.
• Accessibility: Accessibility within custom Lightning Web Components (LWC) is not explicitly tested. The development team that implements the custom components is responsible for adhering to accessibility standards.
• Styling and theming considerations:
  • When you create custom LWC, verify that the pagination renders and the pages function seamlessly on different mobile devices and screen sizes.
  • The Quick Actions cockpit card, including the page header, is themed as the mobile app, but the mobile app theme doesn't affect the LWC page theme.
  • The LWC container style uses the existing theme in the Consumer Goods (CG) Cloud app. The container theme uses the application background and page header themes. These page header configuration information themes the page header for the container.
    • backgroundColor
    • toolbarSeparatorColor
    • standardButtonsBackgroundColor
    • standardButtonsBorderColor
    • standardButtonsFontColor
    • fontColor

    The main background and back icon are used from theming. SVG rendering at runtime isn’t supported. When the theming images are SVG, then it falls back to the default image.

• LWCs are built using Salesforce SDKs. As a result, the LWC offline considerations and limitations apply to the LWC integration with the CG Cloud mobile app. Review the components and mobile capabilties that are supported in the CG Cloud mobile app and desktop app.
• Media, external files, and deep links in LWC:
  • Videos that are hosted as static resources don’t load or play in LWC when those are deployed as quick actions. This is a known limitation in LWC.
  • Don't embedded videos from online platform. For example, YouTube.
  • Downloading files within LWC, including from cloud drives, such as, Google Drive isn't supported.
  • Deep links to quick actions isn't currently supported in LWC integration with the CG Cloud mobile app.
• Phone, Email and SMS in LWC: When you click phone, SMS, or email links in the LWC, the respective app (phone, SMS, or default email app) opens. The phone number or email address is pre-populated in the app.
• Unsupported capabilities in LWC:
  • The LWC page doesn't open the debug page with a triple tap, even when the debug mode is turned on.
  • There is no sync indicator on the LWC page.
  • LWC support for Modeler simulator app
  • Custom security pin screen on a LWC page on the mobile app
  • Offline working with LWC

Development and Troubleshooting Considerations

• Upgrade consideration: You may be required to reconfigure your LWC after upgrading to a future release of Consumer Goods Cloud.
• To use static resources with a custom connected app, enable webscopes. For instructions to enable webscope, see Static Resource Usage in LWC With Custom Connected App.
  

  Tip Switch to default connected app for the Consumer Goods Cloud mobile app to ensure a seamless user experience.
• Developer responsibilities: LWC developers are responsible for managing potential inconsistencies because of ‌differences in device and Salesforce user settings. For example, locale, time zone, language, and date format differences. When creating custom LWCs, developers must check that pagination and pages work well on different phones (form factor) and screen sizes.
• Debugging and error handling:
  • If a transaction cannot be saved, the mobile app shows an error message when the LWC closes.
  • If trace mode is enabled, you can view logs of LWC category in the Log Settings tab of the mobile app.
  • The LWC page doesn't open the debug page with a triple tap, even when the debug mode is turned on.