Setting Build Properties for Application in vDesigner

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

Before you create a build for the application designed in vDesigner, you need to configure several properties at the following levels:

  • Android:- This section allows you to define the icon, version number, version name, loading strategy, and others for the build that you want to create for the Android phones.
  • iOS:- This section allows you to define the icon, version number, version name, loading strategy, and others for the build that you want to create for the Apple phones.
  • Web:- This section allows you to define the icon, version number, version name, loading strategy, and others for the build that you want to create for laptops and computers.
  • Middleware:-This section primarily allows you to configure properties that enable the connection between the application and middleware-incorporated modules, such as vConnect, VRT, and others. Also, you can configure the S3 bucket’s name and ID so that you can store a variety of data, including documents, images, videos, logs, and others, in easily accessible object format.
  • Security:- In this section, you can configure check box-based security-related properties. You can click to select the check box to enable the property. Or, you can click to clear the check box to disable the property.

To configure the build settings:

  1. On the Applications page, search and find the application (designed in vDesigner) to create its build.
  2. After you find the application, click its name to display the Dashboard page.
  3. On the Dashboard page, see the left navigation panel.
  4. Put the mouse pointer on the left panel to expand it.
  5. In the left panel, click Downloads () to display the Downloads page.
  6. On the Downloads page, click Settings to display the Settings page.
  1. Under Environments, find the environment (for example, SAND_BOX) to configure the build-related properties.
  2. After you find the environment, click it to display all build-related properties:
  3. The following screen capture shows the build-related properties:
  1. To configure the build-related properties, see the following tables:

Android Settings

Android SettingsDescription
Upload Icon ()Click the plus icon to select the icon of the application from the local drive.
Upload a Splash IconClick Browse to upload a splash icon, which comes into view on a specific page in the application. When the user accesses the application, it loads the related page to display the splash icon.
App NameIn this box, enter the name of the application’s build. The Play Store service displays the build by the name that you enter in the App Name box.
Version NameIn this box, enter the version name (for example, 1.4.5) of the application’s build. When the user installs the application, he can access the application’s version name in the application’s information.
Version CodeThis box displays the value by default. When you create a build of the application, the Downloads module automatically or incrementally generates the version code and then displays it in the Version Code box.
Package NameThis box displays a default value, com.yvjzj.app. You change this value to another value in the following format:
com.<<random text value>>.app

The package name is used to manage and identify the app on the Play Store.
Min SDK VersionIn the mobile phone device, the version number of the android operating system is internally mapped with a specific SDK version. For instance:- Android operating system’s version 11 is internally mapped to the SDK version 30.

When you select a specific SDK version (for example, API 28) in the Min SDK Version box, you define a back version of the Android operating system on which the user can install the application.

If the end-user installs the application on the operating system that is older than the configured back-version, the application’s build will not allow the user to install the application.
Upload Push Notification FileYou can use this property to send the notification to the application’s user. In this property, click Browse to select the notification file. After you select a push notification file, the app server sends notification messages to the app’s user periodically.

These notification messages include periodic alerts, app-related updates, event reminders, system-related alerts, and others.
Do you want to upload the signing certificateClick this check box to upload the signing certificate related to the new mobile app. The signing certificate is issued by the certificate authority, such as Google Keystore for Android or Apple’s Developer Certificate for iOS. After you click the check box, the following properties come into view.

1. Signing Certificate:- Click Browse to upload the signing certificate that the certificate authority provides.

2. Alias Username:- In this box, enter the alias user name. The alias username serves as an identifier for a specific key (alias) in the keystore.

3. Alias Password:- In this box, enter a password. This password is used to access a specific key associated with the alias name.

4. Store Password:- In this box, enter a password to protect all data in Google keystore or Apple’s Developer Certificate.

The Google keystore or Apple’s Developer Certificate contains data in encrypted format that prevents unauthorized usage of the application within the Android or iOS platforms or outside the platforms. Conclusively, you can define the Alias Username, Alias Password, and Store Password to protect information in the Google Keystore, in addition to the encrypted key-related data.
DescriptionIn this box, you can enter a brief description about the app’s build. The description can contain the information related to the app’s usage or app’s project’s objective.
Loading StrategyThis property contains the options to define how the app will load on the device when the user accesses it to use it. These strategy options are given as below:
a. Eager:- It loads the app’s configuration details before the app is launched.

b. Lazy:- It loads the configuration details based on the requirements, and it reduces the application’s loading time.

c. Only Embedded Config:- It embeds all configuration details in the application. This strategy eliminates the usage of the API to load the configuration details.

d. Embedded Config with Deployment Check:- This strategy embeds initial configuration details in the application and then fetches the delta changes that the developer incorporates into the application after the deployment.

iOS Settings

iOS SettingsDescription
Upload Icon ()Click the plus icon to select the icon of the application from the local drive.
Upload a Splash IconClick Browse to upload a splash icon, which comes into view on a specific page in the application. When the user accesses the application, it loads the related page to display the splash icon.
App NameIn this box, enter the name of the application’s build. The Play Store service displays the build by the name that you enter in the App Name box.
Version NameIn this box, enter the version name (for example, 1.4.5) of the application’s build. When the user installs the application, he can access the application’s version name in the application’s information.
Version CodeThis box displays the value by default. When you create a build of the application, the Downloads module automatically or incrementally generates the version code and then displays it in the Version Code box.
Package NameThis box displays a default value, com.yvjzj.app. You change this value to another value in the following format:
com.<<random text value>>.app

The package name is used to manage and identify the app on the Play Store.
Min iOS VersionIn this box, select an iOS version (for example, iOS 15). When you select a specific iOS version (for example, iOS 15) in the Min iOS Version box, you define a back version of the iOS operating system on which the user can install the application.

If the end-user installs the application on the iOS operating system that is older (for example, iOS 13) than the selected iOS version, the application’s build will not allow the user to install the application.
Upload Push Notification FileYou can use this property to send the notification to the application’s user. In this property, click Browse to select the notification file. After you select a push notification file, the app server sends notification messages to the app’s user periodically.

These notification messages include periodic alerts, app-related updates, event reminders, system-related alerts, and others.
DescriptionIn this box, you can enter a brief description about the app’s build. The description can contain the information related to the app’s usage or app’s project’s objective.
Loading StrategyThis property contains the options to define how the app will load on the device when the user accesses it to use it. These strategy options are given as below:
a. Eager:- It loads the app’s configuration details before the app is launched.

b. Lazy:- It loads the configuration details based on the requirements, and it reduces the application’s loading time.

c. Only Embedded Config:- It embeds all configuration details in the application. This strategy eliminates the usage of the API to load the configuration details.

d. Embedded Config with Deployment Check:- This strategy embeds initial configuration details in the application and then fetches the delta changes that the developer incorporates into the application after the deployment.

Web Settings

Web SettingsDescription
Upload Icon ()Click the plus icon to select the icon of the application from the local drive.
Upload a Splash IconClick Browse to upload a splash icon, which comes into view on a specific page in the application. When the user accesses the application, it loads the related page to display the splash icon.
App NameIn this box, enter the name of the application’s build. The Play Store service displays the build by the name that you enter in the App Name box.
Version NameIn this box, enter the version name (for example, 1.4.5) of the application’s build. When the user installs the application, he can access the application’s version name in the application’s information.
Version CodeThis box displays the value by default. When you create a build of the application, the Downloads module automatically or incrementally generates the version code and then displays it in the Version Code box.
Upload Push Notification FileYou can use this property to send the notification to the application’s user. In this property, click Browse to select the notification file. After you select a push notification file, the app server sends notification messages to the app’s user periodically.

These notification messages include periodic alerts, app-related updates, event reminders, system-related alerts, and others.
DescriptionIn this box, you can enter a brief description about the application’s build. The description can contain the information related to the application’s usage or project’s objective.
Loading StrategyThis property contains the options to define how the app will load on the device when the user accesses it to use it. These strategy options are given as below:
a. Eager:- It loads the app’s configuration details before the app is launched.

b. Lazy:- It loads the configuration details based on the requirements, and it reduces the application’s loading time.

c. Only Embedded Config:- It embeds all configuration details in the application. This strategy eliminates the usage of the API to load the configuration details.

d. Embedded Config with Deployment Check:- This strategy embeds initial configuration details in the application and then fetches the delta changes that the developer incorporates into the application after the deployment.

Middleware Settings

Middleware SettingsDescription
Application IDThis box automatically displays the application ID of the current application.
Org IDThis box also automatically displays the workspace ID of the current workspace in which you are creating the application’s build.
Client SecretThis box automatically displays a unique client secret ID, which is used connect to the Vahana Run Time Manager.
vConnect Endpoint URLThis box displays the URL to connect to vConnect APIs for the data manipulation.
Config fetch URLThis box displays the URL related to the app’s configuration details. When the user launches the application, the configured loading strategy loads the configuration details from this URL.
Storage IDIn this box, enter the alphanumeric storage ID (for example, g8a0ef8f-ff1f-64a3-8d5b-2bda8aabc78b). The storage ID internally points to different AWS buckets (for example, S3 bucket, Oracle bucket) where you want to store the data.

Note:- When you create the application build, you need to contact the Decimal Technologies’ DevOps team to get the storage ID.

In the DMS bucket, you can store a variety of data such as, backup data, full dump, temporary data, migration-related data, data logs, and others.
DMS Bucket NameIn this box, enter the DMS bucket name (for example, decimal-integrations) where you want to store the data. The data is stored in the DMS bucket based on the storage ID and DMS bucket name.

Note:- You also need to contact the Decimal Technologies’ DevOps team to get the DMS bucket name.
Allow SSLClick this check box to enable SSL (Secured Socket Layer)-based data transmission.
Select SSL CertificateClick Browse to upload the SSL certificate in .cer and .cert formats.

Security Settings

Security SettingsDescription
Bypass SSLClick this checkbox to disable the SSL-based data authentication and transmission.
Allow Rooted DevicesWhen you click to select this check box, this property provides the administrative-level access to the Android devices. Thus, the end user can install the app on the Android operating system by bypassing all operating system-level restrictions and settings that block app installation on the devices.

In the device’s operating system, these settings and restrictions guard the device from the malware and other Internet-based threats.
Allow Landscape ModeIf you click to select this checkbox the end user can use the application in the landscape mode in the mobile devices and tablets.
Allow ScreenshotsIf you click to select this check box, the end-user can take the screen capture of the application’s pages.
Allow Copy PasteIf you click to select this check box, the end-user can copy the content of the application and then paste it to another place.
Enable DebuggerIf you click to select this check box, the “debugger” feature becomes active in the application. If you make the debugger feature active, you do not need to apply the debugger task in the application.
Embed Configuration with BuildIf you click to select this check box, the application build embeds the application’s configuration details into the application.

Thus, when an end user accesses the application, the application loads the configuration details faster to display the application’s content to the user.
Override Device FontIf you click to select this check box, the application-level font settings override the device-level settings. In this case, when the end user changes the font settings at the device level, it does not change the font’s settings at the application level.
  1. After you configure Android, middleware, and security settings, scroll down the Settings page to the end and then click Save to apply the build-related settings.
Was this article helpful?
YesNo