Question

`a!submitUploadedFiles() cannot be evaluated in Process Start Form - Any workaround?

Forum|Forum|13 days ago
July 21, 2026
5 replies
0 views

Hi Everyone,

I have a requirement where a user clicks a notification, and before opening the Summary page, I need to mark the notification as Read.

To achieve this, I created a Process Model Start Form that updates the notification status and then displays the same Summary UI.

The issue is that the Summary UI contains an email section with a File Upload field. When the user clicks Send Email, I call:

a!submitUploadedFiles(
  documents: local!attachments
)

This works correctly when the Summary UI is opened from the Record Summary page, but when it is opened through the Process Start Form, I get the following error:

a!submitUploadedFiles() cannot be evaluated in this environment

I understand that a!submitUploadedFiles() is not supported in a Process Start Form.

Has anyone implemented a similar requirement? What is the recommended approach complete it

Would creating a separate interface or dialog just for file uploads be the recommended approach, or is there a better Appian design pattern for this scenario?

Thanks in advance!

stefanhelzle0001

I have a requirement where a user clicks a notification, and before opening the Summary page, I need to mark the notification as Read.

I do not understand what this has to do with sending an email and uploading a file.

In a process start for, to upload a file, you MUST submit the form. a!submitUploadedFiles() is ONLY made for Appian portals.

R

rajeshp7374Author

There is a requirement where notifications are generated for users based on specific business conditions. When a logged-in user reviews a notification, they are expected to take action on it.

To achieve this, we implemented a View button. When the user clicks View, they are redirected to the Summary page, and at the same time the notification is marked as Read. From the Summary page, the user can navigate to the Send Email functionality to respond to the notification.

However, the Send Email interface uses a!submitUploadedFiles(). When the user clicks the Send button, a!submitUploadedFiles() throws an error because the navigation to the Summary page is performed through a process model. The process model first executes a Write Records node to update the notification status and then redirects the user to the Summary page.

As a result, the interface context required by a!submitUploadedFiles() is lost, causing the function to fail when the user attempts to send the email.

After Clicking on send button getting error : An error occurred while executing a save: Expression evaluation error: a!submitUploadedFiles() cannot be evaluated in this environment.

Note: The Notification screen and the Email screen are attached for reference.

mikes0011

Brainy

What is the exact reason you have this implemented within a PM Start Form? I'm not quite sure I understand your overall process flow design in question. That said, there is almost always a way to seamlessly submit a form when a user clicks some button or link, perform the functionality you required the form submission for, then proceed on to whatever else you wanted to do anyway. This can involve subsequent chained user input tasks in the process model that had the start form.

Sign up

Login with SSO

Login to the community

Login with SSO