Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Create Case smart shape not changing class name

SA-28758

Summary



When trying to extend the Appeals and Grievances framework into a custom built framework, a flow for creating a case and sub-case using the Create Case smart shape is failing to pick up the pxObjClass specified on the pagelist.


Error Messages



Not Applicable 
 

Steps to Reproduce

  1. Run the DetermineComplaint flow from the implementation application.
  2. Observe the spun off cases use the base framework class (PegaHC-AG-Work-Appeal) and not the pxObjClass value set on the pagelist.


Root Cause

An issue in the custom application code or rules. To dynamically set the child class, the Case Type option on the Create Case shape must be set to "other" and specified to match the property of interest. 


Resolution



Perform the following local-change:
Update the Case Type property on the configuration form of the Create Case shape to align with the dynamically ​set property of interest.
 

 

Suggest Edit

Published October 21, 2016 - Updated December 2, 2021

Did you find this content helpful? Yes No

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us