Skip to main content


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

Configuring the Tags widget

Updated on October 21, 2022

Help users find relevant information by providing a readable landing page that stores data with assigned tags. Displaying tagged data in one place saves users' time and enhances the process of analysis.

After user clicks a certain tag, the system displays a comprehensible landing page with cases and Pulse comments that contain that tag. For example, if you click the Testing tag, the system retrieves all cases and Pulse comments with that tag.

To use the Tags landing page, you configure the pyConfigureTagsLandingPageURL data transform that maps properties with a URL that holds the landing page.

Note: If you do not configure the data transform, then after clicking a tag, the system opens a list of cases with tags in a modal dialog box.
  1. In the navigation pane of Dev Studio, click Records.
  2. Expand the Data Model category, and then click Data Transform.
  3. In the list of data transforms, select pyConfigureTagsLandingPageURL.
  4. In the editing view for the data transform, choose the property for URL mapping:
    1. On the Definition tab, in the Action list of the .pyURLContent property, select Set.
    2. In the Source field, select a property that holds the URL mapping.
  5. In the upper-right corner of the data transform view, click Save.
For example:
Tags landing page

The following example shows the Tags landing page with all cases and Pulse posts that include the #ui tag.

Tags landing page that contains a table with details about each case and Pulse message that include the #ui tag.

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