RoboFlowHelp.1.04
!!! warning "Legacy Documentation" This page contains documentation for the original RoboFlow application. Some features described here may not exist in the new Damtoolkit WAP interface.
RoboFlow Workflow Templates
| Name | Type | Meaning | Execution order of action sets | Start event* |
| Process content of a hot folder | hotfolder | Monitor a file system folder and act on newly dropped files. Typically, files are moved to the asset store location (or another folder) and cataloged afterwards. At the end of the workflow, the file is removed from the monitored folder. | files | timer |
| Process list of records | hotcollection | Process a list of records with arbitrary actions like updating metadata, generating reports or performing asset actions. | records | timer, trigger |
| Synchronize files from folder with FTP site | syncfolder-synchronize-with-FTP | Files dropped in a local folder can be uploaded to an FTP-server (recreating the local folder-structure). Or, this workflow can work the other way around, downloading files from an FTP-server and saving them in a local folder. | files | timer |
| Process list of categories | watchcategories | Process a list of categories with arbitrary actions like updating metadata, generating reports or retrieving contained assets. Optionally the records assigned to the processed categories can also be processed. | categories, records | timer, trigger |
| Synchronize changes on file system with Cumulus catalog | watchfolder | Synchronize the content of a folder (and subfolders) with a Cumulus catalog. New files are cataloged, records of modified, moved or renamed files are updated. Records of removed files are removed. | files, records, categories | timer, trigger |
| Process result of SQL query | watchsql | Process result of an SQL query with arbitrary actions like updating a record, category or catalog. | SQL result records, records | timer |
* Besides the start events listed, each workflow type can be triggered by a previous workflow.