We have upgraded from Pega 6.2 to Pega 7.2 recently . We had CPM portal so upgraded that also to 7.2. Now when we are trying to execute our flow from portal, we are getting harness fail error. We have saved as the latest OOTB ''CPMPerform'' harness from PegaCPMI-Work-Interaction into our application ruleset and tried executing - we were getting this error - Error(s) detected while generating java. Compiler reported: ---------- 1. ERROR in //opt/WAS/profiles/AppSrv01/temp/AppSrv01/wasap01/wasap01_PRPC/prweb.war/com/pegarules/generated/ProcessXSLT_071027_M_J_Gnia4_2wyx2U_GHKbA.java (at line 117) tFactory.setAttribute(javax.xml.XMLConstants.ACCESS_EXTERNAL_DTD, ""); ^^^^^^^^^^^^^^^^^^^ ACCESS_EXTERNAL_DTD cannot be resolved or is not a field ---------- 2. ERROR in //opt/WAS/profiles/AppSrv01/temp/AppSrv01/wasap01/wasap01_PRPC/prweb.war/com/pegarules/generated/ProcessXSLT_071027_M_J_Gnia4_2wyx2U_GHKbA.java (at line 118) tFactory.setAttribute(javax.xml.XMLConstants.ACCESS_EXTERNAL_STYLESHEET, ""); ^^^^^^^^^^^^^^^^^^^^^^^^^^ ACCESS_EXTERNAL_STYLESHEET cannot be resolved or is not a field ---------- 2 problems (2 errors) Compile failed.
This error is because of another section ''CPMTabNavigation'' of PegaCA-Work-Interaction present in the CPMPerform harness.
When we remove this part of section from the harness the screen is rendered. but we need to have this section also. We also feel that this section has a function backend and that function is not getting generated. How can we make the function to be generated successfully ?
Please help us on this resolution.
Thanks In Advance!
***Updated by moderator: Lochan to update Categories***
Hi Anahita, if you are using CS 7.22 and the new Interaction Portal, you should not have to worry about the CPMTabNavigation Section at all. Those sections were used in the older CSR portal. The new portal uses the standard Perform harnesses, instead of the CPMPerform harness. Please refer to the CS 7.22 documentation on how to properly upgrade from an older version of CPM. The CSR portal is completely deprecated in this version of Customer Service and requires additional rulesets to work properly.