> For the complete documentation index, see [llms.txt](https://kb.theloops.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kb.theloops.io/releasenotes/release-notes/cx-platform-release-notes.md). # CX Platform: Release notes {% updates format="full" %} {% update date="2026-10-09" %} ## Highlights * **Edit existing topics in Manage Topics** - edit an existing topic directly from the Manage Topics interface without deleting and recreating it. * **Agent detail menu visibility** - Added the ellipsis menu icon to the Intelerad agent detail sidebar. * **Prevent duplicate tickets in Regression Datasets** - Preventing the addition of the same ticket ID to a Regression Dataset multiple times. * **Persist input schema updates** - Fixed an issue where changes to a tool’s JSON input schema in the Advanced Panel were not retained after saving and refreshing. ## New Features ### Edit existing topics in Manage Topics Users can now edit an existing topic directly from the Manage Topics interface without deleting and recreating it. **Customer benefit:** Teams can maintain topic names more efficiently while preserving existing subtopics, scores, and associated ticket data. **What changed** * Added an **Edit Topic** action that follows the familiar Edit Namespace interaction pattern. * Topic names are validated before saving, including checks for empty or duplicate names within the same namespace. * Updates appear immediately in the Topics list without requiring a full page refresh. * Existing subtopics, scores, and associated ticket counts are preserved. * Access remains limited to users with the appropriate topic or namespace edit permissions. ## Bug Fixes ### Agent detail menu visibility Fixed an issue where the ellipsis menu icon was missing from the Intelerad agent detail sidebar. **Customer benefit:** Users can now access the available agent actions from the detail sidebar as expected. ### Prevent duplicate tickets in Regression Datasets Fixed an issue that could add the same ticket ID to a Regression Dataset multiple times. **Customer benefit:** Regression Datasets remain accurate and easier to manage, with each ticket represented only once. **What changed** * Prevented duplicate additions of the same ticket ID to a Regression Dataset. * Preserved existing dataset contents while preventing repeated entries. ### Persist input schema updates Fixed an issue where changes made to a tool’s JSON input schema in the Advanced Panel were not retained after saving and refreshing. **Customer benefit:** Tool designers can update input schemas with confidence, and test executions use the saved schema instead of reverting to an earlier version. **What changed** * Ensured JSON schema changes persist after saving a draft. * Retained updates after the page is refreshed. * Prevented schema changes from being lost during subsequent test execution. * Verified the fix across Concept, Preprod, and production environments. {% endupdate %} {% update date="2026-10-02" %} ## Highlights * **Reveal and update OAuth credentials on existing IFS connectors -** Admins can view OAuth Client IDs and update OAuth credentials directly on existing IFS connector variants without recreating them. * **Bug Fixes** - Ask Anything now remembers the selected search source filter across consecutive queries, Fixed an issue where opening an existing Heretto integration configuration displayed a blank page. ## New Features ### Reveal and update OAuth credentials on existing IFS connectors Admins can now view OAuth Client IDs and update OAuth credentials directly on existing IFS connector variants without recreating them. **Customer benefit:** Teams can quickly look up Client IDs for IAM troubleshooting and update rotated credentials without rewiring dependent workflows. **What changed** * Added a visibility toggle next to the **OAuth Client ID** field on existing connectors so users can view or copy the value. * The **OAuth Client ID** and **OAuth Client Secret** fields are now editable on existing connectors. * The **OAuth Client Secret** remains write-only and hidden for security. * Verified support across the IFS connector variants listed in the implementation comments: **IFSCloud24R2**, **IFSCloud25R1**, **IFSCloud25R2**, **IFSCloud26R1**, **IFSCloud26R2**, **IFSCloud**, and **IFSAPPS10**.
## Bug Fixes ### Search filter selection persistence in Ask Anything Ask Anything now remembers the selected search source filter across consecutive queries. **Customer benefit:** Users can run multiple searches within their preferred source, such as Knowledge Articles or Past Cases, without selecting the filter again each time. **What changed** * When users change the source filter, the selection remains active for subsequent searches during the session. * The selected filter remains in place until the user explicitly chooses another option. ### Heretto integration configuration editing Fixed an issue where opening an existing Heretto integration configuration displayed a blank page. **Customer benefit:** Administrators can now reliably view and update Heretto integration settings without interruptions. **What changed** * Resolved the rendering issue that occurred when selecting the **Edit** icon for an existing Heretto integration. * The configuration details page now loads correctly with all fields available. * The **Update** action is fully functional. {% endupdate %} {% update date="2026-09-25" %} ## Highlights * BambooHR connector configuration is now available directly in the UI through a dedicated Configuration tab. ## New Features ### BambooHR Configuration tab for catalog attributes BambooHR integrations now include a dedicated **Configuration** tab, following the same pattern used for Salesforce integrations. **Customer benefit:** admins can manage BambooHR tenant-specific settings directly in the UI without editing JSON manually. **What changed** * BambooHR settings now use the tab structure: Basic, Authentication, Configuration, Schema, Jobs, and Test. * The Basic tab continues to show the integration name and capabilities. * The Configuration tab displays BambooHR catalog attributes with labels and descriptions from the integration catalog. * Admins can configure supported fields such as approved status lists, vacation threshold settings, deleted status lists, and ignored time-off types. * Enumeration and repeated string fields are supported, including multiple values for fields such as ignored time-off types. * Saving configuration changes preserves existing integration attributes and updates only the edited catalog fields.
{% endupdate %} {% update date="2026-09-08" %} ## Highlights * **Better Copilot usability:** the Ask experience is now easier to discover and use directly within the widget. * **Broader content-management coverage:** publicly accessible Fluid Topics content, SkillJar content, and IFS Cloud KB article attachments are now better supported. * **Improved alert clarity:** sentiment notifications now provide more actionable context behind score changes. ## New Features #### Sentiment alerts now include deeper drilldown context Sentiment notifications have been enhanced to provide clearer context about why a score has decreased, including the underlying drivers that contributed to the change. **Customer benefit:** teams can understand negative sentiment shifts faster and take action sooner without needing to manually investigate each case in detail. **What changed** * Alerts can now surface more detailed reasons behind a score drop. * This may include contributing sentiment tags, phrases, or tone indicators that explain the decline. * Users get more immediate context directly from the notification experience. ### Ask is now more prominent in the Copilot widget The Ask experience has been moved to a more visible position within the Copilot widget so users can enter questions more naturally while staying in context. **Customer benefit:** this improves discoverability and encourages faster adoption by making it easier for agents to ask questions without leaving their current workflow. **What changed** * The Ask input is displayed directly below the widget section for easier access. * The text box remains visible while users browse widget content such as intents, resolutions, insights, and comments. * Selecting the Ask button places focus into the input so users can begin typing immediately.
### Content-management integrations expanded for Fluid Topics, SkillJar, and KB attachments (CX) Release 0.8 includes additional content-management capabilities across integrations and core services, covering publicly accessible Fluid Topics content, SkillJar connector support, and attachment retrieval for IFS Cloud KB articles. **Customer benefit:** teams can bring more external and knowledge-base content into Loops workflows with less manual handling and better connector coverage. **What changed** * Added support for fetching publicly accessible Fluid Topics content that does not require users to sign in or provide additional authorization. * Implemented SkillJar as a ContentManagement integration, including API configuration, authentication, content fetching, mapping, error handling, and test connection support. * Added support for pulling Knowledge attachments for IFS Cloud KB articles. {% endupdate %} {% update date="2026-08-28" %} ## Highlights * **Better transparency** in Copilot experiences with broader AI disclaimer coverage * **Faster troubleshooting** with direct execution lookup support * **Exploration of lightweight feedback** options in Microsoft Teams conversations ## New Features ### Copilot **What changed:** Expanded the AI disclaimer so it is shown consistently across all Copilot application tabs. **Benefit:** Users get clearer guidance about AI-generated content wherever they interact with Copilot, improving transparency and consistency. ### Executions **What changed:** Added search support to help users find executions directly by execution identifier or ticket handle, instead of manually paging through execution history. **Benefit:** Support teams and administrators can investigate specific runs much faster, especially in high-volume environments. ### Workflow authoring **What changed:** Added the ability to insert tasks between existing workflow steps, including before the first task, without rebuilding the rest of the sequence. **Benefit:** Workflow designers can make changes more easily, reduce rework, and refine automation logic without disrupting the full flo ### Testing experience **What changed:** Improved the launch test user experience to make testing flows easier to start and use. **Benefit:** Users can move through testing more smoothly with a clearer and more efficient experience. ### API Task testing **What changed:** Fixed an issue where resizing the browser window or opening developer tools could reset values entered during API Task testing. **Benefit:** Test context is preserved more reliably, helping users avoid rework and making API task validation less frustrating. ### Microsoft Teams integration **What changed:** Explored options for adding like/dislike feedback buttons to Teams Adaptive Cards, including user experience, platform support, and backend event handling. **Benefit:** This investigation lays the groundwork for simpler in-context feedback collection within Teams conversations. ## Detailed Notes ### Testing and troubleshooting enhancements * **Launch test UX:** The testing flow has been improved to reduce friction when starting and running tests. * **API Task resize fix:** Entered values are no longer unexpectedly lost during common resize events such as opening DevTools. * **Execution search:** Users can reach a specific execution more directly using known identifiers. ### User trust and feedback * **AI disclaimer coverage:** Users now see the AI disclaimer consistently across Copilot tabs, helping set expectations wherever AI content appears. * **Teams feedback exploration:** Work has been done to evaluate how quick thumbs up/down feedback could be captured in Teams-based interactions. {% endupdate %} {% update date="2026-06-08" %} ## Highlights We have introduced significant improvements to workspace management by adding UAT and Production workspace types. This enhancement provides greater flexibility for customers to: * Use UAT workspaces for testing, validation, monitoring, and connecting sandbox/UAT integrations. * Use Production workspaces for production integrations and live data. This approach helps keep data from different environments isolated, making it easier to manage, track, and monitor. For existing customers, all current workspaces will be migrated as Production workspaces. A corresponding UAT workspace will also be created. ### Known Behavior The UAT environment **must** be configured with UAT/Sandbox integrations. If no UAT environment is set up, it will appear empty. ## New features ### Enhanced Breadcrumb Experience The breadcrumb navigation has been enhanced to display the currently active workspace along with its workspace type (UAT or Production) on every page after login. #### Change Workspace Using Breadcrumbs You can now switch workspaces directly from the breadcrumb. {% stepper %} {% step %} **Click the Workspace Name** Click the workspace name displayed in the breadcrumb.
{% endstep %} {% step %} **Select a Workspace** A modal window will open showing all available workspaces and their corresponding workspace types, click the Production or UAT tag for the workspace you want to access.
{% endstep %} {% step %} **After selection, a loader will be displayed while the application:** * Switches to the selected workspace * Refreshes workspace metadata * Reloads relevant data and API responses {% endstep %} {% step %} **Once the process is complete, the breadcrumb will display the newly selected workspace and its type.**
{% endstep %} {% endstepper %} ### Switch between Production and UAT workspace through breadcrumbs You can quickly switch between the UAT and Production versions of the same workspace directly from the breadcrumb. {% stepper %} {% step %} **Click the Workspace Type Badge** Click the UAT or Production badge displayed in the breadcrumb.
{% endstep %} {% step %} **A confirmation pop-up will display** Click Yes to switch to other type of workspace or No to stay on the same workspace.
{% hint style="info" %} Note: Switching workspace types refreshes workspace metadata and related information in the background. A loader will be displayed until the process is completed. {% endhint %} {% endstep %} {% endstepper %} ### Improved Change Workspace Page The Change Workspace page has been redesigned to provide a better user experience. The page now displays: * All available workspaces * UAT and Production workspace types * Edit functionality * Delete functionality * Set Default Workspace option * Add Workspace option The currently active workspace is highlighted for easy identification.
#### Add or Delete Workspace * To add a new workspace or delete an existing workspace, please contact the Loops Administrator. #### Edit Workspace * Workspace names are unique and cannot be modified after creation. * Only the workspace description can be updated.
#### Set Default Workspace The default workspace is highlighted in the workspace list. To change the default workspace: 1. Locate the desired workspace. 2. Click the Star icon next to that workspace. The selected workspace will become your default workspace.
{% hint style="info" %} Note: After login, the system always activates the Production version of the default workspace. {% endhint %} ### Additional Breadcrumb Enhancements * The breadcrumb now provides quick navigation to the home page of the currently active section. * Simply click the active page title within the breadcrumb to return to its home page.
{% endupdate %} {% endupdates %}