Push Notification Architecture for Work Tasks Pro

The Push Notification of Work Tasks Pro App comprises of Azure Notification Hub wherein, the mobile application communicates with the AVEVA Work Tasks Server through Azure Service Bus.

The following section explains how to achieve the desired functionality for mobile applications.

• Push Notification

  When a task is assigned to a mobile application user, a notification alert has to be sent to their mobile device.

  The mobile channel which is a part of the workflow engine, tries to communicate with a push notification engine called Notification Hub. This is a multi-platform, scalable, push notification engine meant for quickly sending millions of messages or alerts from any back-end to any mobile device.

  With a single cross-platform API call, you can easily send targeted and personalized push notifications to any mobile platforms from on-premise back-end.

  The mobile channel which is a part of the workflow engine, communicates with the notification hub, provisioned for each client. However, if the workflow engine fails to establish the communication, the notification alert information gets stored in the database. If notifications are not sent, the notification service will retry based on settings configured in Retry Settings.

  The local Mobile Notification Service, which gets deployed with the AVEVA Work Tasks installation, ensures reliable delivery of the stored messages. The local Mobile Notification Service polls the information and schedules it for delivery on the basis of Retry Settings. The reliable delivery mechanism ensures that all the stored messages are delivered and no messages are lost during the transmission.

• Registration Services

  Registration service enables AVEVA Work Tasks to send notifications. Hosted REST service for registration enables AVEVA Work Tasks to send notifications. For registration process, see Registering to Wonderware Skelta BPM Mobile Notification Service.

  After successful registration and validation, the notification hub will be provisioned for each client and a key is assigned for each user. Based on the authentication, notification messages are sent.

  After the notification hub is provisioned, whenever AVEVA Work Tasks tries to send notification to mobile devices, communication happens only through notification hub. This hub is unique to each client and is responsible in communicating with the relevant platform provider and delivers the notification.

• Platform Providers and Mobile Application

  The platform providers deliver the notification alerts to the respective mobile devices, whenever a new task is assigned to the mobile application user. The alert is delivered to the mobile device service even when the mobile application is offline.