Skip to main content


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

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Posting a message in Pulse

Updated on April 5, 2022

Post a message in Pulse to share information, for example, the status of a case, or to ask a question in a conversation thread.

Before you begin: Option to post a task in Pulse is available only in global Pulse feed and Spaces. To enable posting a task in a particular context, configure the feed gadget. For more information, see Enabling users to post messages in the activity feed
The following guidance applies to case messages, however, you can communicate in other contexts, such as a team or application. For more information, see Choosing a context for Pulse messages.
  1. Open a case:
    • Search for the case.
    • Click on the case in the worklist or work queue on your dashboard.
  2. Add a message by performing the following actions:
    • To add a message for all case users, click PostPost
    • To add a message for specific case users, click PostPrivate post, press the Down Arrow key, and then select the message recipients.
      Note: All the users involved in a private conversation can add more users to the conversation by referencing them, but only the owner can remove users from the conversation.
    • To create and assign a task in Pulse, click PostTask. For more information, see Creating a task in Pulse.
  3. Click Start a conversation, and then enter your message text.
  4. Optional: Change the format or content of a message before you post the message in Pulse.
  5. Click Post.

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