Transition to the new Huwise experience
The new Huwise experience enhances your existing portal to address your challenges :
accelerate data usage by your business and non-technical users;
maximize the ROI of your portal efforts and data projects;
align with current expectations for user experience and AI.
This guide details the major changes and the steps required to configure and optimize your new environment.
Key Improvements
The new experience introduces structural changes designed to simplify your business processes.
Functional scope | Current experience | New experience |
Types of exposed assets | Datasets only | Datasets, BI reports, pages, applications, data products, APIs… |
Catalog | Dataset list with direct access | Asset list, bookmark (favorites), direct access and/or via enriched product pages (similar asset recommendations, sources, use cases, definitions) |
Search | Keyword-based lexical search (exact matches) | Enhanced search with semantic similarity |
Integrated AI agent & MCP server | Not available | Available |
Customization of interfaces | CSS | No-code |
Business Glossary | Not available | Available in two formats: a centralized page and product pages (with definitions displayed on hover) |
Access Management | Ad hoc, via SSO | Ad hoc, via SSO and access request workflows |
Usage Analytics | API call logs | API call logs and conversion funnel by data asset |
Pages and data visualizations | Not discoverable in the catalog (accessible only via URL or through the navigation menu) | Integrable and discoverable in the catalog (fully packaged assets with metadata, lineage, and analytics) |
Accessibility | Standard | WCAG 2.0 compliant |
Preparing the activation of the new experience on your portal
To support you through these changes, here are 3 resources to:
Explore the new features : discover the features of the new experience, including homepage customization options and data usage monitoring tools.
Preview the new experience on your portal before final activation, you can preview your future portal directly from the back office. This step allows you to validate the visual and functional rendering of your content.
Understand the required actions during activation : some manual steps are necessary to ensure the continuity of your services. Specifically, you will need to : verify the migration of your existing metadata, review the permissions on your new datasets, link your assets to the terms in the glossary if necessary.