Difference between revisions of "Seon plugin seonplugin filerename"
From Seon
(New page: == Purpose == Rename all files of an Seon job according to a specific rule. == Requirements == * File <code>/etc/seon.conf</code> or configuration file pointed to in environment variabl...) |
|||
Line 22: | Line 22: | ||
*%r: recipient partner shortname | *%r: recipient partner shortname | ||
*%s: sender partner shortname | *%s: sender partner shortname | ||
+ | *%t: recipient location name | ||
+ | *%u: recipient department name | ||
+ | *%v: recipient first name | ||
+ | *%w: recipient family name | ||
+ | *%x: recipient address code | ||
+ | *%g: sender location name | ||
+ | *%h: sender department name | ||
+ | *%i: sender first name | ||
+ | *%J: sender family name | ||
+ | *%k: sender address code | ||
+ | *%e: depending on the job direction, the company shortname of the external communication partner: | ||
+ | **incoming jobs: sender's company shortname (= "<code>%s</code>") | ||
+ | **outgoing jobs or undefined job direction: recipient's company shortname (= "<code>%r</code>") | ||
− | + | == Examples == | |
− | + | All examples are based on an Seon send job with number 76, addressed to company "c-works": | |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | == | ||
− | |||
/opt/seon/tmp/%r/seon_job_%j/ | /opt/seon/tmp/%r/seon_job_%j/ | ||
− | + | will compute to: | |
/opt/seon/tmp/c-works/seon_job_76 | /opt/seon/tmp/c-works/seon_job_76 | ||
---- | ---- | ||
/opt/seon/tmp/%D/%r/%j | /opt/seon/tmp/%D/%r/%j | ||
− | + | will compute to: | |
/opt/seon/tmp/outgoing/c-works/76 | /opt/seon/tmp/outgoing/c-works/76 | ||
---- | ---- | ||
− | + | A SWAN-like directory behaviour would be: | |
/opt/seon/data/%Y/%m/%d/%j | /opt/seon/data/%Y/%m/%d/%j | ||
− | + | which will compute to: | |
/opt/seon/data/2008/03/18/76 | /opt/seon/data/2008/03/18/76 | ||
− | == | + | == Return values == |
− | 0: | + | 0: everything OK |
− | 1: Configfile (/etc/seon.conf | + | 1: Configfile (/etc/seon.conf or value of environment variable "<code>Seon_CFGFILE</code>", read in as file) cannot be found or database unavailable. |
− | 2: | + | 2: License error |
− | 3: XML | + | 3: XML parameter file cannot be parsed |
− | 4: | + | 4: Files cannot be renamed |
Revision as of 19:24, 28 April 2014
Purpose
Rename all files of an Seon job according to a specific rule.
Requirements
- File
/etc/seon.conf
or configuration file pointed to in environment variable$Seon_CFGFILE
. Via the used configuration file, the information are retrieved used by the plugin (such as default configuration etc.).
Configuration
The target filename can be set up to contain variables. These variables are exchanged by runtime information of the Seon job, in which context the plugin is run.
The usable variables are:
- %j: job number
- %d: day of job creation (two digits)
- %m: month of job creation (two digits)
- %Y: year of job creation (four digits)
- %H: hour of job creation (two digits, 24h format)
- %M: minute of job creation (two digits)
- %S: second of job creation (two digits)
- %D: job direction: "
incoming
" or "outgoing
" - %r: recipient partner shortname
- %s: sender partner shortname
- %t: recipient location name
- %u: recipient department name
- %v: recipient first name
- %w: recipient family name
- %x: recipient address code
- %g: sender location name
- %h: sender department name
- %i: sender first name
- %J: sender family name
- %k: sender address code
- %e: depending on the job direction, the company shortname of the external communication partner:
- incoming jobs: sender's company shortname (= "
%s
") - outgoing jobs or undefined job direction: recipient's company shortname (= "
%r
")
- incoming jobs: sender's company shortname (= "
Examples
All examples are based on an Seon send job with number 76, addressed to company "c-works":
/opt/seon/tmp/%r/seon_job_%j/
will compute to:
/opt/seon/tmp/c-works/seon_job_76
/opt/seon/tmp/%D/%r/%j
will compute to:
/opt/seon/tmp/outgoing/c-works/76
A SWAN-like directory behaviour would be:
/opt/seon/data/%Y/%m/%d/%j
which will compute to:
/opt/seon/data/2008/03/18/76
Return values
0: everything OK
1: Configfile (/etc/seon.conf or value of environment variable "Seon_CFGFILE
", read in as file) cannot be found or database unavailable.
2: License error
3: XML parameter file cannot be parsed
4: Files cannot be renamed