Activity Chaining Not Working the second time of upload a file (File Upload in a GridLayout)

riang over 7 years ago

Hi,

I'd like to ask what are the possible reasons why chaining won't work? and what could fix this issue.

I have this process which has subprocesses that parses contents of excel file.
I uploaded first the excel file (using fileupload in a gridlayout) then click "Import Excel File" button.
This button skips validation and in submits the form then the process will get the file uploaded and parsed.
Once it is parsed it goes back automatically(activity chained) to the form where it initially came from.
The problem is the second time of uploading (removed the previously uploaded file and uploading new file) it won't automatically go back to the form.
The activity chaining won't work. I tried other scenario, wherein the previous file is retained then clicked "Import Excel File" button but still won't return to the form.
There are no asynchronous proces...

Discussion posts and replies are publicly visible

Parents

0 riang over 7 years ago

@rodgraham yes, that's what I'm expecting too. But based from what happened, it seems that it's counting the previous nodes executed even after returning it to the user input task. I attached the screenshot, In there, you can see the blue lines, which has been first executed (parse excel) then the green line is the 2nd execution(delete attachment), the red line represents that this node has been executed in both execution (parse excel, then delete attachment). As per my understanding, I counted the subprocesses for save data and generate memo(both synchronous and activity chained) plus the other nodes in deleting attachment, and it's not reaching 50 times...but what happened is, it's closing automatically and chaining seems to break. Below is the log I found:
--> 2017-01-20 00:24:26 [PX011] {pe420.kdb ,310655} (Default) WARN .a.p.PROCESS.i "[P268437469-ICMS Generate Memo] [Activity Chaining] Could not chain to attended activity. Limit of 50 unattended nodes executed was reached."
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 riang over 7 years ago

@rodgraham yes, that's what I'm expecting too. But based from what happened, it seems that it's counting the previous nodes executed even after returning it to the user input task. I attached the screenshot, In there, you can see the blue lines, which has been first executed (parse excel) then the green line is the 2nd execution(delete attachment), the red line represents that this node has been executed in both execution (parse excel, then delete attachment). As per my understanding, I counted the subprocesses for save data and generate memo(both synchronous and activity chained) plus the other nodes in deleting attachment, and it's not reaching 50 times...but what happened is, it's closing automatically and chaining seems to break. Below is the log I found:
--> 2017-01-20 00:24:26 [PX011] {pe420.kdb ,310655} (Default) WARN .a.p.PROCESS.i "[P268437469-ICMS Generate Memo] [Activity Chaining] Could not chain to attended activity. Limit of 50 unattended nodes executed was reached."
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

No Data