Blueprint relation with Pega Customer Service case types

How can we import or tell the AI assistant in blueprint to consider or load all the case types from Pega Customer Service (with its related states and steps). I tried and seems like if its knowledge base does not considers articles such as Pega CS Case Types or/and what is already in the framework (Code).

My starting point is an scenario were we need to create a blueprint for a project were we know that we are going to implement Pega CS.

What I have been doing with blueprints is to do an initial import, de-selecting everything from my blueprint, and using import to just create my new application(s). I’ll get those merged, set up my dev ops pipelines, dev apps, test apps, etc. Then, I will import stuff into reuse layers as needed. Then I will import stuff into my implementation layer.

You might want to initially add your customer service case types to your implementation layer as you would otherwise do. After creating the CS cases, then you could run the import wizard to add in your blueprint case types and data (setting inheritance where appropriate).

In my experience, doing smaller imports makes them faster and easier to review and merge. In your case, doing the pre-app set up may help you get necessary infrastructure in place so it can be referenced post-import.

Hi Chris, thanks for your response.

I understand your advice for scenarios when we have some additional case types in the Blueprint that I want to add to the CS Framework in the platform.

What I am thinking is the scenario where we have a contract to implementing CS Framework and we even have identified the service case types to implement, let’s say “Address change, Close account, Create a new contact” for this example. I see two possibilities for this based on your comments:

  • Option 1: Add manually those case types in a Blueprint for getting the high fidelity level and even as part of the Pega Test Drive Foundation, but do not import the case types into the platform, as the real deal are the ones in the framework (here we might leverage data types, integrations and personas from the Blueprint, but we do not import the cases as a whole, here we just consider the delta in the requirements Blueprint-Framework
  • Option 2: Go classic, and showcase the wanted service case types to the customer directly in a Pega instance for demos.

How would you recommend to tackle this scenario?

Thanks and best regards,