You are here:
Patch Releases Winter `27
We release patches periodically. Check back here for information on each Winter `27 patch release for the Life Sciences Cloud for Customer Engagement package.
Winter `27 Release
To view the release notes for Winter `27,see Life Sciences.
To view patch release notes for the Life Sciences Cloud mobile app,see Patch Releases Winter `27.
Version 264.4.0.0
This patch contains fixes to ensure that the Life Sciences Clouds for Customer Engagement features work correctly.
| Feature | Issue | Description |
|---|---|---|
| Inventory Management | In the Return to Sender window, users could save the record without completing required fields, and custom fields added to the standard field sets sometimes didn't appear. | The Return to Sender window now enforces required fields before saving and displays the custom fields added to its field sets. |
| When users entered an actual count of 0 during an Inventory Count, the product batch item's remaining quantity was cleared instead of set to zero, and the batch item was marked inactive. | Entering an actual count of 0 now sets the product batch item's remaining quantity to zero and keeps the batch item active. | |
| Visit Management | Users couldn't launch a future-dated Remote Visit that had no Samples or DTPs because a validation incorrectly blocked the action. The same visit could be launched on mobile. | Users can now launch a future-dated Remote Visit without Samples or DTPs on the desktop site, matching the behavior on the Life Sciences Cloud mobile app. |
| On the web, the Survey Status values In Progress and Completed on the Visit Surveys tab appeared in English regardless of the user's language. | All Survey Status values on the Visit Surveys tab now display in the user's language. |
Version 264.3.0.0
This patch contains fixes to ensure that the Life Sciences Clouds for Customer Engagement features work correctly.
| Feature | Issue | Description |
|---|---|---|
| Account Search | Creating a Provider Affiliation record displayed the record type selection screen even when only one record type was available. | The record creation workflow now automatically selects the single available record type and skips the selection screen. |
| When a duplicate rule blocked account creation, correcting duplicate values caused the Create button to disappear, requiring field reps to restart the workflow. | The Create button now stays available after duplicate values are corrected, allowing field reps to save without reopening the window. | |
| Consent Management | The Capture Consent quick action was missing from the visit engagement page, preventing field reps from recording consent from that workspace. | The Capture Consent quick action button now appears on the Visit Engagement page. |
| Entering edit mode on a record with captured verbal consent left the Verbal Consent checkbox selected instead of resetting like other consent proof types. | The Verbal Consent checkbox now resets when entering edit mode, matching other proof types, and retains its original value if editing is canceled. | |
| Remote Engagement emails stayed stuck in retry status and couldn't deliver to contacts with configured email addresses due to an unexpected verification error. | Remote Engagement emails now deliver successfully to contacts with configured email addresses without triggering sender verification errors. | |
| Event Management | Monetary cap recalculations failed whenever cap criteria referenced a field through a custom lookup relationship. | Cap criteria evaluation has been updated to support custom lookup relationships so monetary cap recalculations complete successfully. |
| Updating or deleting an estimated expense allocation didn't recalculate total expenses, which allowed subsequent allocations to exceed monetary caps without warning. | Deleting or updating an expense allocation now recalculates total expenses, ensuring monetary cap spending limits are enforced accurately. | |
| Estimated expense allocations that aren't created through the Managed Event record page couldn't be blocked if they exceeded parent estimated expense amounts. | The validation now blocks any participant allocation that exceeds parent estimated expense amounts regardless of how the record is created. | |
| Estimated expense allocations that aren't created through the Managed Event record page could save for participants assigned to a different event. | The validation has been updated to ensure participant allocations save only when the participant belongs to the same event as the expense. | |
| When no allowed attendance statuses were configured for visits, the window for creating visits displayed all attendees, including those with invalid statuses. | The window for creating visits now shows no attendees when attendance statuses aren't configured and provides clear setup guidance to administrators. | |
| General | Default values based on record merge fields were left out of Generic Workflow Record Update actions, leaving form fields blank upon opening. | Default value handling now populates record merge field values in action forms and applies them when saved. |
| Generic Workflow | Experience Site users couldn't save updates to communication subscription preferences because an internal workflow permission check incorrectly blocked them. | The workflow permission check for Experience Site users has been bypassed so that communication subscription preference updates save successfully. |
| Product Management | Users assigned cloned versions of the admin permission set were denied access to administrative areas like product hierarchy because checks relied on exact API names. | Permission checks now evaluate granted permissions rather than hardcoded permission set names, granting the expected access to the cloned permission sets |
| Screen readers didn't announce field validation error messages because errors weren't connected to their input fields. | Validation error handling has been updated so that error messages are now associated with the respective fields and are announced by screen readers. | |
| Remote Engagement | During a Twilio Remote Engagement video call on mobile, participant views didn't use the full screen, causing join buttons and call controls to appear offscreen. | Updated the mobile participant video view to occupy the full screen so all call controls stay visible and accessible. |
| The mobile participant view in Twilio Remote Engagement displayed large empty side margins, reducing usable viewing area for call content. | The mobile participant view layout has been adjusted to use the entire available screen width while keeping call controls accessible. | |
| Opening a Remote Engagement session on mobile Safari cropped the signature capture area and More Info options, making them inaccessible. | On the mobile, Safari now renders the signature capture area and More Info options in full view during Remote Engagement sessions. | |
| When ending a Remote Engagement session in Spanish, the confirmation dialog and End Session button appeared in English. | The End Remote Engagement confirmation dialog and button now displays text in the user's configured language. | |
| The Start Remote Engagement button appeared on Microsoft Teams visits launching a non-functional video screen. Remote Engagement video calls are strictly supported for Twilio visits. | The Start Remote Engagement button now appears only for Twilio video visits and remains hidden for Microsoft Teams visits. | |
| Sample Inventory Management | Field reps couldn't submit an inventory count assessment when the actual stock count was zero. | The submission validation has been updated so that field reps can successfully submit inventory count assessments with zero stock. |
| Safeguards that prevent duplicate inventory count submissions weren't scoped to the record owner and location, causing valid submissions to be blocked. | Duplicate submission safeguards now evaluate owner and location criteria, preventing valid inventory count submissions from being blocked. | |
| Store Check | Opening the web calendar while a Store Check visit was in progress returned an error and prevented the calendar from loading. | The web calendar now loads correctly when a Store Check visit is in progress. |
| Visit Management | Editing a visit failed to set the Visit record type from the configured Account Visit record type mapping, even though the mapping worked fine when creating a visit. | The Visit Engagement form now applies Account Visit record type mappings consistently when editing visits or changing accounts. |
| The Status field on the visit creation screen remained editable and showed unauthorized values despite being configured as read-only. | The visit creation screen now enforces read-only configurations on the Status field and automatically sets the default values. |
Version 264.1.0.0
This patch contains fixes to ensure that the Life Sciences Clouds for Customer Engagement features work correctly.
| Feature | Issue | Description |
|---|---|---|
| General | When adding subjects to an event, the system-generated filter excluded active subjects with blank start or end dates, preventing valid subjects from appearing in search results. | The subject search now includes active subjects whose applicable date range overlaps with the event, including subjects with a blank start or end date. |
Did this article solve your issue?
Let us know so we can improve!
