What’s New in Vahana Cloud?
Vahana’s New Unified Interface
Discover our new unified view! We’ve redesigned application tiles, bringing all your tools together.
- Now access and manage every app type from one streamlined interface.
- Enhanced Left Panel: Improved visibility across all modules.
- Streamlined Access: Easier navigation for Academy, Community, and Support
Click here for more details!
Introduction of Vahana Development Lifecycle
VDLC outlines the entire project journey, from Design to Operation/Maintenance. We have consolidated tools across the stages of the SDLC to provide better visibility for users. Additionally, the Administration section has been consolidated to include options for managing accounts and IAM.
Click here for more details!
New Application Creation Journey
Application creation is now a multistep process as outlined below:
-
Select Application Type: Choose the type of application you’d like to create from Native Mobile & PWA, Web, or Middleware.
-
Enter Basic Details: Input key information such as the app icon, name, tags, and description.
-
Connectors: Connect your application to Data Modeler, Themes, and Middleware.
Note
-
Only Native Mobile & PWA applications have access to all connectors. Web applications do not include Data Modeler and Themes, while Middleware applications have no connectors.
-
Users can now create separate vFlow applications, decoupled from Middleware. This allows users to connect vFlow with Middleware in a manner similar to Designer 2.0, improving reusability.
Click here for more details!
Workspace Transfer and Duplicate Applications
- Workspace Transfer: Seamlessly transfer workspaces between accounts to consolidate resources.
- Duplicate Application: Users can now copy Designer 2.0, vFlow 2.0, and Middleware applications across accounts and workspaces. This new feature provides flexibility by allowing developers to duplicate solutions, giving them a solid base to start from and accelerating their development process.
Known Bug:
- Users must subscribe to Vahana Hub services to enable vConnect APIs in the duplicated application.
Click here for more details!
Revamp of Application Setting Page
The enhanced Application Settings page allows you to easily connect your Data Modeler, configure middleware connections, and view essential application details—all in one place.
Known Bug:
- The Edit option is not available on the App Settings page.
Deploy Duration
The deployment duration can be viewed on the Deploy History page, where all deployment tiles are displayed. Two new parameters are introduced on each tile:
- Processing Time: The time taken to prepare for deployment, including communication with other modules and related processes.
- Deploy Time: The time taken to apply the deployment changes.
Loading Strategy
We’ve introduced new loading strategies to optimize app performance based on size and complexity. These strategies allow for more efficient configuration loading, reducing load times and enhancing user experience.
- Eager Loading: Preloads the entire app configuration before launch. Ideal for small apps requiring immediate access to all components.
- Lazy Loading: Loads essential configurations initially, with additional configurations loaded as needed. Best for larger apps to reduce initial load times.
- Only Embedded Configuration Loading: Embeds the entire configuration during the build process, eliminating runtime API calls.
- Embedded Configuration with Deployment Check: Embeds the initial configuration, fetching only changes (delta) after deployment for faster updates.
Export Configuration of Designer Application
To export the configuration, the user must change the VRT type to “Export.” Once changed, the “Deploy” button on the deploy tab in the frontend will switch to an “Export” button. By clicking it, the configuration file will be downloaded.
Minimum iOS and SDK version
A new functionality has been implemented in the Download Module of Designer 2.0, allowing users to control the application’s minimum running version of iOS on specific devices.
- Android: The default minimum version is set to API 28, with the option for users to change it up to API 32.
- iOS: The default minimum version is set to iOS 12, with the option for users to change it up to iOS 18.
Enhanced the Middleware Portal
-
Removed the left panel and application listing.
-
Removed the following modules from the dashboard page: vFlow, Downloads, vFlow New, vLibrary, Master Data Management, Consent Manager, Sync Engine Config, and Manage Your Profile.
-
Removed “Account” and “Organization” from the profile in the header.
-
Removed the option to switch workspaces from the middleware dashboard page.
-
Older apps will still retain the vFlow and Downloads modules.
Introducing vFLow Application Management
Now you can see same interaction vFlow as Designer 2.0 as mentioned below:
- Similar to Designer 2.0, the left panel now includes: Dashboard, App Settings, Download, Deploy, Security, and Multilingual modules.
- The Multilingual module in vFlow now supports configuring RTL (Right-to-Left) languages.
- Users can create Feature Branches, Integration Branches, and Releases via the Configuration Manager (formerly Release Manager), improving configuration management.
- Security settings for the Frontend App of vFlow can now be configured.
- The download settings page has been redesigned. Users can now create builds from this module, similar to Designer 2.0.
Other Features
- Ensure consistency in the name, icon, and description entered on the settings page of the Download Module when sharing web applications on social media platforms.
What’s New in vDesigner 2.0?
Custom JavaScript Function Integration in vDesigner 2.0
We’re excited to introduce custom JavaScript functions under the L1 menu. This feature allows developers to write JavaScript for logic such as data manipulation, concatenation, and more.
Key Features:
- Write Custom Logic: Create JavaScript for specific use cases.
- Invoke Function Task: Use parameters directly within the app workflow.
Important Notes:
- Name Matching: Function and parameter names must match exactly.
- Reconfigure Task: After updates, reconfigure the Invoke Function task.
- Known Bug: Code formatting may distort when copied; review after pasting.
Click here for more details!
Fig: This figure represents the Custom Java Script Functions under l1 menu
Correction in Displaying References
We have addressed a technical debt related to the display of references. With this release, references for Task Groups, APIs, Business Rules (BR), Assets, and elements are now displayed in the correct format, enhancing overall usability.
Known Bug:
- Reference Name Updates:
When a developer changes the reference name of a page or element, the changes do not appear in the references of Business Rules, APIs, Task Groups, or the Asset Manager upon reopening. This problem arises when developers reopen the references.
Smart Selector Enhancement
In vDesigner2.0, we have optimized the performance of the Smart-Selector by addressing the lag issue caused by frequent API calls. The implementation of a debounce mechanism will significantly improve user experience by reducing unnecessary data fetching and enhancing system responsiveness.
Key Feature:
- Users can now select filter types directly in the Smart-Selector, with tags for Entities, Elements, Enums, and Functions, enabling precise data selection.
- A loader has been added to the Smart-Selector to indicate data loading progress, improving the user experience during slower API responses.
Fig: This figure represents the entities UI paths during the selection in the smart selector.
Prefix Input Field in vDesigner 2.0
The new Prefix Input Field element allows users to provide dynamic data for both the prefix and the input field, with the entered data storable in an object for use across the app. This enhances flexibility for input forms requiring prefixed values like gender, codes, or currency symbols.
Note:
Image support for prefix data is not currently available.
Fig: This figure represents Prefix Input Field Element
Bug fixes
- Fixed an issue where long task group names disrupted the UI in data column indicators.
- Resolved a JSON list rendering issue under list element.
- Debugger now opens correctly when the icon is clicked in the web build of the regression app.
- Added the Reload field to the Datepicker task as an enhancement.
- Fixed an issue where the tooltip icon did not appear on the canvas after enabling the tooltip checkbox.
- Camera image no longer remains visible in the debugger after resetting the image.
- Resolved a sizing issue for stacks within the footer.
- Stack copy functionality has been fixed.
- Business Rules (BRs) now operate correctly for Checkbox Group elements.
- Improved functionality of the Range Seekbar.
- Adjusted the minimum width validation for Input Field and Dropdown elements to 32px.
- Fixed an issue where Smart Selector under Copy Data was unable to detect (').
- Resolved an issue where Input Fields duplicated automatically and could not be renamed.
- Resolved the issue of dismissible event for the pop up page and bottom sheet.
- Fixed the wrap issue for the LOVs for dropdown element.
What’s New in IT Ops & vConnect?
Force Logout submodule
The Force Logout submodule in the App Ops module in IT Ops is now operational. You can use it to kill one or more running user sessions for a mobile or web app consuming vConnect’s Auth service for login. On killing a session, the user will be logged out from the app once he performs an action that calls a vConnect service.
One of the use cases can be that if the user suspects that his account has been compromised or loses his phone, he can request a forced logout to ensure that any unauthorized sessions are terminated immediately.
Fig: This figure represents the Force Logout submodule
Learn More: Force Logout – Vahana Academy
Advanced Search Improvement
The Advanced Search functionality in Developer Logs and Event Logs submodules in Observability Module in IT Ops has been revamped to improve user experience and fix the issues with the previous search.
Fig: This figure represents the Advanced Search functionality in Developer Logs submodule
Import Release Configuration
We have introduced a new submodule Import Release Config in App Ops module in IT Ops that allows importing deployment configuration of Vahana apps (mobile, web, middleware) into VRT via manual import of configuration file. This functionality is given as an alternative to the existing direct sync mechanism.
This feature will benefit clients who prefer not to allow Vahana Cloud direct access to their systems for security reasons, by allowing manual import of app configurations into their VRT via client-side IT Ops (Standalone IT Ops - Upcoming feature).
To export the configuration, you must change the VRT type to “Export” for a VRT in Environments > VRTs (Vahana Run Time) in the Project Management portal. Once changed, the Sync button will switch to “Export” button when deploying configurations using existing flows for Designer 2.0, vFlow, or Middleware apps.
Fig: This figure represents the Import Release Config submodule
Other Improvements
- Environment Selection before an IT Ops module loads: After opening an IT Ops module and selecting the app, now you have to select an environment first before the opened submodule loads. This is done so that you don’t need to wait for the submodule to load with the default Environment before switching the Environment to open the module for the required Environment.
- Increased number of entries in Trace Logs Chart: Maximum number of entries to be displayed in Trace Logs chart in Developer Logs has been increased from 10 currently to 200.
- Ease of record switching in Developer Logs: Now you can also switch developer logs records to previous or next record when viewing a record so that you don’t have to go back to the previous screen to open other records.
- Updated centralized header and left menu: These have been updated to provide a unified experience as per the current Vahana design.
- Usage Analytics at Microservice and Connector level: Usage analytics were provided at Service level only in the Logs Analytics submodule in the Analytics module in IT Ops. We have now extended it to Microservices and Connectors also for more thorough analysis and debugging.
- Record Identifier in Developer Logs: A new column has been added in Developer Logs called “Record Identifier” to uniquely identify or filter records in the Developer Logs submodule in the Observability module in IT Ops. This will reflect the value configured in “Record’s Primary Key” field in a vConnect service.
- Updated Encryption Algorithm: Encryption algorithm has been upgraded in vConnect from SHA1 to SHA512.
- Microservices merger - ESB and DBES: This is done to improve performance and costs.
- Data Modeler Improvements: Removed transactional attributes, Implemented Scroll API for attributes, Optimized Data Modeler Unlink
Bug fixes
- User name has been fixed in Vahana Module to remove any invalid characters
- Resolved an issue where multiple session errors occurred. Now, the authentication API is executed first, followed by a check to determine whether multiple sessions are permitted.
Introducing vFlow Version 2.0
Redefining the experience—faster, Intuitive, and more powerful than ever before.
What’s New?
- Enhanced Performance
We’ve pushed the boundaries of speed and efficiency. The new version brings more than 40% faster performance, with reduced load times and smoother navigation. Whether you’re managing multiple tasks or handling complex operations, vFlow delivers unmatched responsiveness.
- Intuitive Design
Our design philosophy centers around simplicity and elegance. Version 2.0 introduces a refreshed UI with streamlined navigation, making it easier than ever to find what you need. Every detail has been carefully considered to enhance usability while maintaining the familiarity you love.
- Advanced Features for Greater Control with Legacy vs. Innovation
New Configurator
vFlow 2.0 comes with a completely new UI for developers, providing a unified view of page entities and a seamless top-to-bottom configuration journey. With enhanced data validation and market-aligned terminology, this makes app creation more efficient.
Learn More: https://academy.vahanacloud.com/design/an-introduction-to-vflow-2-0/
Real-Time Design Preview
The preview option allows developers to visualize designs across multiple devices as they develop, ensuring that apps look great on all devices.
API at L1
API configuration is now accessible at the L1 level, enabling the reuse of APIs throughout the entire app, which speeds up development and simplifies the integration process.
Messages at L1
A new feature at the L1 menu enables users to create and manage custom messages, which can be used as templates for notifications across the app, simplifying message management.
Other Additional Features
Property Information Panel Implementation
An info overlay provides contextual help and guidance when users hover over properties or options. This view-only panel enhances the configurator’s usability by offering visual previews and definitions without disrupting the workflow.
Functionality to Change Favicon
Users can now customize the favicon for their applications directly within vFlow, enhancing branding capabilities and the overall user experience in the browser.
Known Limitations:
- Multilingual support for Enum values is currently unavailable.
- DMS entities like image uploader and media uploader (DMS v3.0) are still under testing.
- When excluding a component in the integration branch, users must also manually remove it from the layout in newly created branches. This will be resolved with the migration of CUG apps to the new Configurator.
- The configuration of task groups will be empty during branch comparisons or conflict resolution.
- After deleting an element from a component or a task from a task group, users need to refresh the page manually to see the changes.
- UI issues are present in the Camera and Video elements of the Fieldset.
- Minor UI issues on configurator
Important Information:
- Default services, such as Auth_Vahana, must be configured under the vFlow API section.
- API integration at the Page, Component, and Element levels no longer requires response configuration to achieve the same functionality as before.
- The count on icons will need to be managed using custom CSS for now.