You can set up automations in Clarus WMS to automatically create and upload files to an SFTP account whenever stock is transferred. This generates dynamic files with relevant event data.
Go to the automations section in Clarus WMS and begin creating a new automation.
Set the automation's trigger event to ""Stock is Transferred To Account"". Choose the specific conditions you want this event to trigger upon, such as transfers from a certain account, to a certain account, or within a specific warehouse.
Select the ""Create a File and Upload to FTP"" option. Then, specify the following:
File Name: Enter the name for the file that will be created.
FTP User: Choose the FTP account where the file will be uploaded.
Document Category: Specify the document category the file relates to (e.g., dispatch).
Mapping Group ID: If you want the file to use mappings from a specific mapping group, select it here.
In the Template File box, upload the template that will be used when stock is transferred. This template can be in standard formats like CSV or TXT.
REMEMBER: You can include dynamic data in your template using placeholders for specific information related to the stock transfer.
The key dynamic data objects available are transaction_source and transaction_target. These relate to the transactional data from the stock movement from and to an account.
Both objects include data such as:
id description boolean1 to boolean5 category created_at (and formatted versions) datetime1 to datetime5 (and formatted versions) integer1 to integer5 fifo_date string1 to string5 subtype quantity hold_notes height unit_of_measure account (with id, code, name, and external_system_references) warehouse (with code, name, and external_system_references) product (with id, code, description, product codes, long_description, external_system_references, specific_gravity, and unit_dimensions) goods_in_receipt (with id, reference, dates, notes, and related details like trailer, supplier, carrier, and address) goods_in_receipt_line (with quantities and references) reason_code (with code, name, and external_system_references) storage_unit_from (with reference) storage_unit_to (with reference) location_from (with code) location_to (with code) completing_user (with name and email)
For example, to output the account code of the account the stock was transferred to, use the following variable syntax in your template file: {{transaction_target.account.code}}
Review the Automation Setup: Make sure all fields are filled in correctly, including the file name, FTP user, and template data.
Save the Automation: Once everything is complete, save the automation. It will now automatically create files when stock is transferred, using your chosen template and dynamic data.
Common formats such as CSV and TXT are supported.
Dynamic data refers to placeholders within the template that will be filled with relevant, event-specific information when the automation runs.
No, each automation setup allows you to specify only one FTP user.
The file will not be created unless the specific criteria you set are met.
Yes, you can use dynamic data to include event-specific information in the file name.