The parameters present here can be compiled by entering relevant data regarding how the action will be performed:
Identification and Appearance
Parameters: Name
Description: Name of Tivoli Integration file for identification
Parameters: English name
Description: If the previous name is given in a non-English language, insert its translated version here for the easiest multilingual recognition.
Parameters: Color
Description: Indicate the colour to display the action block in the T-Workflow Designer section.
Parameters: Description
Description: Insert a brief text explaining what the action is intended to do.
Behaviour
Concurrent processes - This parameter indicates the number of instances (by default, only one) of the current action that each Etere Data Mover server will be allowed to run contemporaneously.
NB: Etere suggests using concurrency, for example, if the current action will be used simultaneously by various T-workflows or if the source and destination count with a wide bandwidth.
Do not use media folders even if configured - If disabled (by default), the file transfer will be performed by reading the source/destination paths from the selected metadevice's media folder (i.e. etereweb path); otherwise (if enabled), it will be performed reading the paths directly from the database (i.e. media folder for the asset forms).
NB: Media folders are available only for DataMover actions that read data (i.e. files/paths) from the database (e.g. multistep copy, transcoding, etc.).
Destination metafile - Specify the method to be used for naming the metafile stored in the final destination; available methods include:
Keep source name - The metafile (file_id) will maintain the source filename.
Use asset ID as a name - The metafile (file_id) will be renamed using the asset's ID.
Use asset Code as a name - The metafile (file_id) will be renamed using the asset's Code.
Use asset Code + NewType as a name - The metafile (file_id) will be renamed, concatenating the asset's code and type (e.g., COM, NEWS, PROMO, etc.).
Generate a unique name - Enable this option to generate a metafile name using a unique name (UID).
Use rule - Press the [] button to define a custom name for the metafile. The Rules Editor determines the name to combine database fields and free text.
NB: The value of this field cannot be directly typed, but it can be copied.
DB Update
This option allows specifying how to update copied files in the database. Available options include:
Update database files after the job are complete. Ok - The file will be updated in the database once the job finishes successfully.
Update database files as soon as the job starts - The file will be updated in the database immediately after the job starts,
Never update DB files - The file won't be updated in the database.
Moreover, it will also be possible to specify the assets for which the database will be updated:
Update all assets linked to the source file - If enabled (default), the copied file will be associated with all the asset forms linked to the source file.
Enabling this option is useful; for instance, when a single file is used by multiple assets (e.g. which transmit it overlaid with different logos); in this case, every time the file is copied, the new copy will be updated across all linked assets.
If disabled, the copied file will be associated only with the asset form for which the T-workflow has been launched.
Disabling this option is useful, for instance, when a single big file (e.g. a live feed recording) is used by multiple assets which partially retrieve a smaller file from it; in this case, only the asset from which the partial retrieve has been executed will be updated.