Child Case creating on PageName like "IteratePage_< < classname > > "
When I'm trying to create child case from parent case using create case smart shape.Child case is getting created on IteratePage_<<classname>> but not on pyWorkPage.
In Parent Case --> First Stage--> First Step flow contains (start shape --> Create Case --> End shape.No assignments in flow.)
if there are any assignments before to Create Case shape then pages forming correctly like ParentCase on pyCoverPage and ChildCase on pyWorkPage.
In tracer I noticed that activity OpenAndLockWork step 2 when rule condition (@GetInstanceHandle(Param.workPage, tools) != Primary.pxRefObjectKey(primary page going as newAssignPage) getting false(when there are no assignments) and this activity is doing renaming the IteratePage_<<classname>> page to pyWorkPage in step3.
I tried in both Pega 7.1.9 & 7.2.2 facing same issue.
Can any one please let me know what may be the issue here?
Please see the Screenshots.
Parent Case Flow
**Moderation Team has archived post**
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.
You did some great investigation. It sounds like it is definitely working as coded. I don't know about the underlying design decision for that activity, but I can say that by default you only have a newAssignPage when there is an assignment being actively worked. As such, I wouldn't expect that page to be present if there is no assignment in the flow. In theory, you could add a utility that puts a newAssignPage into the clipboard before doing this, to avoid that. I have no idea what may break if you have an empty stub if downstream the process engine expects actual data there, but it might be a good place to start.
OpenandLockWorkobject getting called whenever an assignment is processed. But in my Parent case there are no assignments.
When the flow entered into the sub case and at this time once it reaches at Assignment newAssignPage is created and OpenandLockWorkobject getting called but this time it's failing this condition @PageExistsWithClass(Param.workPage, tools) in step2 of OpenandLockWorkobject activity. Here the Param.workPage is "IteratePage_<<classname>>" and the page exist in Clipboard with class formed but still returning false .
I would definitely need to dig into this more to be able to offer much more helpful advice. I suspected stubbing out the page would have downstream surprises. Do you think the problem is with the system trying to deal with the Page-LIst of new work items? Would it work better if your activity spun off a top level page for the child and once the page is properly created, copy the item into the Page-List and then delete the top level page? I'm wondering if you are pushing the API in ways that were never considered by the developers and that it doesn't quite support. Creating a wrapper for the call is a few extra steps, but might be less work in the long run.