Using tags to classify and later find cases

User Experience
1

Context

Client uses 32 different icons to “flag” submissions that have issues that need to be addressed in addition to the overall submission status. Users have options to search or filter by icon which is really performing a text based search on what the icon represents.

Our goal is to use tags in Pega to allow for -

  1. The application to tag cases programmatically based on external system statuses
  2. The user can search for / filter cases based on one or more tags
  3. The application can include some of the tags in prioritization logic
  4. The application can remove / replace tags as updates happen to the case in external systems

I’m fairly confident we can achieve items 1 and 4 through combination of decision rules, data transforms and / or activities and don’t need to demonstrate this.

I am hoping to show the client a simple demo where I will manually add tags to some sample cases in Pega and then using a combination of Insights (they want a pre-filtered view based on a tag) and promoted filters on a landing page that allows them to search / filter by one or more tags.

Can someone walk me through the steps for the basic demo?

2

@DaveFinley interesting Use Case. I have put together steps to get this more advanced reporting feature enabled for Insights (Explore Data)

Do not underestimate the effort in programmatically making tags - I have not done this before but it sounds like it could be tricky (need to find the right Activities/Data Transforms, hopefully provided out of the box)

Alternative Solution

You may want to consider a data reference. The end result would be much the same, the implementation would be a little simpler as you don’t need to create an Advanced Association rule to join different Pega objects together to show in Explore Data. That would be my first solution, before trying the solution I posted in the above article.