Create a File System Input


File system Connection types:

  • DropBox
  • FTP
  • Local File System
  • S3
  • SSH 

fCreate an Input for File System Data in Hero_Flow

  1. Open Hero_Flow.
  2. Click Inputs from the menu on the left.
  3. Click Create New Input.

  4. Enter a name for the File System Input and select a File System Connection from the drop-down list.
  5. Configure the File System Input data.

    CSV Files

    • Enter the file path to the data.
    • Enter a descriptive field name for the names of the files.
    • Select if data should be pulled from the last check point.
      • Yes - pulls data modified after the previous run of the Flow.

        Checkpointing accounts for file modification data and is stored on a per Flow basis.

      • No - pulls all data.
    • Select a file type: CSV
    • Enter the delimiter that separates values in the file.
    • Check the radio button to indicate if headers are present. (Yes, No)
    • If headers are present, check the radio button if the headers should be:
      • Upper case
      • Lower case
      • The original format
    • Select the character set for the CSV 
    • Select the field detection strategy:
      • Detect types - Hero_Flow automatically detects the data types for each field.
      • Convert to String - All fields are set to the String data type.
    • Click the Refresh icon to display field mapping for the Input.
    • From the field mapping table:
      • Confirm or change column names.
      • Confirm or change column data types.
        • Values of fields that have a Date_Time data type require the following format: yyyy-MM-dd HH:mm:ss
      • Remove or confirm the arrangement of columns.
    • Click OK.


    Binary Files

    • Enter the file path to the data.
    • Enter a descriptive field name for the names of the files.
    • Select if data should be pulled from the last check point.
      • Yes - pulls data modified after the previous run of the Flow.

        Checkpointing accounts for file modification data and is stored on a per Flow basis.

      • No - pulls all data.
    • Select a file type: Binary
    • From the field mapping table:
      • Confirm or change column names.
      • Confirm or change column data types.
      • Confirm arrange the order of columns.
    • Click OK.


    JSON Files

    • Enter the file path to the data.
    • Enter a descriptive field name for the names of the files.
    • Select if data should be pulled from the last check point.
      • Yes - pulls data modified after the previous run of the Flow.

        Checkpointing accounts for file modification data and is stored on a per Flow basis.

      • No - pulls all data.
    • Select a file type: JSON
    • Click the Refresh icon to display field mapping for the Input.
    • From the field mapping table:
      • Confirm or change column names.
      • Confirm or change column data types.
      • Remove or confirm the arrangement of columns.
    • Click OK.


    Log Files

    • Enter the file path to the data.
    • Enter a descriptive field name for the names of the files.
    • Select if data should be pulled from the last check point.
      • Yes - pulls data modified after the previous run of the Flow.

        Checkpointing accounts for file modification data and is stored on a per Flow basis.

      • No - pulls all data.
    • Select a file type: LOG
    • Enter the log format.
    • Enter the timestamp format. (Example: HH:mm:ss.SSSS)
    • Enter a filter expression.
    • Check the box allow log tailing.
    • Click the Refresh icon to display field mapping for the Input.
    • From the field mapping table:
      • Confirm or change column names.
      • Confirm or change column data types.
      • Remove or confirm the arrange the order of columns.
    • Click OK.