Question
LTIMindtree
IN
Last activity: 3 Apr 2025 6:12 EDT
How to update pxUpdateOpName after a case is processed by Queue Processor?
In our scenario case is created by Queue Processor, so before and after creating the case we're setting the pxCreateOpName and pxUpdateOpName as "System" in Queue Processor activity. We're good with pxCreateOpName but pxUpdateOpName is getting reset to "Queue processor(XXXXXXX)".
is there anyway to overwrite this?
We don't want to go with field value here, because we need to show it as "System" everywhere (Reports, Audit History, BIX... etc)
Thanks in advance :)
***Edited by Moderator Marije to change type from Pega Academy to Product; update capability tags***
Accepted Solution
Updated: 3 Apr 2025 6:12 EDT
LTIMindtree
IN
@im-ankit Thank you for the response!
We missed a step to reset it after case creation. Just corrected it and it's working fine.
Aaseya IT Services Pvt Ltd
SA
@SundeepK17193247 You can create a custom activity that updates the pxUpdateOpName after the case has been processed. Queue Processors allow you to configure custom post-processing actions after the case has been processed, and that's where you can update the pxUpdateOpName.
LTIMindtree
IN
@Hitesh Jain Could you please help, where is the option to add post-processing action! We're already setting the pxUpdateOpName in processing activity!
Capgemini
IN
As Hitesh said in above comment, you can have an activity that updates the pxUpdateOpName, post case creation by QP.
You can plug the activity at the end of your QP Activity. See snaps below
Case details view
I have done a quick implementation only, use best practice to open and save workobject in actual implementation.
Hope it helps !
Thanks, Ankit
Accepted Solution
Updated: 3 Apr 2025 6:12 EDT
LTIMindtree
IN
@im-ankit Thank you for the response!
We missed a step to reset it after case creation. Just corrected it and it's working fine.
HCA Healthcare
US
@SundeepK17193247 You can override pxUpdateOpName after the Queue Processor finishes by using a post-processing activity. Create an activity that sets .pxUpdateOpName = "System", then use Obj-Save with WriteNow to commit the change. You can trigger this using a Declare-OnChange rule that listens for pxUpdateOpName updates or a Declare Trigger on case updates. Another option is to use a custom system operator ID (e.g., SystemUser) and configure the Queue Processor to run under this ID, ensuring all updates appear as "System" automatically. This avoids manual updates and ensures consistency across reports, audit history, and BIX. Let me know if you need step-by-step details!