Vahana Academy

Home   >   Design • Integrating Different APIs with vDesigner • V1 • vDesigner

Category: vDesigner

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

Configuring ID Generator

This feature allows you to define the ID generator rule for newly created entity. After you configure ID generator rule, it automatically generates a unique ID for the respective entity when Load New Object task executes as a result of specific action. To configure ID generator: Box/Field Description Group Name In this field, enter the… Continue reading Configuring ID Generator

Defining Relationship between Entities

After you create multiple entities, you can define the relationship between two entities. While defining the relationship, you can make one entity as a child entity of another entity. You can define the relationship between two entities as follows: To define the relationship: Box/List Description Parent Entity Click this list, it displays the currently existing… Continue reading Defining Relationship between Entities

Creating New Entity

Introduction The vDesigner application provides you the Entity and Relationship feature that contains two different sub-modules: Entity and Relationship. The entity module allows you to create entity. The relationship module allows to establish the relationship between two entities. While establishing relationship between two entities, you make one entity as a parent entity and therefore can… Continue reading Creating New Entity

Component Migration

After you add new screens and controls or modify the existing screen(s) or controls by using the vDesigner application, you mandatorily need to migrate the added or updated components from the local environments to the cloud environment. If you do not migrate the component, the mobile app will not display newly added screens and controls… Continue reading Component Migration