Overview
The 25.3 release introduces key enhancements focused on orchestration, supported by advanced analytics and visualization capabilities. It brings the Xponent Email Node, a native node for email communication use cases, designed to simplify implementation and accelerate value realization. The Date Constraint support for Segmentation makes segments dynamic with time-based conditions. This helps build more granular segments and better targeting.
Xponent Email Node
Xponent Email Node is a native node for email communication. It provides direct access to templates created in XCC (Xponent Communication Control) and enables triggering communications from within graphs using a single node. When a template is selected, dynamic variables linked to the template can be mapped directly from the graph. This makes it convenient for the configurer and eliminates the need to identify and assign dynamic fields manually.
Xponent Email Node displays a list of templates marked as “Active” in XCC. Email templates are created and tested within XCC, and once marked as active, they can be accessed directly through the Email Node.
Xponent Email Node is available to all users. To enable access, please contact your Xponent Admin or Customer Success team to link your Xponent Communication Control account with Xponent Hub. This is a one-time setup process.
Continuous Improvements
JDA Sankey Pagination
The Sankey Pagination feature enhances the visualization experience for complex Sankey diagrams and now supports pagination, displaying five journey steps at a time. Users can navigate through steps in increments of either five or one. Users can move forward or backward through these step ranges, jump directly to a specific range, or use quick navigation controls to jump to the first step, last step, one step forward/backward, or five steps forward/backward without entering a specific number.
When a user types ‘16’ in the input field, the system displays all ranges that include step 16. For Example, Options may include ‘12–16’ or ‘16–20,’ and the user can choose the desired range, allowing precise navigation without scrolling through the entire flow. This approach improves readability and allows users to view journey steps that were previously hidden. It helps uncover insights that were not visible before, making the analysis more comprehensive.
Date Constraint support for Segmentation
Segmentation now supports Date Constraints, enabling dynamic segments through time-based conditions. These constraints are optional and can be applied to individual criteria. Without them, segments may remain static for certain loosely defined conditions, meaning customers can stay in a segment indefinitely, a behavior that can be useful for deep-dive analysis.
With time constraints applied, segments become dynamic and update automatically as time passes. You can set relative ranges like “last 24 hours” or “last 7 days,” as well as specific dates such as “October 15, 2025.” For example, you can target customers who completed a journey in the last 24 hours and used an offline channel. Delivering benefits such as improved targeting with time-sensitive segments and reduced manual updates for better campaign accuracy.
Bug Fixes
KIT-6688 - Fixed an issue where the analytics page failed to load after copying graph templates containing start journey steps into another project. The problem occurred because the start steps were created without associated journey maps, which broke the global filter population. With this fix, analytics widgets now load correctly, and journey filters exclude steps without maps, ensuring a smooth user experience.
KIT-15573 - Running a visual test on an API listener and then deploying the same graph in the same environment caused the graph endpoint to become unavailable when the test expired. The expiration triggered a halt-graph call that removed the listener, resulting in temporary downtime until redeployment. With this fix, expiring visual tests no longer affect deployed graphs, ensuring continuous availability.
KIT-15696 - Graphs crashed after importing or updating a managed graph. The problem occurred when updates were published to a managed graph and then applied to another graph that had previously imported it. This issue was also occasionally seen during the initial import. With this fix, managed graph imports and updates now work reliably without causing failures.
KIT-15985 - Base nodes appeared above the modal screen when adding or replacing a node in the graph editor. Now, nodes remain behind the modal as expected, ensuring a clean and consistent user interface.
KIT-15036 - Identifier Mapping ComboBox and the Dropdown option lists remained open when the user scrolled the page. This behavior was observed in the Identifier Mapping combobox, Fragments combobox, and environment-related dropdowns. With this fix, all option lists now collapse correctly during page scroll, ensuring a consistent and intuitive user experience.
KIT-15367 - Journey Step dropdown in the Global Filter collapsed when deselecting any selected option. This behavior also affected Segment, Channels, and Journeys filters. With this fix, dropdowns remain open during deselection, ensuring a smoother filtering experience.
KIT-15762 - Custom icons in managed graph nodes were misaligned and hidden on hover. The CSS and rendering logic were updated to position icons on the left and ensure they remain visible when hovering.
KIT-15840 - The Right navigation arrow on the Graphs library page did not function across multiple hubs. The underlying event binding and scroll logic were corrected to ensure smooth horizontal navigation, while maintaining consistent behavior for both left and right arrows.
KIT-16050 - Broken links for Journey Templates and Graph Templates documentation that were leading to 404 errors. Updated the URLs to point to the correct resources in Document360, ensuring users can access template guides without navigation issues.
KIT-15419 - Failed S3 upload requests exposed AWS details in front-end error messages. Updated error handling to display generic messages to users while logging detailed errors in the console, preventing sensitive information from being revealed on the Hub interface.