Cumulus Asset Actions

Cumulus Actions simplify daily workflow needs. An Asset Action refers to a combination of certain functions and can be saved under a chosen name. Whenever you wish to perform this combination of functions, all you need to do is select the corresponding action and it will be done. An Asset Action can include three different types of functions: Processing, Packing, Delivering

Firstly, you can have the selected assets processed, then you decide whether the result of this process should be packed into one file and finally, you define where this file should be delivered. By default the delivery destination is the file system and the only packing possibility is the ZIP AssetStore.

Defining a processing module for an Action is optional. Processing modules will always produce as many files as records were selected for the Action. For processing, a list of possible modules is provided from which you can choose the module you want to use. (For descriptions of the modules, see “Asset Processor Modules” .) If you select more than one processing module for an Action, the sequence is important.

NOTE: The sequence of the processing modules must make sense. For example, having the Zip AssetProcessor as the first processing module and then using the Pixel Image Converter to produce JPEG files does not make any sense. However, doing it the other way around is fine. Then you will get one ZIP file for each selected record and each ZIP file will contain a JPEG image.

NOTE: If an Asset Action that is intended to be used at the Cumulus Web Client includes either the Pixel Image Crop Processor or the Pixel Image Template Crop Processor, make sure that this processing module is always the first in the sequence. Otherwise, the Asset Action won’t work properly.

Packing modules pack the selected assets (or the files resulting from the processing) into one file. For example: if you have selected Pixel Image Converter for processing (to produce TIFF files) and then Zip AssetProcessor for packing, the result will be TIFF files for each selected record packed in one Zip file. Another example that might sound odd but also might make sense in certain circumstances: if you have selected the Zip AssetProcessor for processing as well as for packing, the result will be Zip files for each selected record packed in one easy to handle Zip file.

NOTE: The sequence of the packing modules must make sense. For example, having the Zip AssetProcessor as the first packing module and then using the PDF Page Merge AssetProcessor does not make any sense. However, doing it the other way around is fine. Then you will get one PDF compressed into a ZIP archive.

Defining a delivering module for an Action is not optional. You have to define a delivering module for every Action.

You can also select a specific Asset Handling Set to be used for the Action. If you don’t specify one, the Asset Handling Set will be used that is defined in the User Settings of the user who uses the Action. As this Asset Handling Set might have some modules not activated that are needed for the action, we recommend selecting a certain Asset Handling Set. (We strongly recommend this for Actions that are set up to be used by different users.) The Asset Handling Set selected for an Action should be a shared one and should be available for those you want to perform the Action on. And it should correctly support the modules chosen for the Action.

You can either change existing Actions or create new ones – if you have the appropriate permissions for changing or creating Actions. There are Actions for individual use and Actions that are shared with other users. Shared Actions are displayed in italics in the list for selecting the one to be edited. You may have the right to define and customize your individual Actions only or may even have the right to edit all Actions.

PRECONDITIONS: To view and modify Asset Actions, you must have the appropriate permissions (Server Permissions > Asset Actions Permissions.)