Posted: 22 Feb 2018 13:39 EST Last activity: 17 Sep 2018 9:13 EDT
Unable to open/download the PDF file by clicking the button again and again
We have a requirement to show the PDF by making a Conn-REST call to DocuSign and bring the PDF data from the response. After getting the response, we need to prepare the PDF and allow the user to open/download it from a button click. Here are the steps followed.
2) From the above activity, we have a call to Connect-REST and capture the PDF bytes stream from DocuSign response into a Parameter. After getting the Parameter value, we call the below java code from the same activity and the Page-Remove step.
Code is working fine when we click the button from the Review harness and PDF is opening for download. But the problem is like, if I click the same button again and again then I don't see the PDF gets generated though I see a flickering after button click. By the way we are using PRPC V7.2.2
Please suggest me a solution to resolve this issue.
***Edited by Moderator Marissa to update platform capability tags***
My application id based on mashup code and we have above script configured on one link when document is not present on server post activity execution attached end message gets shown on screen which replace current screen.
We don't want to show this message in separate tab as well like we don't want show this message at all.
Any idea what changes we can do in -- formEle.target = ""; ??
I did add the Refresh Harness but the system got hung after downloading the PDF. Tried to use the Refresh Section but no luck. Is there any other alternative to modify the java code to work as expected?
Looks like I have resolved the issue with my code but the below steps are followed.
From the section -> OnClick event, I am calling the below.
1) Refresh-Section with my above mentioned activity where I get the PDF after Conn-REST
2) Run Activity by having a single step in it. That is "Wait" method for 2 sec.
3) FinishAssignment call
With these sequence of steps, my PDF gets generated with the above java code and system waits for 2 sec to finish the process and making a harness refresh with #3 from above. Hope no performance issues with this idea. Feel free to chime in.
I am able to replicate the scenario and compared the tracers too. I found reloadSection activity is not getting called asynchronously in non-working scenario, will provide any alternate solution workaround to this shortly.