LogoLogo
  • 🏃‍♀️ Get started
    • Create your first integration
      • Step 1 - Creating your Source & Destination System keys
        • Shopify Key
        • FTP Key
      • Step 2 - Select a Source Function
      • Step 3 - Select a Destination Function
      • Step 4 - Select a Transformation
      • Step 5 - Put it all together to create a Stream
      • Step 6 - Run your stream
    • Go-live best practice
  • 🏄🏻‍♀️ Integration Tutorials
    • Shopify with Descartes Peoplevox
    • Shopify with FTP
      • Shopify with FTP
      • Shopify with FTP (Part 2)
    • Shopify with ReBOUND
    • WooCommerce
      • WooCommerce with FTP
    • NetSuite
  • 🏗️ Creating streams
    • Intro
    • Streams
      • Web hook installation
      • Web hook support
        • DEAR Systems
        • Descartes Peoplevox
        • Shopify
    • Systems
      • System library
        • DEAR Systems
        • Email
        • FTP
        • Descartes Peoplevox
        • Magento 1.x
        • Magento 2.x
        • ParcelLab
        • ReBOUND
        • Shopify
        • WooCommerce
    • Keys
      • Key library
        • Shopify private apps
        • Netsuite
        • FTP and sFTP
        • oAuth
    • Sources
    • Transformations
      • Public Transformations
      • Private Transformations
      • Customising a Public Transformation
      • Write a custom transformation
        • Transformation Library
        • Example 1 - Sales Order
        • Example 2 - Shipment
    • Destinations
      • Aggregated Events
    • Data uploads
    • Lookup table
  • 🔧 Editing streams
    • Updating source and destinations
    • Deleting a stream
  • 🎛️ Monitoring streams
    • Job Statuses
    • Event Statuses
    • Resending data
      • Replicate Job
      • Replicate Event
      • Replicate Event without Event in Control Panel
    • Reporting
      • Jobs
      • Events
      • Entities
    • Alerts
  • ⚙️ Administration
    • Login and security
      • Two factor authentication (2FA) setup
        • Signup to HighCohesion without QR scan
    • Creating an organisation
    • Billing Information
    • Creating a user
    • Roles & Permissions
  • 💁🏽 Help and support
    • Glossary of platform terminology
    • Security standards
    • Data retention policy
    • Contact us
Powered by GitBook
On this page
  • What is a Destination Function?
  • Configure your Destination Function

Was this helpful?

  1. 🏃‍♀️ Get started
  2. Create your first integration

Step 3 - Select a Destination Function

What is a Destination Function?

The Destination Function decides what data should be posted to the Destination system and when.

Configure your Destination Function

Through the Control Panel you can easily access the page "Destinations" in the left side column. When entering the Destination page you will see a list of all Public Destinations, as well as your Private ones.

If you want to configure a Destination, you can do so by clicking the "Create Destination" button. From the Create Destination page you should fill in the below fields.

  • Title - Give the Destination function a title that is relative to the Destination, for example: "FTP POST Orders" or "GBP Orders to FTP"

For this example, choose FTP POST Orders Test

  • System - this is your Destination system (e.g. the System you are posting data to)

For this example, choose FTP

  • Function - this is your Destination function (e.g. the configuration of what information you will post to the system)

For this example, choose PostFiles

  • Key - This is a dropdown list of the keys you have added to HighCohesion. Please select the key for the Destination system as enabled in Step 1

  • Trigger - The Trigger defines the logic for when the Destination function should be triggered. You can choose from three pre-defined options:

    • Aggregate (e.g. the Destination is triggered when all events for a specific Job has been completed). This is well suited for the cases when you want all Events to get posted to your Destination system as one file

    • Real time (e.g. the Destination is triggered when the first Event for a specific Job has been completed). This is well used for Streams with Sources run on webhooks, to directly POST a file to the destination System.

    • Scheduled (e.g. the Destination is triggered based on your defined Cron Schedule). This is rarely used, but could be used for Destination systems that require that Files are POSTED at a specific time.

For this example, please select Aggregate

formatting = "xml"
filename_format = "orders_##DATETIMEFORMAT__Ymd_H-i-s__##.xml"
remote_path = ""
root_attribute = "version=1.0"
root_element = "root_order"
PreviousStep 2 - Select a Source FunctionNextStep 4 - Select a Transformation

Last updated 4 years ago

Was this helpful?

Settings - this is necessary to provide additional details such as the the FTP location paths, access rights etc. All of the settings added to Destination configurations should be entered in TOML format, this makes the settings easy to read, edit and update. For a guide on TOML format please see the link: .

The below settings states that the destination system format is XML, defines the output file naming convention, instructs the system of where to look for files on the remote location and indicates the root XML element. For this use case, please add the remote_path to your test FTP location. For more FTP configurations, see

https://github.com/toml-lang/toml
here