‘Access Policy’ is one of the important features in the Vahana platform. It allows you to build the access policy for the mobile app that you design in the vDesigner application. Before publishing a mobile app, you need to define the access policy. While defining the access policy for the mobile app, you can define… Continue reading Defining Access Policy
Blog
Configuring Action on Card
This function allows you to configure an action on the list of the card. You can configure the action on the list horizontally or vertically. You can incorporate a phone book, delete function, and other usable action items. To configure an action on the list: Field Description Action Sub Type Click this list to select:… Continue reading Configuring Action on Card
Defining Card
You define a card to determine the layout for the list. The list displays the data on the card. To define the card, perform the function as follows: Box Description Attribute ID In this field, enter the attribute ID (For example: – ID). In the attribute ID, the list holds specific value and then displays… Continue reading Defining Card
Configuring a List
Overview In the vDesigner application, you can configure a list to display specific set of data in the list format. To display the data in different layout, the List feature incorporates multiple in-built card templates. When you configure a list, you need to select a template to determine a layout, in which you want to… Continue reading Configuring a List
Configuring a Card
In a mobile dashboard, you can configure a card. A dashboard card can consists of header, sub headings, list, textual content, media, icon, button, and other action items/features. The layout of the card is determined on the basis of content, image, or any other data that you want to show on the card. To configure… Continue reading Configuring a Card
Integrating Sync APIs
Introduction In the vDesigner application, the sync API (s) are integrated to insert the mobile app data into database table. As described earlier, the sync API inserts the data into two tables: tb_cop_buss_obj_txn and tb_image_data_obj. It inserts numeric and text based data into the tb_cop_buss_obj_txn table. To integrate a sync API in the vDesigner application,… Continue reading Integrating Sync APIs
Configuring Business Rule for API Call
Overview The vDesigner application allows you configure the business rule for and on different entities that you add to design a mobile app. These entities can include a control/element, form, card, list, and others. You can apply a business rule for several purposes such as disabling or enabling a control, satisfying a condition, displaying a… Continue reading Configuring Business Rule for API Call
Mapping Response Parameter
To map response parameters: Field Description API Name This list displays the name of API (For example: – Verify_professional) that you have selected to map the response parameters. Name In this box, enter the name of key/attribute (For example: – ID, name, data, and others) that the API receives in the response data that is… Continue reading Mapping Response Parameter
Mapping Request Parameters
Introduction In the vDesigner application, you can integrate different API to bind an action to different elements and controls. You can integrate two types of APIs, which are given as below: The sync API is specially used to insert the mobile app data into two tables: tb_cop_buss_obj_txn and tb_image_data_obj. The tb_cop_buss_obj_txn table stores the text and numeric data, while the tb_image_data_obj table… Continue reading Mapping Request Parameters
Introduction
In the vDesigner application, you can integrate different API to bind an action to different elements and controls. You can integrate two types of API(s), which are given as below: The sync API is specially used to insert the mobile app data into two tables: tb_cop_buss_obj_txn and tb_image_data_obj. The tb_cop_buss_obj_txn table stores the text and… Continue reading Introduction