Understanding how to combine sub actions

Fotoware Protocol (FWP)-based sub actions

The following sub actions can be executed without downloading the assets to the local client:

• Process in Color Factory via FWP
• Apply Metadata Macro/Template
• Copy via FWP
• Move via FWP
• Check required metadata fields
• Rename file
• Attach license
• Clear licenses

These operations can all be combined without requiring the client to download the file(s) locally.

If they are combined with other sub actions, the file will be downloaded locally for additional processing. If you then want the resulting file to be stored back on the server, you need to end the sub action sequence with e.g. a Copy via FWP action to re-upload the file.

Two types of sub actions

The order in which the sub actions are performed is important for the end result. That's because FotoStation's sub actions can be divided into two separate categories. Either the sub action changes the image data (an “image processing” sub action), or it performs an operation on a file stored on the hard disk. As a rule of thumb, if a sub action is an image processing sub action, then it must be followed by either another image processing sub action, or by one of the two save sub actions.

This is because an image processing sub action alters the image in memory. If it is followed directly by a file operating sub action, for example, move or copy, there is no file to work on since the image is now in memory only. Hence, an image processing action, or a chain of image processing actions must always be followed by a save action before file operating actions are performed. Or you could perform file operating actions first, then image processing operations, and finally a save action.

When you work with a picture in Photoshop, for example, the same applies, but you really don't think about it.
For example, you need to save your changes before you can make a copy of a file or send it using an email client.

Saving the file - File format vs Save file

The two save sub actions Save file and File format both save the result of one or more image processing sub actions, but while Save file lets you choose where to save the file together with many other options, File format only lets you choose a file format before automatically saving the file to a temporary folder. File format is normally used if you perform changes to an image but only need to save the changes temporarily to be able to perform other sub actions. This may for instance be the case when making changes to an image before uploading it to a web server. After the complete chain of sub actions is complete, the temporary file created using File format will be removed. This is not the case if you used Save file, which renders a permanent file.

A chain of image processing sub actions (see the table above) must be followed by one of the two save sub actions. Note however that you don’t always need the save sub action directly after the last of these sub actions. You can perform some of the sub actions (such as the Apply text macro/template sub action) before using the save sub action.

Make sure that you understand how a sub action works before you use it. If you are not sure, see the topic regarding the sub action in question. See examples of Valid and invalid sub action chains to learn how to correctly combine sub actions in meaningful workflows.