Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

Creating feed sources for activity feeds

Updated on November 15, 2021

Inform users about events that are relevant to them by creating feed sources for messages from internal or external data sources. After you create a feed source, you can include it in a user activity feed.

For example, you can configure a Pulse feed to display posts from members of different departments.
Before you begin: To post and display messages, add the Pulse gadget to your application. For more information, see Adding the Pulse gadget to your application.
  1. In the header of Dev Studio, click CreateProcessPulse Feed.
  2. In the Pulse feed record configuration section, in the Label field, enter a short description for the feed source that you want to create.
    For example: Describe messages that users post for a team by entering TeamPosts.
  3. In the Apply to field, select a class to which this feed source applies.
  4. In the Add to ruleset field, select the name of the ruleset that contains the feed source.
  5. Click Create and open.
  6. In the Feed label field, enter a description for the new feed.
    By default, the system populates the feed label with the label that you provide in the Label field in step 2.
  7. In the Data page field, enter the data page that retrieves the messages for the feed.
  8. In the fields that appear based on the data page that you choose, configure additional parameters.
    For example: If you use the D_pxPostRepliesFeed data page to retrieve replies to user messages, in the UserID field, enter pxRequestor.pyUserIdentifier.

    The system uses this value to fetch replies to the messages that logged-in users post.

  9. Click Save.
What to do next:

Have a question? Get answers now.

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

Did you find this content helpful?

Want to help us improve this content?

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