Configuring the delivery of push notifications with the Push Notification shape
The Push Notification shape in the flow canvas enables the user to configure notification messages for delivery.
The following table lists the various roles involved in the push notification process along with their responsibilities:
|App Developer||Creates mobile app, which: |
Registers and un-registers app users for receiving push notifications from the application, via the provided REST services. See Push Notification User Registration Services for details.
Receives and displays push notification messages to app users.
Deploys app on app platform (for example, App Store, Google Play).
Provides marketing administrator with key registration information for app.
|Outside of Pega Customer Decision Hub|
|Administrator||Registers app for receiving push notification messages from Pega Customer Decision Hub.||In Pega Customer Decision Hub|
|App User||Downloads and installs app from app store.(Behind the scenes, app registers the user for receiving push notifications).||Outside of Pega Customer Decision Hub|
|Analyst||Creates actions and utilizes the Push Notification flow shape to send notification messages to registered app users.||In Pega Customer Decision Hub|
|System||Handles registrations of apps. |
Handles registrations/un-registrations of app users.
Delivers notification messages to registered users for registered apps.
|In Pega Customer Decision Hub|
The following General Configuration options are available for the Push Notification shape:
Notification message to push to the customer’s registered device(s). This can be plain text or an expression and can include property references.
If the Push notification is defined as a treatment for an Action, the message should be configured to reference .OfferData.PushMessage. Refer to Configuring push notification treatments for more details.
Associate sound with the notification message.
If this setting is enabled, the message payload references the default sound. When the message is received by the device, the device-specific default sound for notifications (if enabled) is played.
Marketing code used to identify the treatment.
This value can be passed to the device along with the notification message (as additional values).
A sample configuration for the general settings is shown below.
Users also have the option to specify the application where the notification should be sent.
The following Application Configuration options are available in the Application Configuration sub-section:
|Default Application||Determines whether the notification message should be pushed for the default app.|
|Other Application||Determines whether the notification message should be pushed for the specified app. Select the app to notify from the drop-down of configured apps.|
Setting the Default App
Administrators can mark one app as the default. This is beneficial in scenarios where there is only app or where a particular app is predominantly used. The default app is the (default) target for push notification messages in flows. Analysts can choose to override this by selecting a specific app
Use the Make Default action from the Actions menu to mark an application as the default.
Wait After Sending
Users can determine whether they would like to wait after sending a Push Notification or proceed directly to the next step in the Flow. The wait options available are the same for all wait-based shapes and are described in the section on the Wait shape.
Send Additional Values
Users can choose to include other information as part of the notification message payload. This data can be used by the app developer. Different platforms place different restrictions on the size of the overall message payload. Users should be aware of this limitation when specifying additional values. A notification message that ends up being larger than the allowed payload size may not be delivered.
Enable the Send Additional Values? check box (in the Additional Details section of the properties panel) to pass additional values. Use the grid controls to add fields. For each field, specify a name and value. The name must be plain text, but the value can be an expression. The key code can also be passed as an additional field.
The badge value can be sent in the payload of the push notification and displayed if the user's device's operating system supports this function.
Previous topic Uploading the required certificates for passbooks Next topic Configuring application settings for push notifications