Support Article
CAParentID property stores different value in CPM HC 7
SA-21262
Summary
Between the PRPC 6.x and the Pega 7.x PCS releases, the content of CAParentID has changed from containing the pzInsKey to just the pyID. Custom code which relies on the former value no longer works.
Error Messages
Not Applicable
Steps to Reproduce
Not Applicable
Root Cause
The design of PCS changed. Custom code within a stored procedure written to utilize the fact that CAParentID contained a pzInsKey no longer works.
Resolution
The old pzInsKey can be reconstructed by concatenating the pyID with the InteractionClassGroup which can be found on the pxRequestor.Declare_CAApplicationSettings declarative page.
Published March 25, 2016 - Updated December 2, 2021
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.