A great feature lies tucked away in the Automate Task Builder than can make exporting and sharing tasks a whole lot easier: Attachments.

Attachments allow a file of any type to be embedded within a task so that third-party elements can be included with a task for greater portability. For example if you have a task that plays a .wav file when a certain event occurs you can guarantee the sound file will always be present on the system by attaching the file to the task.

Task attachments can be added and removed in the Task Builder's Attachment windows. Normally this window is docked together with the other Debug Windows at the bottom of the Task Builder (though like all other debug windows, it can be undocked and placed anywhere on the screen). To add an attachment, right-click inside the Attachment window, and then select Add. Browse to the file you wish to attach and then click OK. The full path to the file will be shown in the attachment window.

To remove an attachment, right-click on the attachment filename, and then select Remove. Once the task is saved, the Task Builder will attach each file in the Attachments window to the Automate task file. At runtime, these attachments are extracted and placed in the user's temporary files location.
To use an attachment in your task, use the filename (without the path) of the attachment.

For example, if you attach the sound file C:\MySounds\ScreamingBoar.wav, you would refer to this file in a Play Sound step as ScreamingBoar.wav.

Attachments can be of any type and size, but be aware that the size of the task file expands with the size and number of attachments. On average, the size of the task file will increase by twice the size of each attachment due to the MIME encoding method.

Applies To: Automate 5, Automate 6 

Still have questions? We can help. Submit a case to technical support

Last Modified On:
You don't have the appropriate permissions.
No, open a new Support Case