Sending Push Notifications to Enterprise App Store

Overview

Enterprise App Store (EAS) the app distribution service that enables an enterprise to manage and distribute customized apps to their users supports sending Push Notifications. EAS has been enhanced to provide the Kony Engagement Services support for the client app.

You can now send manual push messages to all registered devices, or to a subset of devices, based on the device ID. This functionality is available for all Android devices as well as the web channel. The Engagement Services provide a subscription-based notification mechanism that enables users to subscribe their devices to receive notifications.

When an EAS app is launched on a device, the device is registered to the Engagement Server that is linked to your environment. In case the EAS login is disabled, the device is registered only by the device ID. If the EAS login is enabled, the username of the person is also registered. After the device registration is completed, you can send push notifications to your entire user base or to select users.

Configuring a Push Notification

  • Administrator rights to a Kony Engagement App. If you do not have an app in the Kony Engagement Server, you can refer to Adding Apps to the Engagement Server.

    • NOTE: To create an app for the Web channel in the Engagement Server, refer to Add New App for Web.

    NOTE: For more information on generating a Server Key and Sender ID for Web devices, refer to Generating FCM Server Key and Sender ID for Web Devices.

  • For enabling push notifications on the Web channel, go to your Visualizer Project Workspace > projectProperties.json and do the following:

      In projectProperties.json add following key value pairs:

    • "enableProgressiveWeb": true
    • "enablePushNotificationsDW": true
    • "enablefcmpushnotifications": "true"
    • "fcmsenderid": xxxxxxxxx (senderID of your FCM project)
  • Go to Admin Console > Settings and do the following:

      In Client App Properties of App Services add the following key-value pairs:

    • PUBLICKEY : xxxxxxxxxxxxxxxxxxxxxxxxxx
    • SENDERID : xxxxxxxxxxx

Device Registration on the Engagement Server

When a user opens an EAS app, the following scenarios can occur:

  • EAS without authentication: The app opens and the device ID of the device on which the app is opened is registered on the Engagement Server.
    • In the Kony Engagement Console, under Overview, click Subscribers. The Devices tab appears, with a list of all the devices registered to the server.
    • You can send a generic message to these users, for example, "The Enterprise App Store will be unavailable on Sunday, 1st Dec 2019, to perform maintenance operations on the system.".
  • EAS with authentication: The sign in screen appears, you must sign in to the app with the required credentials. The device ID of the device on which the app is opened is registered on the Engagement Server along with your User ID.
    • In the Kony Engagement Console, under Overview, click Subscribers. The Devices tab appears, with a list of all the users and their User IDs registered to the server.
    • You can send specific messages to these users, for example, "Your account on the HR App will be made inactive in a week due to inactivity. To continue to use the HR App, please login to your account.".

Sending Push Messages

To configure a push message, follow these steps on the Kony Fabric Console:

  1. From the Engagement section, click Adhoc from the left panel. The Adhoc screen appears, displaying the following three tabs: Adhoc information, Select Users, Define Message.
  2. In the Adhoc Information tab, provide the type of message and application name to which the message should be sent. You can also schedule the date and time at which the message should be sent. For more information on selecting date and time, refer to Send Message.
  3. In the Select Users tab, you can choose the entire subscriber list of the selected application or a Segment of users. For more information on how to create a Segment in Kony Engagement Server, refer to Adding a Segment.
  4. In the Define Message tab, you can define the message that should be sent to your subscribers.

For more information on how to trigger a push notification through Engagement Server, refer to Push Message.

  • When a push is triggered, if the EAS app is open on a device, a notification appears on the device.
  • When a push is triggered, if the EAS app is closed on a device, a status notification appears on the device.