Difference between revisions of "Status actions"
Jump to navigation
Jump to search
old>Admin (→Export) |
old>Admin |
||
Line 53: | Line 53: | ||
=== Shift status === | === Shift status === | ||
A status merely changes the status to a new value. | |||
This type of action only makes sense to use in timed actions. |
Revision as of 20:12, 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 for template based exports
- 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)
Shift status
A status merely changes the status to a new value.
This type of action only makes sense to use in timed actions.