---
title: "Version 1.27 Release Notes"
slug: "version-127-release-notes"
updated: 2025-09-05T13:25:56Z
published: 2025-09-05T13:25:56Z
canonical: "docs.relaynetwork.com/version-127-release-notes"
excludeFromExternalSearch: true
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.relaynetwork.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Version 1.27 Release Notes

**Release Date:** September 5, 2025

**Installation URL**: [https://login.salesforce.com/packaging/installPackage.apexp?p0=04tUH000000ZyxNYAS](https://login.salesforce.com/packaging/installPackage.apexp?p0=04tUH000000ZyxNYAS)

## ⚠️ BREAKING CHANGES

### Legacy Named Credentials

- 🛑 The option to use legacy named credentials is no longer supported. Legacy named credentials have long been deprecated by Sales*f*orce.

---

## 💫 WHAT’S NEW

### Flow Actions

- 🔥Converted ***all*** Relay Flow actions to use background jobs instead of running in a **future.** This resolved some confusion on how to properly configure its execution when running in a Flow **asynchronous path**. A second benefit is that the Relay flow actions now perform automatic batching of calls to Relay - greatly reducing the complexity of your flows. Previously you would have to manage the batching with Flow loops, collections, and branching logic.

#### Relay Onboarding Action

- The **RelayOnboardRequest** object now accepts an optional **RelayDynamicInputs** collection.

See: [Apex RelayOnboardingRequest](/docs/relayonboardingrequest)

#### Relay Message Action

- Internal batching of calls to Relay. Previously, large batches of messaging requests had to be broken up into blocks of 200 using a combination of Flow variables and branching logic. The updated Messaging action, will now automatically preform batching. If processing a large batch, it is recommended to set the action’s **Use background job** property to **true**.
- The **RelayMessagingRequest** object now takes an optional **RelayDynamicInputs** collection.

See: [RelayMessageAction](/docs/messaging-action)

## Objects

### RelayEvents__c New Fields

- **Lb_name__c** → (Launched By Name). Contains the name of the person or service that initiated a Relay call such as onboarding or messaging
- **Lb_source__c** → (Launched by Source System). Contains the name of the service that called initiated a Relay call such as onboarding or messaging.
- **RootTriggerId** →
- **RootTriggerNickname** →
- **RootClientTriggerId** →
- **StepName** →

### LWC

See: [Configure Relay Message List LWC](/docs/configure-relay-message-list-component)

- **Improved Message Preview** → The formatting of the message preview has been improved.
- **New Refresh Button** → A new refresh button has been added to the control. Clicking the button, will cause the all of the message status’ to refresh. This is more performant than refreshing the browser page to get an update on an experience that was just sent.
- **New Configuration Properties** → The following new properties are now available on the LWC’s configuration page.
  - **Launched By Name** → Optional property. Identifies the name of the user that made the callout to Relay.
  - **Launched By Source** → Optional property. Identifies the source service / system that made the callout to Relay.
- **Mark Message as Read-only** → You can now mark individual messages as read-only. When a message is marked as read-only, the agent will not be able to manually send the message to a user. However, all status updates will be displayed. This is typically used to show the status of a message that is triggered by a backend process (e.g. Flow). To mark a message as read-only:
  - Login to the the Relay CXB
  - Edit the experience that contains the message
  - Located the message and click the **Inspect** button
  - In the **Inspect** dialog, add a label with the following value: **sfdc_readonly**
  - Save the change and close the **Inspect** dialog
  - Publish the experience to **COMPLETE** from the **DRAFT** state

---

## Sales*f*orce API Version

The Sales*f*orce API version for the Relay package has been upgrade to 63.

An Apex callout enables you to tightly integrate your Apex with an external service by making a call to an external Web service or sending a HTTP request from Apex code and then receiving the response. Apex provides integration with Web services that utilize SOAP and WSDL, or HTTP services (RESTful services).

Triggering refers to sending the user an SMS text message that contains a personalized URL. The URL will take the user to their personalize Feed.