Overview
The 26.1 release introduces new native capabilities that simplify communication, automation, and analytics within Xponent. This release adds the Xponent Messaging Node for built‑in SMS/MMS delivery and the Agent Node (MVP) for agent‑driven decision support in graphs. It also introduces the Reusable Journey Logic Tool (API), which lets agents trigger journey logic designed in Graphs. In addition, usability improvements such as CSA Intermittent Saving and Journey Insights Outliers Exclusion deliver more reliable workflows and clearer insights.
Xponent Messaging Node
The Xponent Messaging Node adds native messaging capabilities to Xponent, allowing configurers to browse, search, preview, and select Active SMS and MMS templates maintained in Xponent Communications Control (XCC) within the graph. Messaging node supports mapping dynamic values from the project schema into the template, and is used to send messages during graph execution without custom integrations or switching between systems. Simplify multi‑channel communication orchestration today while laying the foundation for future RCS support.
Agent Node
The Agent Node introduces a productized way to use AI agents within Xponent workflows, allowing intelligent, goal‑driven agents to be executed as part of graph orchestration. Configurers can create and manage agents at the organization level, define their goals, knowledge sources, and available tools, and then use those agents within graphs to automate decisions or actions. This MVP enables teams to move beyond manual or repetitive logic by incorporating agent‑based decision support directly into journeys, laying the foundation for more advanced agent‑driven automation in future releases.
Reusable Journey Logic Tool (API)
The Reusable Journey Logic Tool (API) enables Xponent graphs with API listeners to be published and reused as callable tools for AI agents and other integrations. Configurers can expose selected graphs by providing clear descriptions, required inputs, and expected outputs, making complex journey logic discoverable and usable beyond a single workflow. Published graphs can be selected during agent creation. Key details such as the graph’s purpose, required inputs, deployment status, and supported environments are clearly visible. This helps users make informed decisions when assembling agent capabilities. It also lays the foundation for extending reusable journey logic to additional automation and integration use cases in future releases.
Configurers can also hide a published graph from Agents, removing it from the tool selection list for new Agent configurations while allowing existing Agents already using the graph to continue running without impact.
Continuous Improvements
CSA - Intermittent Saving
Current‑State Analytics (CSA) now supports manual mid‑step saving, allowing users to explicitly save progress during complex mappings without completing a step. A persistent save indicator shows whether changes are unsaved or successfully saved, including a timestamp, and surfaces an error if saving fails. The final Event Mapping step now uses a Submit action to clearly indicate completion, while a cancel confirmation on every step, including file upload, warns users when they will lose progress. These enhancements make CSA imports more reliable for large or multi‑session jobs while preserving the existing validation flow.
JDA - Journey Insights Outliers Exclusion
Journey Discovery Analytics now allows users to filter out low‑volume outlier data specifically within the Journey Insights cards, so insights focus on statistically meaningful, high‑impact behavior. A dedicated toggle in the Journey Insights section controls whether insight cards include all data or only steps that meet a minimum population threshold based on active profiles over the last 30 days. This rule is applied consistently across Completion Rate, Stall Rate, Repeat Rate, and Average Step Time cards. When the filter removes all qualifying data for a card or time period. The UI clearly indicates that only outlier data remains for that period, which explains why the card is empty and helps users trust the insights shown.
Email Template Preview
The Xponent Email Node now includes an enhanced template preview experience, allowing users to preview email content before and after selecting a template directly within the workflow. This improvement helps validate email layout and content without switching to XCC, making template selection and verification faster and more intuitive.
Bug Fixes
We have resolved the following bugs to ensure these functionalities now work as expected:
BUG-714310 - Dropdown menus sometimes opened upward due to limited space but kept styling intended for downward-opening menus, causing a visual mismatch. This affected several screens that frequently use dropdowns. The issue has been resolved, and dropdowns now display consistent styling regardless of opening direction.
BUG-714314 - When a REST adapter template used a status code as a public variable and that variable was later removed, the status code could appear as undefined, leading to inconsistent template behavior. The issue has been resolved, and REST adapters now correctly handle status code variables, ensuring expected behavior.
BUG-714365 - Restoring a version while graphs were deployed in the current version could cause unclear deployment visibility and inconsistent behavior, leading to user confusion when switching between versions. This issue has been resolved by improving version restore behavior and ensuring deployed graphs are clearly and consistently displayed when switching versions.
BUG-725266 - Stopping a visual test could result in incorrect status messages or unnecessary error notifications. In some cases, tests appeared stuck or displayed inaccurate stopping states. This issue has been resolved, and visual tests now stop reliably with accurate status updates, ensuring a smoother testing experience.
BUG-748374 - The Hub showed steadily increasing memory usage over time, even under normal operating conditions, which could lead to resource pressure during long-running usage. The issue has been resolved, and the Hub now maintains stable memory usage during extended operation.
BUG-923220 - Some configuration values required by the Hub were not loaded consistently, affecting feature behavior and refresh intervals. This resulted in features relying on incorrect or missing defaults. The issue has been resolved. Features now correctly use configured or default values, dashboards load accurate data, refresh intervals behave as expected, and feature-flagged functionality works reliably across the Hub.
BUG-982679 - Minor text and formatting inconsistencies appeared on the SSO enablement screen, including spelling, capitalization, punctuation, and terminology. These have been corrected to improve clarity, consistency, and overall readability while enabling SSO.
BUG-982943 - Sankey diagrams did not render correctly when multiple Journey steps occurred simultaneously, causing steps to appear out of order, overlap, or display incorrectly. In some cases, this caused the Analytics page to crash, especially when using options such as “View more.” This issue has been resolved. Sankey diagrams now render consistently, with all steps in the correct order, all links properly connected, and the page remaining stable during visualization and interaction.
BUG-989909 - In some navigation scenarios, the Graph Explainer Assistant attempted to send requests without a valid context after users moved between the graph and library views. This unexpected behavior caused unnecessary requests and inconsistent behavior. The assistant now maintains the correct context during navigation and operates reliably across both views.