Overview
Package file allows to collect several source files for translators and pack them to a single archive file. When you send the package for processing, source files inside will go to the translators specified.
Configure the Package File
Create a profile:
On this page
| Table of Contents |
|---|
To configure generic load profile with a package file, fill the File Mask. Specify archive package name and source file name with a slash / delimiter as shown below:
PackageName/SourceFileName
One profile can have several packages files with source files in it. Package files can be combined with source files without packages.
BundleTrigger File
It is pretty common to build workflows that launch on arrival of a specific file. In the terms of profiled workflow such file is called bundleTrigger, then the bundleTrigger arrives to NDFA stream, profiled workflow is launched.
To mark the bundleTrigger file, add tilde ~ symbol at the beginning of its File Mask field. Only one package/source file can play the role of bundleTriggerFile for each profile.
If a package marked as bundleTrigger then each row related to this package must have a tilde ~ symbol at the beginning of File Mask field:
DateRule and wildcards in file mask in profile
It is possible to add wildcards and daterules anywhere in the file mask, as shown below:
@(DATERULE) or @DATERULE – indicate a date rule
* - wildcards in file name