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.

Adding a reference in Pulse

Updated on April 5, 2022

You can reference a user, space, document, or case in a comment or post that you add to Pulse. By including a link in your message that opens a relevant user profile, user group, application document, or work item, you can add context to a conversation.

Before you begin: Enable search indexing for work items.
  1. Enter your message text in Pulse, but do not post the message.
  2. Place your cursor in the message text, and then enter @.
  3. Select whether you want to reference a user, space, document, or case.
  4. Type one or more characters to narrow the list of results and select a value from the list that is displayed.
  5. Click Post.
Result: Individual users and users of the spaces that you reference are notified about your message, based on their notification settings. Documents and cases that you reference become links in your message.
  • Restricting case references in Pulse

    You can control which cases users can reference in the messages that they post to Pulse. By limiting the choices in the list of suggested cases, you can help users create messages more quickly.

  • Differentiating case references in Pulse

    You can control which icons and descriptions are displayed to users when they reference a case in Pulse. By visually differentiating the choices in the list of suggested cases, you can help users create messages more quickly.

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