Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


  1. At the time of releasing an app, you must store the following details about the app in the CT_MOBILE_APP_MASTER table in the database.

    Screen shot of the CT_MOBILE_APP_MASTER table:



    Note

    Separate records must be created in the CT_MOBILE_APP_MASTER table for each of the following conditions:

    • When the app is registered for multiple platforms.
    • When a new version of the app is released. The APP_STATUS for the previous version must be changed to INACTIVE to disable that version. You can delete the previous version entry from the table, if required. If the older version is inactive or the entry is not found, the customer is forced to update the app.

    The details of each column in the CT_MOBILE_APP_MASTER table are as follows:

    Column Name

    Description

    App_KEY

    Combination of app ID, app name, platform and app version. For example, com.intellect.canvas/SmartBank/Ios/1.3.0.0.
    It helps in determining whether the installed app is active in a device. If the app key is not available, the customer is forced to update the app. The force update message will be "Please update app". You must provide the app ID in the app key otherwise the app user is forced to update the app.

    APP_NAME

    The name of the app. For example, SmartBank.

    APP_VERSION

    The version of the app. For example, 1.3.0.0.

    APP_PLATFORM

    The platform/OS supported by the app such as Android, iOS BlackBerry or Windows.

    APP_STATUS

    It indicates the status of the installed app on the device. For example, ACTIVE.

    APP_STORE_URL

    The store location from where the app can be downloaded.

    SUPPORTED_OS_VERSION

    The OS version supported by the app.

    APP_RELEASE_DATE

    Release date of the app.

    APP_ID

    Unique ID of the app.



  2. You must specify the file path of the policy used for the app in the HYBRID_POLICY_PROV_CLASS property of the securityconfig.properties file. By default, Canvas provides the following policy files that can be overridden, if required:
    1. CTOneToOneHybridPolicyProvider
    2. CTOneToManyHybridPolicyProvider

      Following is the sample screen shot of the properties in the securityconfig.properties file:



      Note

      You can switch from One-to-One to One-to-Many policy any time by specifying the required policy file path. You can also disable the device management feature for the app by specifying 'NONE'. For example, HYBRID_POLICY_PROV_CLASS=NONE