yt110154
(Y Naga Venkata Satya Sai Kumar Tanuku)
1
Hi, There is use case where i need to transfer assignment along with that i need to modify few fields in the workpage. I configured casewide localAction and post Activity steps as below.
Since i need to pass assignment key to pxTransferAssignment, getting .pxAssignmentKey from pxFlow.
PropertySet values that i need to set on workpage.
3.Calling Save
4. Call pxTransferAssignment with step page as page with defined work class.
Issue: Once case is transferred i cannot see assignment i can see only when i refresh. can you please guide me on this?
Is this issue specific to Worklist or WorkQueue transfer? Could you pleaes confirm if you’re using OOTB pxTransferAssignment flow action observing the same behavior to isolate the issue?
yt110154
(Y Naga Venkata Satya Sai Kumar Tanuku)
5
This issue i m facing when i transfer to WL, i didn’t tried with WB. when i use OOTB flow action i m not facing this issue.
If you were to use case management for this then you could just change stage / restart stage to regenerate the assignment assigned to the right person?
This then gives you a process in your case lifecycle, where you can run a data transform and manipulate the data.
AND we know that the UX is tied to this kind of case management so you will see the assignment / back-to-back processing will take place.
It also avoids any kind of locking, clashing or custom error handling in your activity.
I have done this on many occasions when activities become overly complex or the Pega UX isn’t optimal in the approach built.
Just curious, since OOTB works as expected, OOTB logs the audit log to record this assignment was transferred or reassigned. What extra properties required for the case to record it?