Difference between revisions of "Status actions"
Jump to navigation
Jump to search
old>Admin (→Export) |
old>Admin (→Export) |
||
| Line 20: | Line 20: | ||
The target reference may contain field references in the {FIELD} format, that will be populated at runtime. | The target reference may contain field references in the {FIELD} format, that will be populated at runtime. | ||
{| | {| | ||
| Line 36: | Line 35: | ||
|- | |- | ||
|} | |} | ||
Please note that | |||
* Export actions are handled in seperate threads (performance) | |||
* There is no guarantee the operation succeds (tjeck the event log) | |||
Revision as of 20:01, 28 May 2013
Status actions
The actions are fired when a certain condition is meet
- An item enters the status
- An item leaves the status
- Time has passed while an item was in this status
Notifications
Export
The template is optional: If no template is found raw XML will be generated.
The following types of routing are supported
- Local file system (optionally a mapped share)
- Remote FTP server
- Sent by email
The target reference may contain field references in the {FIELD} format, that will be populated at runtime.
| Routing | Syntax example |
| File system | c:\exportFolder\{GROUP} |
| FTP server | ftp://username:password@acme.com/exportFolder |
| Send by mail | mailto:boss@acme.com:Attention my friend |
Please note that
- Export actions are handled in seperate threads (performance)
- There is no guarantee the operation succeds (tjeck the event log)