You are here:
Patch Releases Summer `26
We release patches periodically. Check back here for information on each Summer `26 patch release for the Life Sciences Cloud mobile app.
Summer '26 Release and Monthly Releases
To view the release notes for Summer '26, see Life Sciences.
We released several Life Sciences features and changes on a monthly basis during Summer '26. To learn about them, see Life Sciences Features Released by Month.
To view patch release notes for the Life Sciences Cloud for Customer Engagement package, see Patch Releases Summer `26.
Version 262.10.0
This patch contains fixes to ensure that the Life Sciences Cloud mobile app features work correctly.
| Feature | Issue | Description |
|---|---|---|
| Medical Inquiry | When Key Account Manager (KAM) users created a new inquiry, the Life Sciences Cloud mobile app became unresponsive | The issue is now resolved, allowing KAM users to create new inquiries without the app freezing. |
| General | Some users of the Life Sciences Cloud iOS mobile app experienced unexpected app crashes. | The iOS mobile app now includes a targeted crash fix that improves app stability for users. |
Version 262.9.0
This patch contains fixes to ensure that the Life Sciences Cloud mobile app features work correctly.
| Feature | Issue | Description |
|---|---|---|
| Account Management | An account created in the mobile Search Before Create workflow continued to appear unaligned after its DCR was approved, repeatedly prompting users to align it. | Approved accounts now sync updated territory alignments to mobile, removing unnecessary prompts to realign the account. |
| Creating an account and related records from the offline mobile Search Before Create workflow with approval-on-create disabled created child data change requests without linking them to the parent account request. | Child data change requests for related healthcare providers, addresses, affiliations, and specialties now store the parent account request ID, maintaining proper request hierarchy. | |
| Custom Person Account columns in mobile account lists displayed technical field API names instead of field labels, and HCP specialties appeared as API codes rather than display labels. | The mobile app now resolves Person Account field labels from related Contact metadata and displays specialty codes as their configured display names. | |
| HCP advanced search could hide configured name fields, mark an optional Name field as required, or return an error for a Name-only search. | Mobile search forms now display Person Account fields consistently with the web experience and provide clear search prompts for first name, last name, or NPI search criteria. | |
| Calendar | Dragging visits to create or reschedule them in calendar was slow, triggered frequent calendar refreshes, or applied scheduling conflict rules that differed from the Visit page. | Calendar now uses standard visit validation rules, honors configured warning and error settings, minimizes redundant data processing, and refreshes the calendar efficiently. |
| Event Management | The Managed Event expense grid was cut off on iPad displays, making expense details and allocation controls difficult to view and manage. | The grid now uses responsive column layout and consistent spacing, and the allocation window matches the active app theme. |
| Custom labels and translations for Managed Event participant actions weren't reflected in the mobile app. | Participant action custom labels like Attendee, Colleague, Expert, Non-Profiled Attendee, and Write, now correctly display their configured custom labels. | |
| The Managed Event resource workflow displayed addresses for unrelated accounts and included location types not applicable to events. | Addresses are now filtered to the selected account, and account locations are limited to applicable event venues. | |
| The record type was missing when creating a Managed Event on iPad, and record type mappings failed to populate or save the corresponding event type. | Available record types now appear correctly during event creation, and selected record type mappings correctly populate and save to the Managed Event record. | |
| The affiliation action could remain hidden in the Managed Event attendee view even when HCP-HCO affiliations were enabled. | The mobile app now reads the current Managed Event affiliation setting and displays the affiliation action when configured. | |
| The Select Colleague screen could list all active users, including HCP and HCO records that weren't eligible colleagues. | The Select Colleague screen now filters the user list to display only eligible internal user accounts. | |
| Managed Event presentations were available only in preview mode, preventing presentation activity and clickstream data from being captured. | Users can now tap presentation thumbnails to open them in Play mode, allowing the app to record presentation activity and clickstream data directly against the event. | |
| The Subject lookup for a Managed Event displayed subjects intended for other uses, including base and system-generated records. | The subject lookup now filters out system-generated and non-event records, displaying only subjects configured for Managed Events. | |
| The mobile sign-in sheet ignored configured attendee field sets and lock-screen settings. | Signature capture now reads these values directly from the Managed Event configuration, regardless of unrelated feature settings, and displays the configured columns and lock controls. | |
| The Distribution Type field in Managed Event expenses displayed a different label on iPad than on the desktop site. | The mobile expense view now uses the current configured field label for a consistent experience across interfaces. | |
| The Managed Event Account Attendees window on iPad omitted Search Before Create options, preventing users from creating an account from the attendee workflow. | The attendee search workflow on iPad now incorporates configured search settings and field sets, enabling advanced search and account creation directly from the window. | |
| Confirming an HCO or venue resource didn't populate the related location and address on the parent Managed Event. | When a resource reaches confirmed status, its location and address details are copied to the parent Managed Event and preserved across synchronization. | |
| Adding a non-profiled attendee could assign an unavailable invited participant response, and adding an attendee could fail because the app couldn't synchronize an address text field. | Attendee creation now uses valid participant-response values and correctly handles attendee address data during synchronization. | |
| Users could not add colleagues to a managed event. | Fixed the underlying issue and users can now add colleagues to a managed event. | |
| General | URL-addressable Lightning web components (LWC) on home pages or custom tabs failed to render when a namespace was added to a component name more than once. | The mobile app now recognizes names that already include a namespace and consistently resolves the correct component name. |
| Text entered in a rich text area on a dynamically rendered page could be lost when users saved the record on iPad. | The rich text editor now reliably captures and syncs text entries so that edits are preserved and displayed after saving. | |
| Pending mobile updates waiting to synchronize were not reapplied after a download sync, causing records to appear to revert to older server values. | Pending local changes are now reapplied immediately after synchronization so edits remain visible until fully processed by the server. | |
| Lightning web component (LWC) actions placed in a record highlight panel were not prefetched during metadata synchronization and were unavailable offline. | Metadata synchronization now automatically caches highlight panel component actions, making them available offline. | |
| Sales Data | Dashboard report tiles that displayed data in Lightning Experience could appear blank or show no data. | Dashboard requests now use the current supported API behavior, tolerate incomplete component data, and display report tables with corrected sizing and alignment. |
| Surveys | Selecting the survey action from a Managed Event failed because the mobile app used an outdated workflow component name and parameters. | The survey action now connects to current survey components, allowing survey forms to open smoothly from Managed Events. |
| Visit Management | Visit record types on mobile displayed alphabetically or defaulted based on database order rather than following the sort order configured in Visit Record Type Mappings. | The mapped visit record types are now displayed in their sort order and default to the primary mapped type while preserving default settings for unmapped accounts. |
| The custom Agentforce interface continued to display an incorrect agent label after switching to a different agent. | The interface now refreshes immediately upon switching to display the name and label of the selected agent. | |
| The Add Discussion action remained available after a default discussion was created, even when the discussion record type was configured to allow only one discussion. | The action is now hidden when a discussion already exists and Limit to 1 Discussion is enabled. |
Version 262.8.0
This patch contains fixes to ensure that the Life Sciences Cloud mobile app features work correctly.
| Feature | Issue | Description |
|---|---|---|
| General | URL-addressable Lightning Web Components (LWCs) that weren't configured as quick actions didn't load correctly on the home page. | Fixed the rendering process for URL-addressable LWCs so they load correctly now. |
Version 262.6.0
This patch contains fixes to ensure that the Life Sciences Cloud mobile app features work correctly.
| Feature | Issue | Description |
|---|---|---|
| Account Management | The Edit action was not appearing on the Account Territory Fields component for users with edit permissions. | Updated component permission evaluation to render the Edit action on the Account Territory Fields component. |
| Renamed custom field labels for Contact Point Address and Contact Point Email weren't updated after syncing metadata. | Updated metadata sync processing so renamed custom field labels now display correctly. | |
| Device sync transaction payloads for Account Filters included unnecessary column label data, increasing file size and slowing down syncs. | Removed redundant column label data from device sync files to reduce data size and speed up syncing. | |
| Editing Contact Point Email or Contact Point Phone records directly from the details page allowed multiple records to be incorrectly set as Primary. | Added validation rules to detail pages to ensure only one contact point can be set as Primary at a time. | |
| The Business License section appeared in the filter field picker even when the field set was configured as None in the Admin Console. | Updated filter settings so the Business License section is correctly hidden when set to None. | |
| The Account detail page displayed raw picklist API codes instead of human-readable labels in the Specialties section. | Updated specialty field rendering logic to resolve and display localized picklist labels instead of API values. | |
| Account Search | Standard fields such as Phone Numbers, Social Identifiers, and National Provider Identifiers were missing from Advanced Search results when querying business licenses. | Updated search result layouts to display all configured standard fields for business license searches. |
| Activity Timeline | Multiple Account and Activity Timeline screens on iPad displayed hard-coded English strings and inconsistent date formats. | Fixed the localization issues and standardized date formatting across Account tabs, rating options, and Activity Timeline calendar filters. |
| Calendar | Submitted visits temporarily appeared as Completed on the calendar before reverting to Planned status after a sync, causing status discrepancies and duplicate entries. | Unified visit completion status detection across calendar views, previews, and record editing checks to maintain consistent Completed status even when synchronization is pending. |
| Event Management | Actions were displayed inconsistently in Participant Type related lists. Some participant types were missing edit and delete icons, while others had non-functional delete options. | Updated participant related list rendering to display edit and delete icons consistently based on user permissions and restored record deletion functionality. |
| Adding attendees to Managed Events caused sync transactions to stall in In Progress status, resulting in duplicate attendee creation during subsequent manual syncs. | Updated attendee invitation count validation rules to prevent sync transaction stalls and duplicate record creation. | |
| The Subject Assignment component displayed a basic record creation form instead of the interactive subject selection table available on desktop site. | Implemented the interactive subject selection table component to provide consistent user experience. | |
| The Sign In Sheet Table exhibited styling discrepancies, including missing header backgrounds, incorrect table background colors, and typography non-compliance with design standards. | Updated Sign In Sheet Table styling and typography to strictly adhere to standard Salesforce Lightning Design System (SLDS) guidelines. | |
| Adding a Write-In attendee with a Participant Response Type of Invited to a Managed Event caused synchronization transactions to fail. | Updated the synchronization logic for Write-In attendees with Invited response status to ensure successful server synchronization. | |
| Synchronization transactions failed when adding an existing event participant a second time under a different Participant Type. | Updated synchronization logic to validate and synchronize duplicate participant records added with different participant roles. | |
| When adding colleagues or experts, an unnecessary System Generated Filter button was displayed that generated permission error messages. | Removed the unnecessary filter button from the selection interface to match desktop site behavior and eliminate error messages. | |
| Action buttons to add subject, participants, or estimated expenses were missing on newly created Managed Events until a manual sync was performed. | Updated event page initialization to render all configured action buttons immediately upon record creation without requiring a manual sync. | |
| The Done button on the Sign In Detail screen remained disabled even after capturing a signature. | Updated the button styling logic so the Done button enabled after a signature is captured. | |
| The checklist popover on the Financials/Expenses tab didn't match standard UI patterns. | Updated checklist popover styling and alignment to conform to standard application UI patterns. | |
| The Uneven Allocation toggle was missing from the Allocate Expense screen, preventing users from splitting expenses unevenly among attendees. | Added the Uneven Allocation toggle to the Allocate Expense screen. | |
| General | Hyperlinks in Rich Text components did not respond to single taps and could only be opened with a long press. | Updated Rich Text components so external and new-window links open with a single tap. |
| Key Account Management | The Edit action was missing for Assessment Task records accessed from the Action Plan related list under Account Plan Objectives. | Enabled the Edit action for Assessment Task records in Account Plan related list. |
| Surveys | The survey screen experienced layout flickering, vertical jitter on rating selection, and unexpected scrolling when changing question inputs. | Improved native input rendering for survey components to eliminate flickering and jitter, ensuring stable screen positions during updates. |
| Visit Management | Tapping Add Discussion on the Visit Detail caused an error for users with only one assigned record type. | Fixed the background caching error so the discussion form fields now load and appear correctly. |
| Sync transactions relied on redundant workaround logic to bypass backend validation triggers. | Streamlined sync transaction routines by removing legacy client-side workarounds, resulting in faster and more reliable synchronization. | |
| The Edit Visitors button was hidden when visibility rules were applied, and the visitor selection modal failed to preselect existing visitors beyond the first page, leading to duplicate record creation. | Updated the component visibility rule evaluation so the Edit Visitors button appears correctly, and ensured all existing visitors are preselected. | |
| The Next Visit Objective Type picklist on Provider Visits on iPad displayed all field picklist values instead of restricting values based on the assigned record type. | Corrected metadata record type resolution for Provider Visits to ensure picklist values are properly filtered according to configured record type restrictions. |
Version 262.4.0
This patch contains fixes to ensure that the Life Sciences Cloud mobile app features work correctly.
| Feature | Issue | Description |
|---|---|---|
| Consent Management | The Capture Consent quick action was missing from the Visit detail page. Although the quick action was configured for Account and Visit creation flows, it was inadvertently omitted from the Visit Record page. | Added the Capture Consent quick action layout and metadata configuration to the Visit Record page. Verified that metadata access and SOQL queries run properly in the mobile at run time to prevent layout loading errors. |
| General | High volumes of uncompressed log uploads from the iOS app caused excessive daily API usage and high server error rates (HTTP 503). | Refactored log upload logic to batch logs at 200 records per API call and enabled gzip compression, keeping payload sizes well within platform limits. Added bounded retry handling for HTTP 429, 503, and 504 status codes to prevent request storms and protect the daily API quota while preventing log loss. |
| Uploading databases larger than 1 GB from an iPad crashed the app due to a Firebase Performance NSURLSession instrumentation conflict that triggered a duplicate call to the URL session completion handler. | Fixed the completion handler invocation in SFRestAPI.send to prevent double-execution during large payload transfers. | |
| Sync Management | When Enhanced Mobile Sync was enabled, visit data (including samples, DTP, marketing items, and select addresses) was missing from the Visit SPA view. | Corrected the Enhanced Mobile Sync database-mapping logic so all record fields are fully captured during bulk uploads, preventing sparse fields from saving as NULL. Also, removed redundant key transformations to streamline sync performance. |
Version 262.2.0
This patch contains fixes to ensure that the Life Sciences Cloud mobile app features work correctly.
| Feature | Issue | Description |
|---|---|---|
| Calendar | In the Calendar view, account names weren't using the Custom Formula field configuration. | Updated the account name configuration lookup so the calendar view correctly reads and renders custom formula field definitions. |
| Event Management | Managed events created outside business hours saved locally but consistently failed during server sync. | Enforced client-side business hours validation during event creation and editing, showing an immediate error message on the mobile app to prevent non-syncable records from saving. |
| Users were unable to complete expense-related tasks on Managed Events due to a permission validation failure on Estimated Expense records. | Corrected the entity association logic for expense workflows to ensure permission checks succeed and users can complete expense operations on Managed Events. | |
| Users experienced an error during initial data synchronization after logging into the mobile application, requiring them to manually tap Retry. | Improved initial sync initialization and error handling so that first-time log-ins complete data synchronization smoothly without manual intervention. | |
| Tapping the Print button on a Managed Event Sign-In Sheet on iPad redirected to a browser with a "Page does not exist" error. | Integrated native iPad printing capabilities into the mobile app, allowing users to print or save event sign-in sheets directly without redirection. | |
| On Managed Event records, content on the Related tab was overlapped and obstructed by the Subject Assignment section. | Adjusted page layout positioning and scrolling boundaries to ensure all related records are fully visible and accessible on mobile. | |
| Attendees added to a Managed Event on web didn't display in the mobile app, causing attendee status discrepancies. | Updated data synchronization logic to ensure attendees added on web properly sync and reflect accurately on mobile. | |
| Managed Events could be saved with an End Date and Time earlier than the Start Date and Time, resulting in synchronization errors. | Added client-side date and time validation to prevent saving events with invalid time ranges and display an immediate validation message. | |
| Managed Events created during Time Off Territory (TOT) periods could be saved without warning, failing only when submitted for approval later. | Enforced Time Off Territory (TOT) overlap validation during event creation and editing on mobile to inform users of schedule conflicts immediately. | |
| Users couldn't add colleagues to Managed Events due to an inaccessible field error on Participant Role. | Updated field accessibility handling for Participant Role, allowing users to successfully add colleagues to Managed Events. | |
| Tapping the Save button didn't submit or save changes when editing details on a Managed Event record on mobile. | Updated mobile event configuration mappings and event handlers to ensure updates to Managed Event details are properly saved. | |
| The Sign In Sheet on Managed Events didn't indicate when an attendee was already signed in, allowing duplicate sign-in entries. | Added clear visual status indicators and disabled the Sign In button for previously signed-in attendees to prevent duplicate entries. | |
| General | The Account tab was taking over two minutes to load in environments with large account datasets. | Optimized mobile query execution, data caching, and implemented incremental loading for the Account tab. Account lists now load within expected time frames. |
| The app was crashing immediately after a data sync. | Enhanced error handling and memory management within the sync completion workflow, preventing app crashes and ensuring stable background sync processing across large datasets. | |
| The mobile app crashed unexpectedly when downloading Content Version files (CLM documents). | Updated underlying mobile SDK dependencies to resolve the download failure and ensure app stability when opening CLM documents. | |
| Admin Console settings configured for the mobile application (such as View Online, default browser, and Kanban view) were not being enforced on iPad devices. | Fixed setting persistence and configuration decoding to ensure that all Mobile Admin Console settings are accurately applied on iPad. | |
| Records updated while working offline didn't immediately reflect updated data in Mobile Lightning Web Components (LWCs). | Corrected offline cache invalidation and component re-rendering to ensure Mobile LWCs accurately display modified data while offline. | |
| Intelligent Content | Opening the Email wizard from Account Quick Actions on iPad caused significant UI freezes due to unthrottled background template downloads. Furthermore, going to template selection before downloads finish showed an incorrect "Data Not Available" message. | Optimized background template downloading by limiting parallel network requests and fixing thread synchronization issues. Replaced the empty-state page with a clear download loading indicator to keep the UI smooth and responsive. |
| Visit Management | Reusing the same pre-defined prompt in Visit Agent during a single session failed to inject the utterance after closing and reopening the Agentforce window. | Corrected session state resetting so pre-defined Visit Agent prompts can be clicked and injected multiple times within the same session. |
| Required field asterisks configured on Provider Visit Product Discussion page layouts didn't appear on the mobile Visit Engagement screen. | Updated mobile UI rendering to properly display required field indicators (*), aligning field validation visual cues between web and mobile. | |
| Page layout requirement rules for the Channel field on Visit records were not enforced on mobile, and the Schedule Next Visit dialog incorrectly enforced required field checks. | Enforced page layout validation rules for the Channel field on Visit records, and updated the Schedule Next Visit window so the Channel field remains editable without being required, matching web behavior. | |
| Pre-Provider Visit Notes were not carried over from the last submitted Visit when creating a new Visit for an Account. | Updated Visit creation logic to automatically populate Pre-Provider Visit Notes from the previous Visit's objectives, maintaining field precedence rules and matching web behavior. | |
| On iPad devices connected to an external mouse and keyboard, clicking the overflow menu button on the Visit Engagement page caused the cursor to jump away, preventing selection. | Fixed pointer interaction handling on header components so users can seamlessly interact with overflow menus when using an external mouse on iPad. | |
| The mobile app crashed when submitting a Provider Visit if the Planned Start Time was set later than the Planned End Time. | Added time range validation checks to gracefully handle inverted time ranges and display a validation error instead of causing an app crash. | |
| When an iPad device language was set to a non-English locale, attempting to save a Visit on a weekday displayed an error stating the visit must be scheduled on a working weekday. | Updated working weekday validation to evaluate date components using Salesforce user locale settings instead of device language settings, allowing visits to be saved on working weekdays. | |
| Selecting a related address for a new Visit on mobile didn't automatically populate the Parent Organization ID upon initial selection. | Updated address selection logic to immediately resolve and populate the Parent Organization ID without requiring page refreshes. |
Did this article solve your issue?
Let us know so we can improve!
