2025 Alation Frontend Releases

Alation Cloud Service Applies to Alation Cloud Service instances of Alation

Note

These release notes cover updates to the Frontend service in the New User Experience, available on Alation Cloud Service only. Frontend updates are released every two weeks, with additional patch releases as needed.

Alation Frontend Release July 01, 2025

Frontend Version: 1.2

Build: 10.383.2-patch.0-23760

Previous Version: 10.346.0

New Features

  • AL-196796 / AL-195677: Enhanced the stale table profile warning message to improve clarity. The new message now guides users to verify if sampling is turned on and if the Skip Views option is disabled before rerunning sampling. This helps avoid confusion when sampling does not update due to schema-level settings.

  • AL-196452: Added logic to filter out unsupported formats based on the data source type, ensuring users only interact with compatible formats.

  • AL-196451: Enhanced the metric selection functionality by allowing the same metric to be added multiple times.

  • AL-196181: Updated the Alation UI URL routing to direct API calls to the API layer, enabling seamless internal communication with the SDN-SVC.

  • AL-195238: Changed export triggering mechanism from GET to POST in the Table View, leveraging newer web server capabilities to improve reliability and consistency of export operations.

  • AL-194334: Introduced server-side pagination for the Under Review documents table to significantly improve performance when handling large collections (200+ suggestions). Also enhanced search functionality with server-side filtering to retain consistent cross-page search behavior.

  • AL-193145: Introduced server-side pagination to the IP Access Management Dashboard, improving performance and scalability.

  • AL-195235: Updated the export infrastructure to enhance the reliability and accuracy of Table View exports. These modifications address race conditions and reduce unnecessary requests, specifically resolving issues within the New User Experience. Exporting search results from the Table View is now more reliable and accurate.

  • AL-177936: A new Query History tab is now available under the Queries section on Schema, Table, and Column catalog pages. It displays detailed query execution history and allows exporting data as a CSV via email.

Bug Fixes

  • AL-197029: Fixed an issue where navigating between hubs retained the dirty state of column view changes from the previous page.

  • AL-195229: Fixed an issue where the inbox counter did not update correctly after assigning the current user to a conversation.

  • AL-195080: Fixed an issue preventing Viewer and Explorer roles from accessing the Auto Title button in the Columns table on the Table object page.

  • AL-194591: Fixed an issue where the BI field category did not display correct values and could not be sorted properly.

  • AL-194025: Fixed an issue where the UI would snooze when navigating from the Catalog page in the New User Experience to the Settings page in the Classic User Experience for a data source. The transition now behaves consistently when the redirect is enabled.

  • AL-192608: Fixed an issue in search results where selections were lost when navigating between paginated results. Users can now maintain selections across pages for bulk operations, with selections cleared only when applying new filters or search terms.

  • AL-191911: Fixed an issue in the Alation Chrome Extension to ensure Snowflake Dynamic Tables are now correctly detected and displayed from the catalog.

  • AL-189278: Fixed an issue where HTML entities like & were incorrectly rendered as raw text in the BI Source title filter. Integrated, sanitized unescaped content, and updated rendering logic to display the correct character &.

  • AL-182764: Fixed an issue in the Policy Center where user and admin view states for grids were not being persisted across sessions. These view states are now saved and restored correctly.

Alation Frontend Release June 18, 2025

Frontend Version: 1.2

Build: 10.346.0-patch.0-23443

Previous Version: 10.326.4

New Features

  • AL-194334: Resolved a workflows issue affecting the Under Review documents table where collections with large numbers of document suggestions (200+) experienced extremely slow load times. The fix implements server-side pagination, reducing load times and ensuring the interface remains responsive regardless of collection size. As part of the performance optimization, we’ve updated the search functionality to use server-side filtering to maintain the same cross-page search behavior users expect.

  • AL-193788: To prevent indefinite polling when fetching large lineage graphs, the lineage UI will make a maximum of 5 API calls or stop after 1 minute whichever occurs first. In most cases, this limit won’t be reached, as the API is expected to indicate that loading has stopped, triggering a switch to the exploratory view. This update ensures more robust handling of unusually large or unresponsive graph loads.

  • AL-191809: Before this update, while using the Run Query feature, users have to navigate to the Run History details page to see the corresponding SQL query. Now, we have added a SQL Statement tab alongside the Results tab. This shows the corresponding SQL statement for each run history entry.

Bug Fixes

  • AL-195034: When changing the column visibility settings in Document Hubs, the changes only apply to the current document hub. The Documents table has its settings per object page, and Folders tables have one setting per hub.

  • AL-194431: When the feature flag Document Hubs 5: Document Total Count is disabled, we are now correctly skipping counting of documents and have also fixed pagination on Documents tables.

  • AL-193713: We’ve fixed an issue where the Shared connections across tabs radio button in Compose settings would not become selected when clicking on it, even though a success message appeared.

  • AL-192608: Users can now maintain item selections when navigating between pages in search results, enabling efficient bulk operations across large datasets. Users can select individual items or entire pages, and the selections will persist as they browse through paginated results. Selections are cleared when applying new filters or changing search terms to ensure relevant results.

  • AL-189216: Changed how we display buttons inside Rich Text Field Editor. Instead of showing few buttons per category and allowing users to show more, we are displaying all of them by default, separated by vertical bar.

  • AL-188144: Disabled possibility of clicking on auto-title button next to RDBMS object titles for Viewer and Explorer roles.

  • AL-187870: The timestamp for trust flags (endorsements, important information, and deprecations) will now include the time in addition to the date. This matches the behavior in Classic.

  • AL-186746: User is now able to access Query Results from search with all data correctly loaded.

Alation Frontend Release June 04, 2025

Frontend Version: 1.2

Build: 10.326.4-22791

Previous Build: 10.311.1

Bug Fixes

  • AL-194244: Fixed a display issue where the columns might appear or disappear from the search results table. This was caused by the UI referencing incorrect data when determining which filters should be shown.

  • AL-193994: Previously, users couldn’t select 13px (Alation’s default font size) from the font size dropdown in the Rich Text editor. This update adds 13px as a selectable option, making it easier to return to the default size when adjusting text formatting.

  • AL-193870: Fixed the null pointer error when loading filtered search that manifested itself as the error Uncaught TypeError: Cannot use ‘in’ operator to search for ‘parent_group_id’ in undefined in the user interface. This occurred when one filter already returned no results and an additional filter was applied on top.

  • AL-193858: Technical fixes: use both content_long_html and content_html to copy and render SQL code in modal dialogs; allow persisting columns sizes; add support for last_executed_by as a string.

  • AL-193652: Clicking the logo in the top left corner now navigates to the user’s preferred homepage, rather than the default homepage.

  • AL-193293: Fixed an issue where documents added to a subfolder were not visible in the parent (top-level) folder. Now, when a user adds a document to a folder that is itself a subfolder, the document correctly appears in the parent folder’s view.

  • AL-192669: Users can now add tags to documents, folders, data policies, policies, policy groups, files, and file systems directly from the Add dialog in the Tag object table. This update brings functional parity across the Classic and New User Experiences, ensuring tags can be added to the same object types consistently.

  • AL-192608: When using the Stewardship Workbench, users can now maintain item selections when navigating between pages in search results, enabling efficient bulk operations across large datasets. Users can select individual items or entire pages, and the selections will persist as they browse through paginated results. Selections are cleared when applying new filters or changing search terms to ensure relevant results.

  • AL-192330: On folder detail pages, the subfolder table will only render when there are one or more subfolders present. This restores the original functionality, which had recently been changed to always show the table even when empty.

  • AL-191899: In the full search table view, users can now select the same columns in the New User Experience that were previously available in Classic, resolving an issue where most columns were not selectable.

  • AL-187934: Improved error handling to prevent unnecessary backend requests. We’ve implemented a fix to stop the UI from sending requests to the backend when specific errors occur (for example, 499, 500, 502, 504). This enhancement improves system stability and prevents unnecessary pod restarts.

  • AL-183900: Shared titles are now visible in the New User Experience when defined by a catalog set, addressing an issue where shared titles were previously missing. When multiple catalog sets define shared titles for the same object, users see a See all button. On hover, all shared titles are displayed along with their respective catalog set names, providing clarity without cluttering the user interface.

  • The release also includes internal updates aimed at maintaining the stability and quality of the application.