Appian Community and Appian Academy are being upgraded. From July 24–August 3, the Appian Community will be in read-only mode. During this time, the site will be read-only and user registration will be disabled. We apologize for any inconvenience this may cause, but a more secure, stable, and performant Community experience is coming soon!

The new Appian Community launches August 3, followed by Appian Academy on August 7. During the migration, Appian Community Edition, Appian Academy, Documentation, Certifications, Instructor-led Customer Training, Partner Sales Training & Accreditation, and Forum (for Appian Partners and Customers only) will remain available.
  • State Not Answered
  • Replies 6 replies
  • Subscribers 5 subscribers
  • Views 9854 views
  • Users 0 members are here
Related Discussions
Home » Discussions » User Interface

Save draft Functionallity

lokeshk

Appian provides a feature to save your current data through save draft functionality, but when i try to upload a file and try to save the UI through save draft functionality, it gave me an UI expression error: "Saving a form containing files is not supported. Please remove them and try again".

So wanted to know, what other limitations are there other then file upload for SAVE DRAFT functionality.

  Discussion posts and replies are publicly visible

Parents
  • 0
    Certified Lead Developer
    Hello Lokesh,

    At this point i think others have already answered your questions I just wanted to mention the following.

    Do you really need to use the standard save draft? Keep in mind that using the standard save draft can have some drawbacks:
    - to query the information in the save draft you will need a task report. You won’t be able (easily) to query the information and make joins with the database. I personally prefer to store that saves information in the database.
    - think about the reports of the “in process information” or “on hold”. And the completed.
    - saving in draft potentially will have process instances hanging if the user does not continue with the process. In the long term maybe you should have to handle. (Add to the equation the volume and size of the process instance).
    - I can see that you might need a flag to lock just to make sure the information is not updated in the database and when you open the task again something becomes inconsistent.

    Finally the limitations as you found out and the comments that other provided

    Jose
Reply
  • 0
    Certified Lead Developer
    Hello Lokesh,

    At this point i think others have already answered your questions I just wanted to mention the following.

    Do you really need to use the standard save draft? Keep in mind that using the standard save draft can have some drawbacks:
    - to query the information in the save draft you will need a task report. You won’t be able (easily) to query the information and make joins with the database. I personally prefer to store that saves information in the database.
    - think about the reports of the “in process information” or “on hold”. And the completed.
    - saving in draft potentially will have process instances hanging if the user does not continue with the process. In the long term maybe you should have to handle. (Add to the equation the volume and size of the process instance).
    - I can see that you might need a flag to lock just to make sure the information is not updated in the database and when you open the task again something becomes inconsistent.

    Finally the limitations as you found out and the comments that other provided

    Jose
Children
No Data
© 2026 Appian. All rights reserved.
We want to hear from you! Submit a review on Gartner or G2.