...
| Category | Import, Export |
|---|---|
Purpose | Enables integration of other systems via hotfolder, with the same conventions another translation management system offers itintroduced to the translation industry (not to be named for compliance reasons) |
Bootstrap Class | - |
| Type | Plug-in |
Description
A translate5 plug-in that is able to watch a hotfolder for tasks, that should be created in translate5 - and re-exported to the hotfolder, once they are ready.
...
The list of files and reference files in the instruction.xml must be complete, otherwise there is a process error, which cannot be fixed by translate5, but must be fixed by the client. Therefore all files listed in the instruction.xml must be processed by the connector - not more and not less.
Folder structure
Each hotfolder contains three folders:
...
|_D_DFPD_INST_7_en_GB.xml
Instruction.xml
The information in the instruction.xml is evaluated as explained in the attached instruction.xml file.
...
| View file | ||||
|---|---|---|---|---|
|
API point for manual start
Users with role api have right to manually start processing.
...
| Param name | Values | Description |
|---|---|---|
none | - | If no params provided - all clients and default configs will be processed |
defaultOnly | true|false | Only default config will be processed |
clientIds | integer[] | Comma separated client ids. Only provided client ids will be processed (if some present of course) |
Configuration
| Config name | Values | Default | Description |
|---|---|---|---|
runtimeOptions.plugins.AcrossHotfolder.defaultPM | integer | Default user to be assigned as PM for Hotfolder-projects | |
runtimeOptions.plugins.AcrossHotfolder.filesystemConfig | map | [] | Filesystem config for Hotfolder project import |
runtimeOptions.plugins.AcrossHotfolder.enableAutoExport | bool | true | Choose if finished task should be automatically uploaded into client's filesystem |
FilesystemConfig explanation
Default config in Preferences→System configuration always checked
...