When you say "incorrect / corrupted Excel sheet", what do you mean? Is this the wrong file type? Or some other error? What information does this display in the tomcat-stdout log? What troubleshooting steps have you tried?

Hi Peter Lewis,

This is part of Vulnerability Assessment (VA) testing. VA testing team is uploading this file from third party tool like Postman directly to our Appian application. 

File Type is XLSX only.
Content is changed inside of file.

When we download the file from Appian folder and tries to open it will pop up message as shown in below screenshot:

For this kind of files, while readexcelsheet() function is trying to read giving expression evaluation error. Is there any way to catch this expression evaluation error when readexcelsheet() function fails to read corrupted files?

So wait - it's obviously an invalid / dummy excel document - and you're wanting it to do something other than throwing an error message when you try using an excel-specific reading function on it?  How's that now?

BTW in admin console you have the option to disable the upload of file types that don't match their detected underlying document type (i.e. you can't just rename a potentially harmful file to ".xslx" and get it to upload) - i'd suggest you look into that option.

Yes Mike Schmitt,

In Admin console we have already enabled whitelisting of excel file extensions (xls xlsx) to allow along with content type check. But if excel file is corrupt then we are getting this pink error and we want to handle that error.
Is there any way to handle the expression evaluation error in Appian?

Regards,
Sandeep

Yes Mike Schmitt,

In Admin console we have already enabled whitelisting of excel file extensions (xls xlsx) to allow along with content type check. But if excel file is corrupt then we are getting this pink error and we want to handle that error.
Is there any way to handle the expression evaluation error in Appian?

Regards,
Sandeep

Sandeep said:

Is there any way to handle the expression evaluation error in Appian?

You could set up a process model that tries running the rule in a script task, with a parallel flow that waits 30 seconds and then proceeds anyway if the script task got stuck, and in this case you could presume that the script task failed.  If the script task succeeds, proceed immediately to a Terminate node to shut down the timer node.