Valorx
HomeFusionWave
Wave
Wave
  • Getting Started
    • 🌊What is Valorx Wave
      • Pick The Right Wave
    • 📔Get Started with Valorx Wave
      • Wave Browser Extension Installation & Setup
      • Wave Embedded Installation & Setup
  • Wave Workspace
    • Overview
    • 🏡Home
    • 📃Grids
    • 🟣Wave Floaty
    • Wave Dashboard
  • Wave Experience
    • 📚Type of Grid in Wave
    • 📝Create A New Grid
      • 🌈Manage Grid in Wave Browser Extension
      • 🪄Grid Wizard in Salesforce
  • WAVE DATA MANAGEMENT
    • 📊Managing Grid Data
      • Filter
      • Condition
      • Group
      • Column Group
      • Mass Modifier
    • ✏️Data Control & Customization
    • 🔍Data Interaction
    • 🔢Data Insights & Summary
    • ⌛Managing Records in Wave
  • Surf The Wave
    • 🏄‍♂️Surf The Wave in Salesforce
      • Using Wave Grid in Components and Flows
      • Row Action
      • Known Limitation
      • Wave Embedded Grid Migration
  • Matrix
    • 🔳Matrix Screen
  • 🎨Matrix Designer
  • ▶️Matrix Runtime
  • ⚡Matrix Launcher
  • REPORTS
    • 📈Reports Overview
  • IMPORT
    • 🚀Import Overview
  • SETTINGS
    • 🛠️Settings Screen
  • Release Notes
    • 📢Wave Browser Extension
      • March 25 Release (v40)
      • February 25 Release (v39)
      • January 25 Release (v38)
      • December 24 Release (v37)
      • October 24 Release (v36) - Hotfix
      • September 24 Release (v35) - Hotfix
      • August 24 Release (v34)
      • July 24 Release (v32)
      • June 24 Release (v31) - Hotfix
      • May 24 Release (v30)
      • April 24 Release (v29)
      • Archived Release Notes
        • March 24 Release (v28)
        • Feb 24 Release (v27)
        • Jan 24 Release (v26)
        • Dec 23 Release (v25)
        • Nov 23 Release (v24)
        • Oct 23 Release (v23)
        • Sept 23 Release (v21)
        • Aug 23 Release (v20)
        • Jul 23 Release (v18)
        • Jun 23 Release (v17)
        • May 23 Release (v15)
        • Apr 23 Release (v12)-Hotfix
        • Apr 23 Release (v11)
        • Mar 23 Release (v10)
        • Jan 23 Release (v9)
        • Jan 23 Release (v8)
        • Dec 22 Release (v7)
        • Nov 22 Release (v6)
        • Oct 22 Release (v5)
        • Sep 22 Release (v4)
        • Sep 22 Release (v3)
        • Sep 22 Release (v2)
        • Sep 22 Release (v1)
    • ☁️Wave Embedded
      • March 25 Release (v11)
      • February 25 Release (v10)
      • December 24 Release (v9) - Hotfix
      • November 24 Release (v8)
      • October 24 Release (v7)
      • September 24 Release (v6)
      • August 24 Release (v5)
      • July 24 Release (v4)
      • June 24 Release (v3)
  • HELP & FAQ
    • 💡FAQs
    • ✉️Get Support
Powered by GitBook
On this page
  • 📢 Announcing the October Release
  • ➕ What's New?
  • Save Grid Button
  • ✨ Enhanced UI / UX Design
  • Unsaved Changes Warning
  • Optimized Full-Screen View
  • Lookup Filters Support for L2+ Lookup Fields
  • 🔧 Bug Fixes
  1. Release Notes
  2. Wave Embedded

October 24 Release (v7)

Last updated 5 months ago

📢 Announcing the October Release

We are excited to announce the latest update and enhancement in our newest release. This release introduces new feature, enhancements and bug fixes to improve your experience. Below is an overview of the key update.


➕ What's New?

Save Grid Button

A new feature has been introduced, allowing users to save changes to a grid with the addition of a "Save Grid" button in edit mode. This button is positioned in the top-right corner of the interface. Users can make edits either through the Grid Wizard or while surfing a grid in the Surf the Wave section. In both scenarios, the "Save Grid" button becomes visible only when changes are made, making it easy for users to save their updates in real time. Here's how it works:

  • Grid Wizard Example: When editing a grid using the Grid Wizard, users will see the "Save Grid" button appear in the top-right corner after making changes to the grid structure or configuration. Clicking this button saves the changes immediately.

  • Surf the Wave Example: While surfing a grid in Surf the Wave mode, users can modify the grid details. Once edits are made, the "Save Grid" button will become visible, allowing users to save their adjustments directly from this mode.

In both cases, a confirmation message will appear once the grid has been saved, stating that the changes were successfully applied.

Important Notes:

  • The "Save Grid" button is accessible only for Designer roles.

  • Users can still create personal copies in designated app locations, but for Designers, personal copies will no longer be accessible within the Surf the Wave section.

  • If a Designer edits and attempts to save changes to a global grid while Standard Users have active personal copies of the grid, a confirmation message will prompt the Designer, asking if they wish to proceed with saving. Selecting "Save Grid" will delete all personal copies for Standard Users, and the updated grid will be shared as the new global version.

This feature streamlines the grid editing process, helping users maintain control over grid configurations while managing personal copies more effectively.


✨ Enhanced UI / UX Design

Unsaved Changes Warning

We have enhanced grid functionality to help manage unsaved changes when switching grids:

Unsaved Changes Warning: If a user attempts to switch to another grid after making changes without pressing the Save Grid or Save button, they’ll receive a prompt:

"Are you sure you want to move to another view without saving the pending changes?"

Options:

  • OK: Discards all changes and navigates to the selected grid.

  • Cancel: Keeps the user in the current grid with changes preserved.

This update ensures users don’t accidentally lose work while switching views, offering flexibility and control over unsaved configurations.

Optimized Full-Screen View

We have refactored the implementation of the full-screen feature to enhance user experience by avoiding the use of double grids. This change simplifies the user interface, allowing for a more streamlined display of information.

Key Improvements:

  • Single Grid Display: The new implementation eliminates the need for duplicate grid displays in full-screen mode, providing users with a clearer and more focused view.

  • Improved Performance: By reducing the complexity of the layout, we have enhanced the performance and responsiveness of the full-screen feature.

  • Simplified User Interaction: Users can now navigate and interact with a single grid, minimizing confusion and improving usability.

This enhancement aims to create a more efficient and user-friendly experience when utilizing the full-screen functionality.

Lookup Filters Support for L2+ Lookup Fields

We’re excited to introduce enhanced Lookup Filters support for L2+ (Level 2 and above) Lookup Fields, offering users greater precision in filtering data.

Key Features:

  • Enhanced Filtering Capabilities: Users can now apply Lookup filters at multiple levels, improving the granularity of data selection.

  • Improved User Experience: This feature simplifies the process of finding related records, ensuring users can access the information they need quickly and efficiently.

  • Consistency Across Levels: The support for L2+ Lookup Fields maintains consistency in the filtering process, providing a seamless experience throughout the application.

With this enhancement, users gain advanced filtering options, making data management and analysis more flexible and efficient.


🔧 Bug Fixes

In this release, we have addressed several issues to improve user experience and functionality.

  • Fixed an issue where grouping by a picklist field in the object view would show the API name of the picklist instead of the label name. Now, the grouped result correctly shows the label name.

  • Fixed an issue where standard users were still able to modify calendar filters after the "Allow Edit Filters" option was disabled on the Access Control page. Now, all filter modification capabilities, including those for calendar filters, are correctly restricted when the option is disabled.

  • Fixed an issue where the API name of lookup fields from related objects was displayed instead of the label name. Now, the correct label name is shown for lookup fields, ensuring a more intuitive and user-friendly display.

For more on Lookup Filters, [].

☁️
click here