Document Size Validation

Jansi J said:

if there is any way to avoid saving this file in Appian folder if document size is more than 10MB

2 methods:

1. Disable the CANCEL button if there's a new file uploaded - and provide a tooltip on the cancel button asking the user to clear out the upload field first.
2. Leave the CANCEL button enabled; continue to save the uploaded document ID into the rule input it was targeted at previously, but in the CANCEL path process flow, add logic to check if there is a populated document ID, and if so, delete it.  I created a specialized system-wide utility subprocess called "Safe Delete", which checks whether the provided document ID is non-null (and actually exists) prior to trying the DELETE DOCUMENT node, as this node is NOT null-safe.

Thank you Mike,2nd method works for me and it seems better than forcing the user to remove all uploaded documents even they are planning to Cancel the flow.

I agree, depending on context.  I've used both before.  However there are some cases where, for example, a document is added to a row in an Editable Grid, where the grid rows themselves can be removed by a user, where i've taken special pains to come up with a method where the "remove row" control is disabled until the user removes the uploaded document on that row.

I agree, depending on context.  I've used both before.  However there are some cases where, for example, a document is added to a row in an Editable Grid, where the grid rows themselves can be removed by a user, where i've taken special pains to come up with a method where the "remove row" control is disabled until the user removes the uploaded document on that row.