Skip to main content

Table of Contents

Configuring the delivery of push notifications with the Push Notification shape


Only available versions of this content are shown in the dropdown

The Push Notification shape in the flow canvas enables the user to configure notification messages for delivery.

The following General Configuration options are available for this shape:

Name Purpose

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.

Play Sound?

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.

Key Code

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.

Sample general configuration for push notification shape in action flow.

Application Configuration

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:

Name Purpose
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.

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.

Set Badge

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.

Did you find this content helpful?

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us