Vahana Release 2.7.20.0


vDesigner 2.0 & Vahana Cloud

:rocket: New Features

:new: Permission Check Functions & Open Device Settings

We’ve introduced a new feature to enhance permission handling and improve user experience: Permission Check Functions and Open Device Settings. These empower developers to manage feature access and guide users effectively when permissions are restricted or disabled.

Key Highlights:

  • Permission Check Functions: Developers can now check if specific app permissions (like camera, location, notifications, etc.) are granted. Click here to know more.
  • Open Device Settings: When a required permission is not granted, developers can redirect users to the corresponding app settings page using the Open Device Settings task. This redirection acts as a terminal step and ensures the user is guided to the right selected setting screen. Click here to know more.

:new: Forus SDK Integration

We’ve integrated the Forus Photo Liveness SDK into the V2, bringing the same trusted experience from the existing V1 app. This enables secure, contactless face capture and liveness checks within your journeys using a consistent, reliable SDK.

How It Works:

  • To register the SDK, go to the SDK Manager in your environment.
  • To consume the SDK in your flow, configure the Invoke SDK task within the vDesigner.

Click here to know more.

:sparkles: Enhancements & Improvements

:small_blue_diamond: Smart Selector Enhancements

We’ve rolled out major improvements to the Smart Selector to make selection, validation, and navigation more intuitive and efficient for all users.

:brain: Data Type Display: Each entry now shows its data type for better clarity.
:round_pushpin: Full Path Visibility & Copy Option: The full path of the selected entity or attribute is now visible, with a convenient option to copy it.
:mag: Exact Match Search Indicator: Introduced a UI icon to indicate when exact match search is enabled.
:window: Large View & Default View Settings: Added an expanded view for the Smart Selector to improve visibility and navigation.
:white_check_mark: Data Type Mismatch Check: Added validation to prevent selection of attributes with incompatible data types.

Click here to know more.

:small_blue_diamond: Enhancement: Environment-Specific Security Values

This enhancement introduces the ability to define and manage security values specific to each environment within the Security module. It enables better configuration control and simplifies security management across development, staging, and production setups.

:small_blue_diamond:

:small_blue_diamond: Background Attribute ID

We’ve added support for Background Attribute ID in layout components like Row, Column, Card, and Stack when used inside List and Grid List. This enhancement addresses a key usability gap where users couldn’t dynamically show background images or colors.

Click here to know more.

:small_blue_diamond: Permission Cleanup for Compliance

To align with Google Play’s Photo and Video Permissions policy, we’ve removed READ_MEDIA_IMAGES and READ_MEDIA_VIDEO permissions from Data On. These permissions are no longer required for one-time or infrequent media access.

:lady_beetle: Bug Fixes

  • Fixed an issue where checkboxes in Multilingual Export were misaligned to the left.
  • Fixed an issue where the upload icon in Download Build had incorrect positioning.
  • Fixed an issue where the color picker in Web builds was getting hidden on click.
  • Fixed an issue where the loader covered the full screen, hiding the left sidebar.

:hammer_and_wrench:Tech Debt

  • Application Management Frontend End Tech Upgrade
  • Message Master & Sync Code Optimisation
  • IAM, Account manager, Invite, Permissions, Email notifications & Data modeler Tech Upgrade
3 Likes

Hi Vikas,

It would be more helpful for the user if you could include some screenshots with these details—especially showing how the Smart Selector appears in a larger window.

Ideally, try to include at least one screenshot for each action to make it easier to follow and relate to.

Background Attribute ID

Details around this feature is very minimalistic, people will not understand if we will not elaborate properly. why was it needed, what actions we have done to do that. what are the possibilities?

Thanks!

@nimesh.singh @Shubhamkumar1 @praveen.sharma

1 Like