A File Attachment object allows users to attach/detach files to your apps. For a complete list of File Attachment object properties and their uses, see the File Attachment reference topic.
You may find when designing your app that you have a requirement that managers be able to attach files to an app in a workflow and have employees open the files, edit them, then save them back to the app directly. The easiest way to do this is by adding a File Attachment object to your app.
|
1.With an app loaded in the App Designer, expand the Advanced Inputs section of the Toolbox. 2.Drag and drop a File Attachment object onto the app. |
Depending on the workflow process, once a user opens the file attachment and makes changes, he or she may then need to delete the original attachment before attaching the new file with the changes.
An alternate method for designing your app that would let you avoid making your users have to delete the older version of the attachment before adding the new ones could be to include a table specifically for your attachments. A table can contain an attachment object column, and users can add as many rows as required. This method allows you to retain copies of each successive attachment version.
 |
Anyone with access to your app would have the ability to attach and detach files to and from the app, so you may want to manage the state of the file attachment object or the table according to workflow stage and role. For additional information see the Limiting User Access to App Fields topic. |
Return to: Laying Out an App, Designing an App
