Difference between revisions of "Status actions"
Jump to navigation
Jump to search
old>Admin |
old>Admin |
||
| Line 4: | Line 4: | ||
* An item leaves the status | * An item leaves the status | ||
* Time has passed while an item was in this status | * Time has passed while an item was in this status | ||
=== Timed actions === | |||
** Creation | ** Creation | ||
** Last change | ** Last change | ||
** Last status update | ** Last status update | ||
** Dynamic '''date field''' | ** Dynamic '''date field''' | ||
== Action types == | |||
=== Notification === | === Notification === | ||
Revision as of 20:05, 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
Timed actions
- Creation
- Last change
- Last status update
- Dynamic date field
Action types
Notification
Task create
Codeunit
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}\{TITLE}.docx |
| FTP server | ftp://username:password@acme.com/exportFolder |
| Send by mail | mailto:boss@acme.com:Attention |
Please note that
- Export actions are handled in seperate threads (performance)
- There is no guarantee the operation succeds (tjeck the event log)