Pega Blueprint Import Module 0.2.16 is not displaying the list of case types

Blueprint and App Design
, , ,
1

Hi Team,
Pega Blueprint Import Module 0.2.16 is not displaying the list of case types during application creation. As a result, the Blueprint import process is failing.
Anyway we can downgrade the module or any fix for this.
Note we have selected all casetypes to be created as part of Import Process.

image
image1402×173 3.57 KB

@MarcCheong @BradTanner @SumanKumar
Thanks

2

Did you restart the instance once the module is upgraded to 0.2.16?

Could you please check Customize Build and add couple of case types to check if the problem persist?

4

Ramesh,

I tried to restart my Community Edition using Power Off & On, but surprisingly Community Edition is not coming up, not sure is the module is creating problem.

Thanks

5

Can you confirm if you have also redownloaded the blueprint and not using one stored locally from an older version of Blueprint

6

Yes Brad, I have downloaded the latest one from blueprint website.

7

could you send me the .blueprint file?

8

@SSrinivas in my community edition i can see the case types.

image
image1728×919 125 KB

image
image1620×849 64.8 KB

As advised earlier, i did power off after i updated the module to 2.16.

image
image1030×796 67.2 KB

9

Restart didn’t resolve the issue. From the logs, the pzConvertCaseToClasses activity was failing. I performed a Private Edit and attempted to save, which resulted in the error below.

image
image1308×591 94.3 KB

Subsequently, I cleared the Rule Cache via the DX API, after which the Blueprint import working as expected.

10

image
image1847×850 45.7 KB

I am still facing this issue. Can anyone of you please help?

11

This topic is closed as @SSrinivas confirmed resolution, it might be worth starting a new one so we can look at that in detail.

Be good to understand:

  1. What version pega you are using (i can see you have 2.17 import module)
  2. Did you restart your evironment after updating to 2.17?
  3. When did you download the blueprint file? (ideally that would be when you updated to 2.17 to ensure the version of your .blueprint file is compatible with 2.17)
  4. Have you attempted the troubleshooting mentioned:
    1. saving pzConvertCaseToClasses?
    2. cleared the Rule Cache via the DX API?

It may also me prudent to raise a support ticket, as there could be other environmental factors where we should look at local configurations