Flow not proceeding to next assignment upon cancelling a modal window from a repeat grid.
Hi,
I'm launching a modal window on click of a button in a repeat grid to attach document(which is an optional action). Upon cancelling the modal window without uploading any document and clicking on submit in the main screen, the flow isn't moving ahead to the next assignment. The screen displays the successful execution of rule message. I have to pick the WO again from my worklist to work on it.
I don't have any post processing activity configured in the main flow action. PFA screenshots.
Note: Upon reopening the WO from WL and clicking on Submit the flow moves ahead to the next assignment. Some issue with the on click action configuration.
Regards,
Sovan
Pegasystems Inc.
IN
Hi ,
For attachment what is the control which you are using ?
As in the designer studio try to open any test case(or simply run a flow), then try to attach a doc by clicking on the addAttachment link. Click on cancel and you will not get this issue.
It may be a configuration issue. If you find everything is OOTB then you can raise a SR for this.
OCBC
SG
Hi,
I'm not using the OOTB control, instead using the flow action called in the pxAttachContent control i.e. pyAttachContent. We need to capture the Link-Attachment key for that particular attachment so we have configured it as such.
I agree that it's a configuration issue but not sure where it's going wrong as there are no error messages on clipboard nor any failed steps in tracer.
Thanks
OCBC
SG
Hi,
Even on using the OOTB control (pxAttachContent), I'm facing the same issue. I have configured to use the control in context of a data class repeat grid.
From my observations, the rowPage parameter that is loaded is of Work class whereas the context is of data class. So when the ProcessAction activity calls the pyAcquireObject activity, it calls it on Work context whereas if the rowPage parameter were of data class then the pyAcquireObject of @baseclass would have been invoked thus the newAssignPage would not have gotten removed as is happening in step 2 of Work-.pyAquireObject activity and the previous assignment details could have been retained.
Please state if my understanding is correct or not.
Regards,
Sovan