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 for Customer Engagement package.
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 mobile app, see Patch Releases Summer `26.
Version 262.15.0.0
This patch contains fixes to ensure that the Life Sciences Clouds for Customer Engagement features work correctly.
| Feature | Issue | Description |
|---|---|---|
| Consent Management | Users without an authorized consent-management role could update participant consent records on events, such as marking invitations or attendance as paper-signed, leading to inaccurate regulated consent information. | The consent upload process now verifies user authorization before processing updates, ensuring only authorized users can change participant consent statuses. |
| General | Filter and sort inputs used when selecting object were not properly validated, which could allow a user to retrieve records beyond their permitted visibility. | Filter and sort inputs are now validated, so users can retrieve only the records they are permitted to access. |
| Intelligent Content | Users without the required administrative permission could initiate email-fragment sharing across information beyond their normal access. | Email fragment sharing now enforces the required permission, so only authorized users can start the process. |
| The content stored in a presentation or email template could run in another authenticated user's browser when the content was opened in the web email template editor. This could expose information or allow unauthorized actions and content changes. | The email template editor now handles records securely to prevent stored values from running unauthorized browser actions. | |
| Key Account Management | Users without the required permissions could create assessment tasks and action plan items for account plans, potentially adding unauthorized or inaccurate planning information. | Saving assessment tasks and action plan items now checks user permissions, so records are created only for users with the appropriate access. |
| Remote Engagement | During a remote engagement session, enabling the field rep's camera while sharing content resized the shared content and cropped part of it. This could prevent attendees from seeing the complete approved, safety, or regulatory content. | The shared-content layout now stays intact when the rep turns their camera on or off during screen sharing, keeping the full content visible throughout the session. |
| When a guest enabled their camera while a field rep was sharing content, the attendee's video took over the full screen and hid the shared content. | The session layout is now corrected so that shared content remains in the main viewing area and the guest's camera appears in a smaller video tile without interrupting the presentation. | |
| Visit Management | In a remote Twilio visit, requesting a signature for the parent visit after adding samples and DTP displayed a validation error. | Signature validation is now corrected so that users can request a signature for the parent visit without an error. |
| Completing a remote Twilio visit with products and an approved signature created disbursement and requested-sample records, but failed to deduct or update sample limits. | Remote Twilio visits now create the sample limit transaction records and correctly deduct sample limits when a visit is submitted after a product signature is approved. | |
| Field reps could not open the switch account list in the visit engagement flow. It returned an internal server error and no accounts loaded, which prevented these reps from logging visits. | Field reps can open switch account, view the accounts and healthcare providers aligned to their territories, and continue logging the visit. |
Version 262.14.0.0
This patch contains fixes to ensure that the Life Sciences Clouds for Customer Engagement features work correctly.
| Feature | Issue | Description |
|---|---|---|
| Account Search | In Advanced Search, users were unable to locate accounts outside their assigned territory unless they had read access to the account records. | Advanced Search now correctly returns matching accounts regardless of territory or sharing permissions. |
Version 262.14.0.0
This patch contains fixes to ensure that the Life Sciences Clouds for Customer Engagement features work correctly.
| Feature | Issue | Description |
|---|---|---|
| Account Search | In Advanced Search, users were unable to locate accounts outside their assigned territory unless they had read access to the account records. | Advanced Search now correctly returns matching accounts regardless of territory or sharing permissions. |
Version 262.13.0.0
This patch contains fixes to ensure that the Life Sciences Clouds for Customer Engagement features work correctly.
| Feature | Issue | Description |
|---|---|---|
| Account Management | Data Change Requests couldn't be created or approved when profile-based creation was disabled, updates used system mode, or the user's country configurations differed from record types. | Data Change Request processing now supports creation with the profile setting disabled, approval of updated records in system mode, and creation across mismatched country and record-type settings. |
| Event Management | Field reps received an access-denied error when attempting to launch a group Visit from an approved Managed Event. | The required group-Visit controller is now included in the Life Sciences core permission set, giving eligible field reps access to the launch group visit. |
| General | Administrative setting labels in the mobile app, such as Metadata Cache and Object settings, were displayed in English regardless of the user's configured language. | Headings, fields, filters, operators, actions, placeholders, and notifications on administration screens can now be translated. |
| Intelligent Content | Users couldn't move forward or backward within videos in multichannel presentations, even though the same videos worked correctly on an iPad. | The presentation player now responds to the video progress control, so users can move forward or backward within videos. |
| The Intelligent Content presentation player displayed the email action twice. | The presentation player now displays the email action just once. | |
| Sending or canceling an email from a visit redirected users to an invalid URL. | The email wizard now decodes the encoded return path before building the redirect URL, returning users to the Visit detail page. | |
| The Send Email consent flow prompted users to draw a signature even though signature capture was not supported, resulting in consent records that did not retain the signature. | The consent flow no longer displays the unsupported signature option, preventing users from providing a signature that cannot be saved. | |
| Presentations created in Intelligent Content on an iPad did not appear in My Presentations on the Desktop site after synchronization. | My Presentations on the desktop site now displays presentations created and synchronized from the mobile app. | |
| The email batch process continued retrying failed emails beyond the configured limit and sent emails through the substitute-address workflow even when records were no longer marked to be sent. | Failed emails are now excluded from further retry and send attempts once they reach the configured retry limit. | |
| Inventory Management | The Description field on the Create Product Request and View Product Request Create pages used different labels. | The Product Request pages now use the same label for the Description field. |
| Visit Management | Users could clear a required number field while editing a visit and save the record without receiving a required-field error. | Required number fields are now validated when users edit a visit, preventing them from saving until they enter a value. |
| Submitting an edited visit deleted assessment tasks created outside the visit workspace because those tasks were omitted from the visit submission data. | Visit submission now preserves Assessment Tasks created outside the visit workspace while continuing to process task changes made within the visit workflow. | |
| The Visit Engagement page loaded slowly and inconsistently when opened for the first time due to delays in retrieving label resources. | Label resources now load more efficiently, reducing initial loading delays on the Visit Engagement page. | |
| Remote Engagement | During a remote engagement, a consent signature prompt briefly appeared at the top of the page or remained displayed after the request was canceled. | Consent signature prompts now open and close within the consent panel without appearing elsewhere on the remote engagement page. |
| During a remote engagement, hosts lost access to the presentation controls after turning on their camera. | Presentation controls now remain visible and available while the host's camera is turned on. | |
| During a remote engagement, a participant's camera feed could disappear when the host turned on their camera, and the host lost access to camera visibility controls. | Participant camera feeds now remain visible when the host turns on their camera, and hosts maintain access to the camera-feed visibility control. | |
| During remote engagements, participant video disappeared after the host enabled their camera, presentation menu buttons stopped responding, and the right navigation arrow disappeared upon resizing the window. | Participant video now remains visible, presentation menu controls stay responsive when the host's camera is on, and slide navigation arrows remain available at supported window sizes. | |
| When a host requested a signature while sharing a presentation, participants could see the host's signature request form or action menu. | Signature request forms and related host controls are no longer visible to participants when a presentation is shared. | |
| When on-device HCP consent was enabled, a consent signature request sent to a mobile participant expired immediately and hosts received an error notification with no explanation. | Mobile participants can now complete consent signature requests when on-device HCP consent is enabled, and hosts receive a clear notification if an error occurs. | |
| After a host rejected a signature and requested another, the Approve option appeared too soon and opened an empty signature window. | Signature updates now apply only to the current request, so a rejected request cannot change the status of a signature request. | |
| Remote engagement failed to start because the conference launcher could not access the call identifier required by the host component. | The host component's call identifier is now accessible to the conference launcher, allowing the remote engagement to start. |
Version 262.12.0.0
This patch contains fixes to ensure that the Life Sciences Clouds for Customer Engagement features work correctly.
| Feature | Issue | Description |
|---|---|---|
| Account Search | Record type-specific picklist values were not enforced on ContactPointAddress fields during SBC Account creation, allowing restricted picklist options to appear on the Account Creation screen. | Updated the account creation flow to enforce record type-specific picklist restrictions so users only see and select valid picklist values. |
| Labels on the Account Additional Information tab and account registration menu appeared in English regardless of localized settings. | Added full localization support to Account Additional Information tab and account registration menu labels. | |
| Activity Timeline | Changes to Activity Timeline Visibility Settings (in the Admin Console) for the Visit object were not saved when selecting a field set. | Fixed configuration persistence logic in the Admin Console to properly save Activity Timeline field set settings for the Visit object. |
| Event Management | Updating event participant records triggered unnecessary quota recalculation queries even when quota-related fields were unchanged, degrading system performance. | Added field-change guards so quota recalculations run only when relevant fields, such as Response Status or Attributed To, are updated. |
| Saving a large number of attendees on a Managed Event experienced delays due to small transaction chunk sizes. | Increased the batch processing chunk size for attendee updates on Managed Events, significantly reducing save times while remaining within platform governor limits. | |
| Pagination requests in the Update Attendees screen transferred redundant record ID data, slowing screen performance. | Optimized pagination request payloads in the Update Attendees window by removing redundant record references, improving screen responsiveness. | |
| Selecting accounts in the Update Attendees window caused the web UI to freeze temporarily in territories with large account datasets. | Improved front-end component performance in the Update Attendees window to ensure instant checkbox selection without UI responsiveness issues. | |
| The Estimated Expense Allocation screen filtered available participants using actual expense rules rather than estimated expense configurations. | Updated participant filtering logic in the Estimated Expense Allocation screen to correctly apply estimated expense configuration rules. | |
| General | Navigating to Account Team Member records from the related list caused a JavaScript error when handling toast notifications that were missing expected parameters. | Added null guards and parameter validation to toast notification handlers in generic related lists to ensure smooth navigation. |
| Home Page | On desktop site, the Up Next (Upcoming Agenda) home page component incorrectly listed completed visits alongside planned visits. | Updated component filtering to exclude completed visits, ensuring only planned upcoming visits appear across desktop and mobile platforms. |
| Intelligent Content | Unsupported PDF presentations appeared as selectable options in the New Custom Presentation creation window. | Updated the custom presentation creation window to filter out PDF presentations, ensuring only supported presentation formats are displayed. |
| Certain email UI elements, including help links, picklist values, status values, and call-to-action buttons, were displayed in English regardless of localized language settings. | Updated UI labels, status values, and action buttons across email features to appropriately support multi-language localization. | |
| Filter labels and UI elements on the Intelligent Content Filter screen were displayed in English regardless of language settings. | Localized all UI text and filter labels on the Intelligent Content Filter screen to align with the user's selected language. | |
| License Management | The "Modify Formulas on Business License Object" log label in License Management was hardcoded in English. | Added localization support for log labels in License Management to align with the user's language settings. |
| Lists and Filters | Saving a newly created, empty Account Filter failed with a ListException error when adding the initial field via "Select Fields to Display." | Resolved field creation handling logic for empty filters so initial field additions save successfully. |
| Remote Engagement | A malformed participant identity in a video consultation room could cause participant connection failures for health care providers and field representatives. | Added server-side validation and error handling for participant identities during video room connections to ensure stable, reliable consultation sessions. |
| The Consent Details window displayed Contact Point names instead of Engagement Channel Type names. | Updated the Consent Details window to display Engagement Channel Type names, providing clear visibility into communication channels associated with consent records. | |
| Rescheduling a virtual visit sent reschedule email notifications containing incorrect meeting IDs to attendees, impacting participant joining and attendance tracking. | Updated reschedule email notification logic to send each attendee their unique and correct meeting ID. | |
| Sales Data | Scrolling the Measure Total Summary table on the Sales chart component caused a null pointer error and disrupted chart rendering. | Fixed scroll event handling in the Measure summary table to prevent null object errors and maintain continuous chart visibility. |
| Sample Limits | Assigning templates to products failed with an Apex heap size limit error in orgs with large product catalogs. | Optimized the product hierarchy query and rendering logic to stay within governor limits, allowing successful template assignments regardless of product catalog size. |
| Visit Management | Creating a visit with specific products failed with a SOQL governor limit error when sample limit validation was enabled in Admin Console. | Optimized sample limits validation queries during visit creation to eliminate governor limit errors and ensure smooth visit creation. |
Version 262.10.0.0
This patch contains fixes to ensure that the Life Sciences Clouds for Customer Engagement features work correctly.
| Feature | Issue | Description |
|---|---|---|
| Data Change Requests | When creating accounts with associated addresses, affiliations, or specialties, child Data Change Requests (DCRs) were generated without linking to their parent DCR, breaking parent-child DCR relationships. | Resolved a mapping failure during record creation to ensure parent DCR IDs are propagated to all child DCRs across both Desktop site and Life Sciences Cloud Mobile app. |
| Data Change Requests (DCR) for Healthcare Provider Specialty records failed to trigger when specific managed fields were updated, despite deploying recommended package updates. | Resolved the nested trigger conflict where the DCR validity state was incorrectly shared across objects. Scoped the validity state evaluation per SObjectType to prevent cross-trigger interference and ensure DCRs trigger as expected. |
Version 262.9.0.0
This patch contains fixes to ensure that the Life Sciences Clouds for Customer Engagement features work correctly.
| Feature | Issue | Description |
|---|---|---|
| Activity Timeline | Visits weren’t appearing on the Activity Timeline tab of Account records, preventing users from seeing full account engagement history. | Corrected the activity query and filtering logic for Account Activity Timelines. All visit activities now properly render in the timeline display. |
| Event Management | When adding actual or estimated expenses to a managed event, the Expense Type dropdown incorrectly showed options meant only for visits. | Updated the filtering logic for Managed Event expense types so that only options designated for Managed Event are shown. |
| Users were unable to allocate Managed Event expenses to write-in or non-profiled attendees because those attendee types were missing from the Allocate Expense window. | Non-profiled and write-in attendees are now correctly shown in the Allocate Expense window based on event settings. | |
| Updating the Invitation-Sent status for an event organizer failed when attendees were present on the event. | Fixed the database query responsible for generating territory sharing records, allowing organizer invitation statuses to be updated when attendees are attached. | |
| The MonetaryCapsRecalculationJob batch job failed due to Apex CPU time limit timeouts caused by redundant sorting of incoming records. | Removed the background sorting step, optimizing CPU performance, and allowing the batch calculations to finish without timing out. | |
| General | Date and time fields appeared in an incorrect format within the LSCGenericRelatedList Aura component. | Corrected the custom implementation to ensure the date and time appear accurately across the LSCGenericRelatedList component. |
| Access Check Failed error pop-ups appeared repeatedly when accessing or managing configurations on the Trigger Handlers page in the Admin Console. | Added the missing orderByField and sortingOrder attribute declarations to the component and updated access-check handling. This change prevents internal server errors (GACKs) and allows admins to sort and manage trigger handlers. | |
| Guest Users | Guest users were unable to complete self-registration on Experience Cloud sites sandboxes due to system permission errors when accessing restricted object types. | Updated the underlying package classes to resolve references to restricted objects dynamically. This change prevents class-load failures during unauthenticated sessions and restores guest self-registration functionality. |
| Intelligent Content | Text elements in the Intelligent Content admin console and presentation views didn’t support language translations. | Replaced all hardcoded text strings with custom labels to support localization, translation, and consistent UI messaging across all Intelligent Content workflows. |
| When Drawing mode was enabled during a presentation, the Menu Player trigger icon disappeared from the page, preventing users from reopening the navigation menu. | Updated the presentation player layout so the Menu Player trigger icon remains visible and functional when Drawing mode is active. | |
| Hyperlinks embedded within PDFs weren’t clickable in Intelligent Content. | All embedded links in Intelligent Content are now fully interactive and clickable. | |
| Sample Limits | When running batch jobs to assign multiple cloned templates for the same product to an account, the existing Product and Service Lifecycle (PSL) records were incorrectly updated instead of creating records. | Updated the batch assignment processing logic to make sure that assigning multiple cloned templates for the same product generates new PSL records as intended, preventing existing records from being overwritten. |
| Visit Engagement | The General section header in Pre-Provider Visit Notes was missing from the Visit Engagement window on the desktop site, despite appearing correctly in the mobile app. | Updated the desktop Visit Engagement component to make sure that General header and its translations render correctly on the desktop site. |
Version 262.8.0.0
This patch contains fixes to ensure that the Life Sciences Cloud for Customer Engagement features work correctly.
| Feature | Issue | Description |
|---|---|---|
| Guest Users | Unauthenticated users were able to bypass access checks and exfiltrate person account data, including Personally Identifiable Information (PII). | Enforced strict authentication and object-level access checks within the performAction method. Unauthenticated requests are now rejected across all execution paths, preventing unauthorized data access while preserving standard functionality for valid users. |
| Unauthenticated guest users were able to access restricted ContentDocument files. | Updated the underlying presentation controller to enforce user access permissions, blocking unauthorized access to private documents |
Version 262.7.0.0
This patch contains fixes to ensure that the Life Sciences Cloud for Customer Engagement features work correctly.
| Feature | Issue | Description |
|---|---|---|
| Guest Users | Unauthenticated guest users were unable to self-register on Experience Cloud sites in sandboxes due to system permission errors when attempting to create person accounts. | Updated the underlying package classes to handle data types dynamically rather than relying on restricted system objects. This change removes permission barriers during class compilation and restores guest self-registration. |
Version 262.4.0.0
This patch contains fixes to ensure that the Life Sciences Clouds for Customer Engagement features work correctly.
| Feature | Issue | Description |
|---|---|---|
| Package Updates | Automated package updates failed if quote preferences were turned off. | We removed dependencies on quotes so package updates install smoothly. |
Version 262.3.0.0
This patch contains fixes to ensure that the Life Sciences Cloud for Customer Engagement features work correctly.
| Feature | Issue | Description |
|---|---|---|
| Package Updates | Automated package updates failed to install due to compilation failures when accessing picklist fields. | We updated how picklist field values are retrieved to ensure package updates install smoothly. As a temporary measure, record type filtering is removed for all account-related objects. |
Did this article solve your issue?
Let us know so we can improve!
