file upload without Form submission?

Agreed with Stewart, what do you mean by "assign them"?

The user will need to perform a Submit click - either button submit, or a!submitLink - but this does not mean that they need to "leave" their "current task"; if you set it up correctly, from their perspective, the user can stay in the exact same place and the only apparent difference is that their uploaded files will now be fully added into the system and available for whatever further use you needed.

Hi Mike, I'm also having issues with retaining in the same user task (form) after clicking on submit link to upload a file. Because I need to show the uploaded file's data in a grid before they submit the form. When you say ' if you set it up correctly' can you please give an example?

Quoting Mike:

"In general, what I was talking about above was having a User Input Task which, upon the click of a specific button or submit link, submits the task and chains immediately back into the same task for that user (performing arbitrary in-process work in between).  In the user's viewpoint, nothing will have happened other than that their file will have been uploaded / "verified"."

Do you have any additional questions?

Hi @Stefan Helzle @Chris @Mike Schmitt

- Is there a way to handle the same issue in Portals where we are planning to upload the file and use that doc in integration input without submitting the form?

There is no "submit" in portals. The documentation on portals explains how to handle this scenario.

Hi @Stefan Helzle

- Thanks for the response. We are trying to get the doc from user in portal and use that as ri for integration as mentioned below. We won't be able to do the same when the file is not available in Appian. Do you know any other option to handle this scenario?

Along with that I have checked the documentation and it is suggested to use submitUploadedFiles() function and this have same condition on working only with saveinto of Submit 

https://docs.appian.com/suite/help/23.1/fnc_system_a_submituploadedfiles.html#example

What are you missing? The docs describe, how you get a file uploaded to Appian.

But maybe that integration has a secret to it. If you share a few more details ...

We are trying to send the document as the request to the integration. If I browse and select the file from the Appian folders I will get the response as below.

If we try to use the file not available in the Appian (Like temp file uploaded in the interface but nor submitted yet), we are getting the below error. Can you let me know what information would be helpful to clarify this query?

Unknown said:

we try to use the file not available in the Appian

Is this after you call submitUploadedFiles()?  Can you share the code snippet of your portal form where you're trying to handle this and/or trying to call the above integration?  Because AFAIK there's no expectation that the file will be accessible until it's been moved to the Appian FS.

Hi Mike - Find the below code that is working which have Submit=True on the Button. This code works in the interface level as the flow won't move further even thought Submit=true. So File will be uploaded in the Appian target folder and when I call the integration with another button it is working. Is there a way we can use "submitUploadedFiles" function without submit button?

The first thing I'd be trying here is to call the integration from within the "onSuccess" parameter of the a!submitUploadedFiles function, instead of from its own button.  What happens when you try this?

Hi Mike - Tried that & not able to resolve the issue.

• If I pass the integration call in onSuccess part & submit:True for the button -> File uploaded in Appian & Integration not called
• If I pass the integration call in onSuccess part & submit: True has been commented for the button -> File not uploaded & Appian Integration not called at all
• If I pass the integration call in as 2nd saveinto part next to a!submitUploadedFiles function & submit:True for the button -> File not uploaded & Appian Integration not called

Any other suggestions on this?

The documentation seems a tad unclear on this, but I suspect having the buttonWidget marked as "submit" on the portal form is either irrelevant, or potentially harmful.  Hopefully just the former.

The different variations you listed seem like they should cover this scenario if anything will work at all.  I would note that you should definitely be testing from the Portal itself as opposed to from the interface designer (at best, both would work, but at worst, the interface designer might give misleading behavior). Sorry if this part seems obvious but you haven't specified.

Can you post the current state of your button code for, at least, the first bullet point?  I'd like to at least verify it looks like I was thinking it should look.

And can you confirm also, if you leave the two functions designated as separate buttons, that it *does* correctly perform the behavior you're after, as long as you click the two buttons in the correct sequence?