Question
Usage of Smart Shape - Create Case
When we use the smart shape - Create Case and choose the option to create multiple sub cases, then we have to provide either a pagelist/pagegroup property.
So this property should point to which class - a Work class or a Data class?
The PageList belongs to the case class which derives from Work-Cover-.
Each item in the PageList has a class that extends Data-.
Each page in the PageList can be passed as a Page Name parameter to a Data Transform defined in the spun-off case class.
The page name is also mentioned in Pages&Classes as having the expected Data- class.
Hi Lee,
I also thought the same, but if we configure the following on the "create cases smart shape".
- Create multiple cases - We select this option
- For each item in list - We provide a page list, applies to a descendant of Work-Cover- class, points to a descendant of Data- class.
- Case type - Provide the child case type
- Starting process - Provide the starting process
- Copy Page data to new sub case - Selected this option
With these configurations in the smart shape (attached a screen shot of the same) we are getting an error.
When I tried to debug the java code snippet in Step-5 of pxAddChildWork activity, sets the error message on the pyWorkPage.
/*
if (sMapType.equalsIgnoreCase("COPYTOCHILD") && !hasDataTransform) {
// Check that the child's class is equal to or derives from the source page property class
Hi Lee,
I also thought the same, but if we configure the following on the "create cases smart shape".
- Create multiple cases - We select this option
- For each item in list - We provide a page list, applies to a descendant of Work-Cover- class, points to a descendant of Data- class.
- Case type - Provide the child case type
- Starting process - Provide the starting process
- Copy Page data to new sub case - Selected this option
With these configurations in the smart shape (attached a screen shot of the same) we are getting an error.
When I tried to debug the java code snippet in Step-5 of pxAddChildWork activity, sets the error message on the pyWorkPage.
/*
if (sMapType.equalsIgnoreCase("COPYTOCHILD") && !hasDataTransform) {
// Check that the child's class is equal to or derives from the source page property class
String sListClass = pgSource.getClassName();
oLog.infoForced("****** BPMS Team Line 21 *****" + sListClass);
if(childClasSpecified){
if (!(sListClass.equals(sPageClass) || pega_rules_default.isAncestorOf(tools,sPageClass,sListClass))) {
myStepPage.addMessage("DescendantClassRequired", "pyMessageLabel", "@baseclass");
break;
}
}
}
*/
Then is this a defect in the Pega codebase or are we configuring something wrong.
The "Other" option is meant to be used in conjunction with Dynamic Class Referencing (DCR).
You would specify a Property such as .AppExtension.TaskClass
If hard-coding the class you should just select one from the drop-down..