Vahana Academy

Applications

This post is referring to Vahana 2 (beta version). To check the document for production, please go to vDesigner-v1.0

After you log in to the Vahana front-end for the very first time, you automatically access the Vahana portal in your default workspace. The default workspace is created when you register with the Vahana front-end. After you access the Vahana front-end’s home page in your default workspace, you need to create an app.

On the Vahana front-end, the term “App” means a virtual application-based container. When you access this app container, it allows you to access Vahana front-end incorporated applications and services. In an app, you can perform the following functions:

Accessing Vahana cloud incorporated applications and services
Developing web application and mobile apps by accessing the vDesigner module
Deploying API in the vConnect module
Downloading build, etc.

Functionally, an app allows you to start and develop only one software application in the vDesigner module. By using a single app, you cannot create and develop multiple applications in the vDesigner module. To develop two or more applications in the vDesigner module, you need to create different new apps. Thus, you can access a newly created app and then access the vDesigner module to develop a new software application.

Note:- The app’s name is treated as the new application’s name in the vDesigner module.

In a workspace, you can create multiple apps. The Vahana front-end manages each component, including a user account, workspace, app, and others, by assigning a unique ID. It manages the workspace with a unique workspace ID. Similarly, it manages the app with a unique app ID.

When you create an app, Vahana front-end also allows you to connect the new app to the middleware. After you connect a new app to the middleware, you can perform the following functions:

Create a build of new application that is developed on the vDesigner module
Consume the API deployed on vConnect
Access other Vahana incorporated resources such as vConnect, Release Manager, VRT, etc.

Creating a New Application Journey

Creating a New Application (Native Mobile) (Old Screen)

Creating a New Application (A Few-Steps Away Convenient Journey)

Creating Middleware App (Old Journey)

Creating Middleware App (A New Two-Step Journey)

Creating a New App

When you want to access different modules and other resources on the Vahana portal, you need to create a new app and then access this app. After you access an app, you can access other Vahana modules based on assigned role and permissions. As described in the introductory section of this post, a newly created application or earlier created application serves as a virtual container to access Vahana cloud-incorporated modules and services.

To create a new app:

On the Vahana portal’s dashboard, click Create Application, and the Choose the type of your app page opens.
On the Choose the type of your app page, you can do one of the following:
- Click Native Mobile & PWA when you want to create a mobile app by using vDesigner.
- Click Web Application when you want to create a web application by using vFlow.
- Click Middleware when you want to create an application on the middleware portal.

After you select one of the available types of the application (for example, Native Mobile & PWA), click Next to display the Fill out the basic details page.
On the Fill out the basic details page, enter the basic details of the application as follows:
- App Icon:- Under App Icon, click to select one of the available icons or click the plus sign to upload an image from the local drive.
- Name:- In this box, write the name (for example, Demo_Mobile_App1) of the application.
- Tags:- In the box, enter an alphanumeric value (for example, mobile, app, or vDesigner). This value is treated as a tag. The tag is used to manage a tag or group of tags. You can use tags to search for a specific tag or a group of tags.
- Description:- In this box, enter a brief reason to create the application.
After you enter the basic details, click Next to display the Connect with Data Modeler page.
On the Connect with Data Modeler page, click the Data Modeler list and then select a data model to connect it to the application.

Note:- Connecting the data model to the application is an optional step. You can connect the data model to the application after you start implementing functionalities on pages. After you connect a data model to the application, you can store and manage the application-level data in entities and attributes. To know more about the data model, click here.

If you select the data model in the Data Modeler list, click Next, or click Skip to display the Choose Theme page.
The Choose Theme page displays the available themes in the current workspace.

On the Choose Theme page, click a tile to select the related theme (for example, New_CustomTheme), and then click Next to display the Connect with Middleware page.

Note:- If you choose to connect your application with middleware, you can integrate back-end services to the front-end (Demo_Mobile_App1) application. Also, you can connect the front-end application with the middleware application later.

On the Connect with Middleware page, do the function as follows to connect with the middleware:
- In the Workspace ID box, enter a unique workspace ID if you have created a middleware application earlier.
- After you enter a workspace ID in the Workspace ID box, click Verify in the same box.
- After the Vahana cloud authenticates the workspace ID, a green tick mark comes into view.
- Click the App Name list and then select a middleware application to connect with the front-end (Demo_Mobile_App1) application.

After you select the workspace ID and middleware app, click Submit to create a new application.

If you decide to connect the front-end application with the middleware application later, click Skip to create a new application.

Approving Front-end Middleware Connection Request

While creating a new app, when you connect the app to the middleware, the Vahana front-end application sends the connection request to the Vahana middleware. The Vahana portal sends the connection request to the admin of the app. Thus, in the middleware portal, you need to access the app with the app Id that you selected in the App Id box when you created the app on the Vahana front-end application. The middleware admin needs to access the middleware portal and then access the related app to approve the connection request as follows:

On the Vahana middleware’s home page, click Frontend App Requests, and the Frontend App Requests dialog box opens.
On the Frontend App Requests dialog box, click Accept to approve the request.

Connecting Existing Application to Middleware

When you create an app on the Vahana front-end, you can create it without connecting it to the middleware. In this case, you will successfully create the app, but you will not succeed to create a build of the application, consume and API, and other functions. While creating an app, you may decide to connect it to the middleware later.

To connect an existing app to the middleware:

On the Vahana front-end dashboard, click an existing app that is not connected to the middleware.
On the dashboard, click the app (For example:- My Test App) that you want to connect to the middleware, and the app dashboard opens.
In the left panel, click the App Settings icon (), and the App Settings page opens.
On the App Settings page, click the Connect Middleware tab.
On the App Settings page, click Go to Middleware, and the Vahana middleware’s login page opens.
To connect the app to the middleware, perform the steps from step 5 to step 12 that the Create a New App section describes.

After you perform the steps from step 5 to step 12, the App ID box displays the list of the middleware-incorporated apps’ ids.
In the App ID box, select an app ID, and then click Reqest, and the Vahana front-end sends the connection request to the Vahana middleware.

After you send the connection request to the middleware, you need to access the middleware.

Duplicating an App

This function allows you to duplicate an existing application. Duplicating an application also copies all application-level configurations. To perform this function, you need to have one of the following roles:

Account Owner
Workspace Owner

To duplicate an application:

On the Vahana portal’s dashboard, see the top panel.

In the top panel, see the Administrative icon () to the right of the notification icon ().
Click the Administrative icon () to display a list of menus.
In the list of menus, click Account Management to display the Accounts page.
On the Accounts page, put the mouse-pointer on the left panel, and the left panel expands.

In the left panel, under Account Management, click Workspace to display the Workspace Home page.

On the Workspace Home page, click a workspace (for example, CUG_Testing) to display the <<workspace name>> page.
On the <<workspace name>> page, see the right panel.
In the right panel, click the Applications tab to display the list of applications.

In the list, under Application Name, find the application (for example:- COIN).
After you find the application, move the mouse pointer in the same row to the extreme right, and a three-dot icon comes into view.
Click the three-dot icon to dislay a context menu.
In the context menu, click Duplicate to display the Duplicate <<App Name>> dialog box.
On the Duplicate <<App Name>> dialog box, click the Branch list and then select the application’s branch that you want to duplicate.
In the New Workspace ID box, enter the workspace’s ID of the destination workspace.

Note:- The destination workspace is the workspace where you want to duplicate an app.

After you enter the workspace ID, click Verify to verify the workspace.
After the Vahana cloud successfully verifies the workspace, the Duplicate <<Workspace Name>> dialog box displays the details of the workspace.

After workspace’s successful verification, click Duplicate Request to send the request to the account owner.

To approve or disapprove the user’s request to duplicate the app, the account owner needs to access the middleware portal. After the account owner approves the request, the app is duplicated in the destination workspace.

Deleting an App

The Vahana portal’s dashboard also provides you a feature to delete the existing app. After you delete the app, app-level connections, such as the app’s connection to a middleware, the app’s connection to a data model, and others, are also deleted.

When you perform the function to delete an app, the Vahana portal allows you to delete the application after double-verification steps. When you click the element to delete the app, Vahana portal displays a dialog box that asks you if you want to delete the app. If you decide to delete the app, the portal sends a unique OTP to your registered email ID.

After you enter the unique OTP and perform the function to delete the app, the portal verifies the OTP and then lets you delete the app.

To delete an app:

On the Vahana portal’s dashboard, click in the Search Filter box.

In the Search Filter box, enter the app’s name (for example, Kotak Mobile Banking).
Press Enter to search the app’s name, and the portal searches the app.
If the portal finds the app, it displays it in tile format.

On the app’s name’s tile, see the vertical three-dot icon.
Click this three-dot icon, and a context menu opens.
On the context menu, click Delete App, and the Delete Application dialog box opens.

On the Delete Application dialog box, click Proceed, and the Vahana portal performs the following functions:
- It sends a unique OTP to your registered email ID
- It displays the “Verify OTP” dialog box so that you can enter the OTP

Access your registered email ID and then find the OTP that the Vahana portal sent to you.
On the Verify OTP dialog box, in the Verification Code box, enter the OTP that you received on your registered email ID.
After you enter the OTP, click Verify & Delete to delete the application.

Disconnecting App from Middleware

The Vahana front-end portal allows you to disconnect an existing app from the middleware by using the following scenarios:

When User Disconnect Middleware from Front-end App

Case1:- (When the admin of the front-end application and middleware portal is same)

The Vahana front-end application’s user can disconnect the app from the middleware by clicking the Disconnect button in the dialog box.

On the Vahana portal’s dashboard, double-click the application’s name, and the application-related dashboard opens.
On the dashboard, see the left panel and then click the App Settings icon (), and the App Settings page opens.
On the App Settings page, click Disconnect, and the Disconnect Middleware dialog box opens.

In the Disconnect Middleware dialog box, click Disconnect to disconnect the app from middleware.

Case2:- (When the admins of the front-end application and middleware portal are different)

The Vahana front-end application’s user cannot disconnect the app from middleware by clicking the Disconnect button in the dialog box. When the user clicks the Disconnect button, the Vahana front-end application sends a request to the middleware portal’s admin.

To send the disconnection request:

On the Vahana portal’s dashboard, double-click the application’s name, and the application-related dashboard opens.
On the dashboard, see the left panel and then click the App Settings icon (), and the App Settings page opens.
On the App Settings page, click Disconnect, and the Disconnect Middleware dialog box opens.

In the Disconnect Middleware dialog box, click Disconnect, and the front-end application sends the disconnection request to the middleware portal’s admin.
In the right panel, click the Middleware icon (), and the middleware portal’s log in page opens.
Access the middleware, and then see the left panel.

In the left panel, click the application where you want to approve the request, and then click Frontend App Requests, and the Frontend App Requests box opens.
In the Frontend App Requests box, see the request to disconnect.

After you find the request, put the mouse pointer on the request, and then click Accept to approve the disconnection request.

When User Disconnect Middleware from Middleware

Case1:- (When the admin of the middleware portal and frontend application is same)

The application user can disconnect the middleware by clicking Disconnect Middleware in the dialog box.

Access the middleware, and then see the left panel.

In the left panel, click the application where you want to approve the request, and then click Frontend App Requests, and the Frontend App Requests box opens.
In the Frontend App Requests box, see the request to disconnect.

After you find the request, you can disconnect the frontend from the middleware in the dialog box.

Case2:- (When the admins of the front-end application and middleware portal are different)

If the admins of the front-end application and middleware portal are different, the user cannot disconnect the middleware from the frontend on the middleware portal. In this case, when the user clicks Disconnect, the middleware portal sends the disconnection request to the front-end application’s administrator.

To approve the disconnection request on the front-end portal:

On the Vahana portal’s dashboard, double-click the application’s name, and the application-related dashboard opens.
On the dashboard, see the left panel and then click the App Settings icon (), and the App Settings page opens.
On the App Settings page, click the Middleware tab.
In the Middleware tab, see the box that displays the text message: “Middleware” requested to disconnect the middleware.

In the box, click Approve to disconnect the middleware from the front-end application.

Sync Module

The Vahana portal (frontend application) provides the “Sync Module” feature to deploy changes, enhancements, or new development from the current branch to a destination branch. You can deploy the changes across the following environments that you configure by using the VRT (Vahana Runtime) module.

Developer
Test
Prod

Under these available environments, you can deploy the changes to the following branches:

Case1:- (If the environment is: Developer or Test)

You can deploy the changes to the following destination branches:

Feature
Integration
Release
Master

Case2:- (If the environment is: Prod)