Using the Filename Transfer Method unlocks additional customization and flexibility for how Creative Force interacts with your Post-Production vendor. In this article, we will take a look at the available configuration options and how they work.
Overview
When configuring an External Post-Production vendor with either FTP or Box.com as the method, there is a configuration field called 'Transfer Method' within the Transfer Settings.
Method Definitions
The available options for the Transfer Method will appear as either 'Filename Mode' or 'Legacy Mode (Metadata).'
Legacy Mode
The original system that Creative Force implemented when sending out files to post-production vendors. With this mode, Creative Force writes a Physical File ID into the asset metadata during delivery.
Then, the system monitors assets in the defined return location. When there is a match, we pull the asset back into the system, moving it forward in production.
You can learn more about this here.
Filename Mode
This is a more recently implemented mode that looks to address some of the issues studios may experience when utilizing the legacy method. With Filename Mode, Creative Force delivers the assets and then scans for the correct filenames in the defined return location.
When Filename mode is selected, additional configuration options will become available. We will cover further details about those options in the sections below.
File Return Method
The configuration option for File Return Method allows further customization of how Creative Force should verify the returned files.
Filename Only
When Creative Force checks for returned assets, the filename must be correct as per the Style Guide setup.
The specific folder it sits in is not relevant, as long as that folder is in the root file path defined in the 'Connection Settings' under 'Download Folder.'
Filename + Folder
When Creative Force checks for returned assets, the filename must be correct as per the Style Guide setup.
When Creative Force checks for returned assets, it must be in the exact file path configured in the Style Guide settings.
Changing Methods
If the vendor is currently configured to Filename Mode, it is not possible to switch to Legacy Mode. A new configuration would need to be added that utilizes Legacy instead.
However, if the vendor is currently configured in Legacy Mode, you can switch it to Filename Mode and click 'Save'.
You will see a pop-up asking for your confirmation on the action.
⚠️ Important: When switching from Legacy to Filename, productions that are currently In Progress or Rejected at External Post before the change is saved will continue following the Legacy Mode until the Workflow step is completed.
Expected Return Files List
We recommend enabling the Expected Return Files List, as this file includes all of the information that the vendor must follow to return the files successfully.
Configuration Options
Setting Field | Function |
Expected Return Files List | Control whether Creative Force will send an additional file alongside the assets. The file will contain a full list of all the files and their requirements, which Creative Force will need in order to progress forward.
|
Include Preset Specifications | When enabled, preset specifications such as DPI, Color Profile, and more will be included within the Expected Return Files list that is sent to this vendor.
Only applies to fan-out steps. |
File Format | Set the format that the created return list will be sent to the vendor as.
|
File Name - Ecomm | Set a defined naming structure for the return file list when related to Ecom productions.
|
File Name - Editorial | Set a defined naming structure for the return file list when related to Editorial productions.
|
Use tokens to insert values from properties into the file name.
Transfer Log
This option is up to the studio whether the information is relevant to be included:
Configuration Options
Setting Field | Function |
Transfer Log | Deliver an additional log file for every upload once the transfer is completed. The transfer log contains a list of all uploaded files, including their directories on the FTP server.
|
File Name - Ecomm | Set a defined naming structure for the Transfer Log when related to Ecom productions.
|
File Name - Editorial | Set a defined naming structure for the Transfer Log when related to Editorial productions.
|
How it Works
Sending to Vendor
When the External Post-Production step is triggered within the Workflow, the assets and additional return list will be sent to the vendor in the configured 'Upload' file path.
Transfer_completed.log
The log file contains a list of all sent files, including their directories on the FTP server. This file should not be returned when returning completed files
Expect_returned_files.txt
This file contains all of the information the vendor needs to know when returning files back to Creative Force.
The number of files they must return
The name of each file returned and their corresponding source files
The folder where the vendor must upload the files back
The preset specification of each image (if enabled)
If the file extension is N/A, the vendor can send any file format back
Any included reference files that were also sent to the vendor.
These do not need to be returned.
Example
With the above example, the File Return method is Filename Only, therefore, the return folder location is /Hann Fresh acc/Upload from FTP/UAT as this is the Download folder set in the vendor settings.
You can easily recognize this method as the folder path will start with a slash '/'. This means that the vendor can just send the files to the target folder 'UAT.'
If you selected the Filename plus Folder Path method, you will see the folder starts from the root folder. The return folder location in this example is All files/Hanh UAT/EU/Box 1.
Then, when returning the files, the vendor must send back the whole folder All files/Hanh UAT/EU/Box 1/Product_011122_9_Flat2_main.jpg.
Receiving from Vendor
As files are uploaded by the vendor to the FTP, Creative Force will automatically scan the folder.
The vendor can check if the files are received after uploading. If the files are mapped correctly, they will be moved to the Archived folder.
If files are not mapped correctly, they will be moved to the _CF-Invalid-files folder within the Archived.
Note: This only applies when you have the clean-up settings as Archived.
Main/Variant Duplicate Naming
There might be a scenario where you need the main images and the variants to have the same name and the same file extensions.
In the case where there is only one source file but you require different versions to be sent back, CF will use a fallback service to be able to map the files back, and the information will be shown in the Expect_returned_files.txt file.
If Not Fan-Out Step
If the current external post step is not a fan-out step, CF will use the defined naming tokens + Asset ID in the filename.
If the step is not set as the fan-out step when receiving files back, CF will not check the file extension.
As long as the filename is correct, all files will be received as expected.
If Fan-Out Step
If the current external post step is a fan-out step, CF will use naming tokens + the preset variant code in the filename.
After the External Post step is completed, the filename will be renamed according to the setup in the Style guide.