--- title: "Version 2.27" slug: "version-227" updated: 2025-09-03T14:13:49Z published: 2025-09-03T14:13:49Z canonical: "docs.relaynetwork.com/version-227" 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 2.27 ## ⚠️ BREAKING CHANGES ### Named Credentials > [!NOTE] > NOTE > > The Relay package post-install script will send you an email if your named credentials require updating. In order to support the new feature of retrieving Relay Power-up Form PDFs, we had to change the *URL* setting of the Relay *Named Credentials* setting. - Edit your **RelayNetwork** *Named Credential.* - Edit the URL parameter and remove the **/platform/v3/api** portion from the path. The URL value should now only contain the Relay domain name and no additional path values. - Edit the Name field and update it to include your Relay Client ID. The new Name format is **RelayNetwork_{client_id}** where **{client_id}** is your Relay Network Client ID. e.g. If you client Id is **onetrustbank**, then the Name field ***must*** be set to **RelayNetwork_onetrustbank**. See: [Named Credentials](/docs/configure-named-credentials) ### 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. --- ## 🐜 BUG FIXES - **LWC:** Fixed an issue where the correct status for sent messages was not properly displayed. This was a rare case which required a complicated pattern of events to be sent. - The **Launched By** property was not being properly set during batch messaging. --- ## πŸ’« WHAT’S NEW ### Flow Actions #### Relay Power-up PDF Download A new Flow action has been added that allows you to download PDFs, generated via a Relay Power-up form, and add it as a file to any object in Salesforce. See: [Relay Pull PDF Action](/docs/relaypullpdfaction) #### Relay Power-up Attachment Download A new Flow action has been added that allows you to download file attachments, uploaded via a Relay Power-up form, and add it as a file to any object in Salesforce. See: [Relay Pull Attachment Action](/docs/relay-pull-attachment-action) ### LWC - **New Refresh Button** β†’ Added a **refresh** icon button, to the top of the component. Clicking the button will refresh the status of the experiences. This is more efficient than refreshing the entire browser page. - **Message Preview β†’** Improved the formatting of the message preview - **Send Button Changes β†’** When the LWC is configured to allow sending multiple messages, the **send** button on each individual experience was removed. The agent must use the **send** button at the top of the component. This was to remove confusion for the agent sending messages as sometimes they would use the **send** button on the individual message thinking all of the selected messages would be sent which was not the case. #### New Configuration Properties | Property | Description | | --- | --- | | Top-of-Feed Trigger | Optional property. Often used in conjunction with sending multiple messages at a time. Specify a Relay message trigger id that is configure to send the user to the top of their Feed. | | Last 4 SSN | Optional property. Specify a field name that contains the last 4 digits of an SSN. | | Launched By Name | Optional property. Allows you to override **who** triggered the Relay experiences. If left blank the default value will be the Sales*f*orce user name who triggered the messages. | | Launched By Source | Optional property. Allows you to override the **source** that triggered the Relay experiences. If left blank the default value will be set to **salesforce**. | #### 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:** 1. Login to the the Relay CXB 2. Edit the experience that contains the message 3. Located the message and click the `Inspect` button 4. In the **Inspect** dialog, add a label with the following value: `sfdc_readonly` 5. Save the change and close the **Inspect** dialog 6. Publish the experience to `COMPLETE` from the `DRAFT` state --- ## πŸͺ„ ENHANCEMENTS ## 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. ### New Flow Actions - **Relay Power-up PDF Download -** Provides the ability to download Power-up Forms (completed by users in the Relay Feed) as a PDF and associate them as Attachments to the correct Account/Contact/etc. - **Relay Power-up Attachment Download -** Provides the ability to download Power-up File attachments and images (upload by users in the Relay Feed) and associate them as Attachments to the correct Account/Contact/etc. ### Onboarding Action The following properties were added to the **RelayOnboardingRequest** object: - **clientMessageTag β†’** Optionally set the **clientMessageTag** value. This value is not used by Relay, however, it will be included in all **RelayEvents__c** objects associated with this onboarding action. - **launchedByName β†’** Optional. Allows you to override **who** onboarded the user(s) to Relay. If left blank the default value will be the Sales*f*orce user name who triggered the messages. - **launchedBySource β†’** Optional. Allows you to override the **source** that onboarded the user(s) to Relay. If left blank the default value will be set to **salesforce**. - **dynamicInputs** β†’ Optional. Allows you to provide a collection of dynamic input name and value pairs to be used with the triggered onboarding message. ### Messaging Action The following properties were added to the **RelayMessagingRequest** object: - **dynamicInputs** β†’ Optional. Allows you to provide a collection of dynamic input name and value pairs to be used with the triggered onboarding message. The following properties were added to the **RelayMessageActionRequest** object: - **launchedByName β†’** Optional. Allows you to override **who** onboarded the user(s) to Relay. If left blank the default value will be the Sales*f*orce user name who triggered the messages. - **launchedBySource β†’** Optional. Allows you to override the **source** that onboarded the user(s) to Relay. If left blank the default value will be set to **salesforce**. ## RelayEvents__c Object Added additional fields: - **Lb_name__c** β†’ The name of the user or service that triggered a Relay message or onboarding action. - **Lb_source__c** β†’ The source system that triggered a Relay message or onboarding experience. ## Sales*f*orce API Version The Sales*f*orce API version for the Relay package has been upgrade to 61. ## Test Coverage Our test code coverage is now at 98%. Well beyond the minimum of 75%.