Skip to main content

Creating UI subscription channels

Suggest edit
Updated on February 7, 2022

Provide a way to notify the client about changes on the server without having to explicitly refresh the application, by setting up UI subscription channels.

Notifications use a publisher-subscriber model where messages are published to a channel that broadcasts to all subscribers. You can create notification channels to send specific messages. You also can configure subscribers to listen to messages from a specific channel.

  1. In the header of Dev Studio, click ConfigureUser InterfaceNotification channels.

  2. In the upper-right corner of the Notification channels landing page, click Create.

  3. In the Notification channel dialog box, define the channel properties:

    1. In the Channel name field, enter a meaningful name that can help you identify the channel.

      The channel name is for labeling purposes only. The system uses the class name to identify which rule to run.
    2. In the Description field, define the purpose of your channel.

    3. In the Associated RuleSet field, define the rule set that you want to use.

    4. In the Class name field, define a class name for the notification channel.

    5. In the Properties to publish field, define which properties you want to include in the notification message.

    6. To define more properties, click Add properties.

  4. Click Create.

Integrate the channel with your application:
  1. Create an activity that uses a publish-notifications method to publish relevant properties to the notification channel. For more information, see Creating an activity and Publish-Notifications.
  2. Subscribe to the channel by adding an action set with an On load subscribe action. For more information, see Adding action sets to a layout and Available UI actions.
Did you find this content helpful? YesNo

Have a question? Get answers now.

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

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

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us