Question
Capgemini
CA
Last activity: 20 Aug 2018 10:50 EDT
Case type is missing under Cases Tab
Hi,
We have a Case Type in Dev environment and when we moved it to the QA environment it's not displaying the Case Type under Cases tab. pyDefault Case Type rule is present in the class and we are able to create WOs for this case type.
Only it's missing under the Cases tab to see the graphical representation and add stages or steps.
Thanks
Accepted Solution
Pegasystems Inc.
IN
Hi DurgaVaraPrasad,
Are you referring to the case not being visible in the Case explorer. ? If so, could you check whether the class inheritance is "Work-Cover-" . If not could you please that.
Pegasystems Inc.
US
The case types are specified on the 'Cases & data' tab of the application rule. Was the application rule moved to QA? It sounds like there might be a different version of the application rule in QA.
Capgemini
CA
Hi Carissa,
Yes the application rule moved to QA and I am seeing the Case type on Cases & Data tab. But on the Application Overview I am not seeing the case type listed on QA. It's there on Dev Application Overview. Our Pega version is 7.1.5.
Thank you
Pegasystems Inc.
US
Can you run the Declare_CaseTree Data Page manually in each environment and trace it so you can compare and see what is causing the difference?
Capgemini
CA
Hi Carissaw, thanks a lot for your help. I traced the Declare_CaseTree data page on both machines and found that our case is missing on it. The reason behind it is the parent class of our case is referring Work- instead of Work-Cover-. So, in the when condition it's skipping our case. Updated the parent class to refer Work-Cover- and it's working fine now.
Thank you for the support.
Accepted Solution
Pegasystems Inc.
IN
Hi DurgaVaraPrasad,
Are you referring to the case not being visible in the Case explorer. ? If so, could you check whether the class inheritance is "Work-Cover-" . If not could you please that.
Capgemini
CA
Hi Mounika, thank you for the help. Yes the issue is with the Work-Cover- missing in the Inheritance path. We have the parent class referring Work- instead of Work-Cover-. So, the issue is because we missed moving the updated Parent class referring Work-Cover- to QA. Previously it pointed to Work- and was updated to Work-Cover- on Dev but we forgot to move it to QA. After the deployment of the update it's working fine now.
Thanks a lot.
Capgemini
CA
Hi Gayatri, the issue is because we missed moving the updated Parent class referring Work-Cover- to QA. Previously it pointed to Work- and was updated to Work-Cover- on Dev but we forgot to move it to QA. After the deployment of the update it's working fine now.
Capgemini
CA
Hi Raveendra, the issue is because we missed moving the updated Parent class referring Work-Cover- to QA. Previously it pointed to Work- and was updated to Work-Cover- on Dev but we forgot to move it to QA. After the deployment of the update it's working fine now.