Skip to main content
Person pointing at computer screen

How do I prep my Pega case type for Process Mining?

Martin Cook, 5 minute read
Welcome to the first entry in our "How do I…?" series on Pega Process Mining. Join us as we explore the fundamentals of becoming a world-class Pega Process Miner, from prepping your case types to identifying opportunities for improvement!

This month’s entry covers something that all Systems Architects need to know if they want to make use of Pega Process Mining’s Pega Connector – “How do I prep my Pega case type for ingestion by Pega Process Mining?”

In this blog we will answer the following questions:

  1. How can I check if my case type and metadata are available to Pega Process Mining through the Pega connector?
  2. How do I configure a case type for visibility in Pega Process Mining if it’s not already there?
  3. How do I configure a field to make it visible in Pega Process Mining?

A detailed walkthrough of all of these steps can be found here.

Background

Pega Process Mining can use the Pega connector to pull data from the Constellation DX APIs in Pega Platform™. To make this work, each case type needs a “queryable data page” so that Pega Process Mining can identify case types and retrieve case data.  Case types created in Pega Platform 8.1.x or later would have this configuration automatically, but watch out: if your case is from a version earlier than 8.1.x, it might not.

What you will (and won’t) need:

  • Access to Dev Studio
  • The ability to enable API access
These methods do NOT require access to a Pega Process Mining environment

How can I check if my case type and metadata are available to Pega Process Mining through the Pega connector?

Before we start making changes to case types, it's best to check what might already be set up and ready to be exposed to Pega Process Mining. To do that, you should:

  1. Enable API access to your source Pega environment
  2. Manually call the APIs to determine what case types are visible to Pega Process Mining
  3. Check what metadata is available for each case type

In this way, you will not only have a clear view of any case types that are already available to process with the Pega Connector, but also the fields that can be pulled through to enrich your analysis!

How do I configure a case type for visibility in Pega Process Mining if it's not already there?

What if you’ve completed the above steps, but you don’t see the case type you're interested in? No problem! All you need to do is create a queryable data page and use that as the default data source for the case type:

  1. Create a new Report Definition for the case type
  2. Create a new queryable Data Page that is backed by the new Report Definition.
  3. Update the default data source of the case type to use this ‘queryable data page’

Once you’ve done that, you can go back and manually call the APIs to see if your changes have worked.

How do I configure a field to make it visible in Pega Process Mining?

And finally, what if you’ve done all of that and now you cannot see the field you want to use as a filter for your Pega Process Mining analysis? Just carry out these last two steps:

  1. Make sure the field you want is tagged as a relevant record
  2. Optimize the field for reporting

And you're done! You’re now ready to pull your case type data into Pega Process Mining for analysis.

For detailed step-by-step instructions on how to complete the steps outlined in this post, please see our Support Document on the Pega Support Center.

 

Related Resources

Don't Forget

About the Author

As a product manager, Martin works to capture client and market needs to drive the direction of Process and Task Mining development at Pega.

Share this page Share via x Share via LinkedIn Copying...

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 Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us