vFlow 2.0
New Features
Subcomponent Support for Fieldset
Overview:
The Fieldset component in vFlow now supports subcomponent elements, expanding the ability to design more modular and structured UI layouts.
How It Works:
-
Users can now add a subcomponent element within a Fieldset.
-
List and Table components can be mapped inside these subcomponents to capture and view structured data.
-
Style and Events sections are now available at the subcomponent level for advanced customization.
-
Recursive handling has been implemented to prevent infinite loops when nesting subcomponents or subpages at the Configurator level.
For more information follow academy link- Click here
Enhancements & Improvements
Debugger Enhancements
What’s Improved:
The debugger has been enhanced to display:
-
Subcomponent configurations
-
Subpage configurations mapped to Tab/Stepper
-
Header and Footer configurations used in Pages or Components
User Impact:
Gives developers deeper visibility and control while debugging complex UIs involving nested components and configurations.
Business Rule Access from Task Level
What’s Improved:
You can now view associated Business Rules (BRs) from within a Task inventory in the Configurator. A Create button has also been added for directly creating a new BR from the task panel.
User Impact:
Reduces navigation steps and improves efficiency when setting up or modifying BRs linked to a specific task.
Default Loader for Server-Side Pagination
What’s Improved:
A default loader has been introduced for Table and List components using server-side pagination. This loader is displayed while API data is being fetched.
User Impact:
Enhances the user experience by giving visual feedback during data loading delays at runtime, especially in low-bandwidth conditions.
Important Changes & Notices
Label Change:
The checkbox label in the Footer for buttons has been renamed from “Validation Required” to “Check mandatory fields with validations” for clarity.
Task Validation Rules:
Field validations have been added for tasks like Visible, Invisible, Enable, and Disable.
Action Required: If any of these tasks were previously configured without required fields, you may face issues while saving and need to reconfigure them. If all fields are already filled, no action is needed.