Actions support uploading attachments from Workshop, Object Explorer, Object Views, Quiver, and Slate. Permissions to view, edit, and delete an attachment are consistent with the object to which they are uploaded. For example, if a user has view permissions to an object, they will be able to view and download attachments stored on this object. Replacing an existing attachment would require edit permissions on the object.
You can upload a single attachment or a list of attachments. To upload an attachment using Actions, follow the configuration steps for both Action types and object types.
In the parameter configuration view, select Attachment as the parameter type. Attachments can only be uploaded using attachment parameter types. The corresponding column in the object-backing dataset must be a String and the edited object property must be of type Attachment.
To upload several media files at once, select Allow multiple values. Note that support for several media files in one Action requires an additional toggle during object type configuration to Allow multiple, as described below.
In the object detail view, select Attachment as the property type. Attachments can only be uploaded to attachment property types.
To upload several media files to one property, toggle Allow multiple. In this case, the property in the object-backing dataset must be an Array.
Attachments are immediately uploaded to Foundry once they are added to an Action form. Upon form submission, permissions to view, edit, and delete an attachment are inferred from the user's permissions on the underlying object type. If form submission fails or is cancelled, the outstanding attachment is no longer directly reachable and will automatically be permanently deleted after some time. Similarly, attachments that belong to deleted objects or are no longer mapped to an object (which occurs when the corresponding property is deleted) are no longer directly reachable and will eventually automatically be permanently deleted.
Attachments are supported for both logic-backed and function-backed Actions. There is a global, fixed file size limit of 200MB.