Question
ING Belgium SA NV
BE
Last activity: 10 Jul 2025 9:59 EDT
Resolve case stage not working after queue processor
In order to do better errorhandling, we execute some processing in a queue processor while the case is assigned to "[email protected]" to wait until the queue processor execution is done. Once the execution is done, the QP-activity calls "ResumeFlow" in order to proceed the case. It now comes to our attention that, in case the case can proceed until the end stage, the case is not correctly closed. The OOTB pxForceCaseClose is executed on pyQueuePage. In step 4, the current primary page (pyQueuePage) is copied into a workpage In step 11.1 This workPage is used as pgWork in order to close all assignments and resolve the case. So by the end of step 11.1, pgWork has a status "Resolved-whatever", but my pyQueuePage is still in "Ongoing" As the pgWork is not copied back into the primary page, when I reach the end of my QP-activity, the case is overwritten by whatever is in pyQueuePage, resetting my status back to "Ongoing". Do I do something wrong? Is this a bug in Pega? Should I have taken another approach in case I want some processing to be done by a QP before continuing my normal caseflow? Looking forward to your feedback!
Publicis Sapient
IN
Hi @Joris Claus
Hope this helps
This issue might happen because pxForceCaseClose updates a temporary pgWork page, but your Queue Processor saves pyQueuePage, which still holds the old status. Try adding a Page-Copy from pgWork to pyQueuePage at the end of your QP activity to persist the resolved state. Alternatively, let the case naturally resolve by just using ResumeFlow, or move the resolution logic to the flow after the QP completes.
ING Belgium SA NV
BE
Hi @PoojaPalla, Thnx for your reply but this doesn't work.
- pxForceCaseClose removes the temporary pgWork page in the end so, you're not able to take a copy of it afterwards
- also "let the case naturally resolve by just using ResumeFlow" is not working as this is the approach we're currently using. The QP does a ResumeFlow, but as this happens within the QP-activity, the complete process is handled within this threat, so after the "Flow" that has been resumed comes to an end (and the case is in "Resolved-...", the QP still overwrites it in the end of it's threatlife...
HCA Healthcare
US
@Joris Claus The issue happens because the Queue Processor runs on a temporary page called pyQueuePage, and when you use pxForceCaseClose, it creates another page (pgWork) to resolve the case. Although pgWork gets the resolved status, this status is not saved back to pyQueuePage. So, when the Queue Processor finishes, the case is still marked as "Ongoing" instead of "Resolved". To fix this, after pxForceCaseClose, you should copy pgWork back to pyQueuePage or use Obj-Save on pgWork to save the resolved status. Also, make sure to commit the changes. This way, the final status will be saved correctly, and the case will close as expected.