Author: Ankita Lakra

This task is applied to view the number of synced and un-synced records on the mobile app. When this task executes, it displays the number of synced and un-synced records on the mobile app. In comparison of Update Sync Status task, this task has broader functional scope. It maintains the number of synced and un-synced… Continue reading View Sync Details

When you apply this task, it updates the sync status. It captures recently updated number of synced records. This task is mainly applied at the application level so that the vDesigner application user can track the records and data that are synced at the API and database levels. After the data is successfully synced, it… Continue reading Update Sync Status

When this task executes, the mobile app user exits the app. The difference between the Logout task and the Exit task is that after the Logout task executes, the user logs out the app and needs to log in to the mobile app to access it again. After the Exit task executes, the mobile app… Continue reading Exit

After this task executes, it terminates the current user-session, and the mobile app user logs out of the mobile app. To access the mobile app again, the user needs to log on the app. You can apply this task to incorporate the logout feature in the mobile app. The logout task is commonly applied to… Continue reading Logout

This task is applied to sync the services that you deploy on the Vahana platform. After the service is synced, it interacts with the mobile app and other UI based panel. To apply the sync table task: After you apply the Sync Table task, the sync service is successfully synced and then can interact with… Continue reading Sync Table

This task is applied to copy the value of one object to another. When this task executes, it copies the value of source object to the destination object. To copy the value, you need to provide the JSON path of the source and the destination objects. To apply the copy value task: Box Description Copy… Continue reading Copy Value

This task is applied to make the control invisible after the user performs a function on the mobile app. To make the control invisible, the Is Visible property of that control should have Yes as selected option. To apply the control invisibility task:

This is very unique task in the vDesigner application. When this task executes, it deletes the entity/control/record that the user has currently selected to delete. To apply this task, you need to provide the JSON path of that parent entity under which you add multiple objects such as form, card, list, elements, and others. In… Continue reading Delete Current Child Object

After this task executes, the control becomes visible. This task is applied on the specific control or entity. After user performs the action on that control, another control becomes visible as a result of user-action. For instance: – If the user selects a state from the drop down list, another drop down list with the… Continue reading Control Visibility

This task executes to make a control active (editable) as a result of user action or any other event. After the control becomes active, the user can perform the function on the control. If you want to make the control active (disable) by applying this task, the Is Enabled property of the element should have… Continue reading Control Editable