Skip to main content

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

Enabling users to post messages in the activity feed

Updated on January 14, 2022
Applicable to Hybrid mode applications

Enable users to post messages in an activity feed for a specific context. For example, a user can make release announcements in the context of an application for all the application users to see.

Users can view their activity feeds in the Case Manager and Case Worker portals when they click the Pulse menu option.
This procedure applies to standard Pega Platform applications. For applications based on Cosmos React, see Configuring Pulse feed sources for Cosmos React.
  1. In Dev Studio, search for the pyPulseWrapper section.
  2. Override the pyPulseWrapper section that includes the pxFeed section.
  3. On the Design tab of a section or harness, click the pxFeed section.
  4. Open the Layout Properties panel by clicking the Settings icon.
  5. On the Parameters tab, in the Configure post settings section, select the Enable post check box.
  6. In the Context key field, define the context for posting messages by entering a key value.
    For example: Enter: Application.pxInsName
  7. In the section, select the message types that users can post:
    • To allow users to post public messages, select Message.
    • To allow users to post private messages, select Private post.
    • To allow users to create and assign tasks, select Task.
    Result: The post types are displayed in a menu when you open Pulse and click Post. For more information, see Posting a message in Pulse.
  8. Optional: Update the description of a selected message type:
    1. Next to the message type, click the Edit icon.
    2. In the Feed name field, update the description.
    3. Click Done.
  9. Click Submit.
  10. Click Save.

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. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us