Document Viewer

In the 23.2 version, you can use a!submitUploadedFiles() in the saveInto of fileUpload field to save the files in target folder and then use document viewer to show the file beneath.

If you are below 23.2 then the only way to show the uploaded file is to submit the task/form and loop the UIT to itself.

In the 23.2 version, you can use a!submitUploadedFiles() in the saveInto of fileUpload field to save the files in target folder and then use document viewer to show the file beneath.

If you are below 23.2 then the only way to show the uploaded file is to submit the task/form and loop the UIT to itself.

Mines is 23.1 , i can't able to catch wt u said loop UIT itself,  You are saying like after submiting task again connect the outward connector to same task? with chaining

Yes, but add an XOR gateway in between with a condition when viewDocument flag comes true from interface then only go back to UIT o/w continue the flow.

Unknown said:

In the 23.2 version, you can use a!submitUploadedFiles() in the saveInto of fileUpload field

I've already built myself a test interface to test the FULL extent of this new feature and i'll admit, so far it's pretty powerful.  I would note, anyone wishing to take advantage of it in this way, should DEFINITELY be implementing "document removal cleanup", which works seamlessly but needs attentive coding within the saveInto's of the FileUploadField.  I can provide my example code if anyone's curious.

I do note, also, that using the a!submitUploadedFiles() function immediately in this manner, results in the "fileNames" parameter having no effect, which is... strange.  I assume it's just an un-caught bug.  To test, I compared this behavior against an identical setup, except the "submit uploaded" functionality is in a nearby button instead, which results in the "fileNames" parameter having its normal effect (i.e. a manually-overridden filename being saved in place of the original name of the uploaded document).  Not that I used that parameter very often, anyway...