Field Service Developer Guide
jConsiderations for LWC Offline in the Field Service Mobile App
The following considerations apply to LWC Offline when you run your components in the
Field Service mobile app.
- Global quick actions are available on all pages that have the Actions menu. They do not receive the record ID of the current record when invoked from a record detail page.
- A Community license user who opens a service appointment can experience a missing record error. This is a known issue with this specific user type.
- Task objects added to a briefcase aren’t primed for offline use. If a briefcase contains a Task object and priming is attempted, an error message is displayed. However, other objects in the briefcase are primed. To resolve the error, remove Task objects from the briefcase.
- There’s a conflict between Appointment Assistant and LWC Offline that can result in missing URLs. See this known issue for details.
- (iOS only) Changes to Lightning web components are loaded into the app only when the app is fully quit and then relaunched (a “cold start”).