Difference between revisions of "Status actions"
old>Admin (→Export) |
old>Admin (→Export) |
||
Line 66: | Line 66: | ||
|- | |- | ||
|Send by mail | |Send by mail | ||
|"mailto:" + email + ":" + subject + ":" + filename | |"mailto:" + [email] + ":" + [subject] + ":" + [filename] | ||
|mailto:boss@acme.com:Attention:your_2013_report | |mailto:boss@acme.com:Attention:your_2013_report | ||
|- | |- |
Revision as of 08:46, 3 September 2013
Status actions
The actions are fired when a certain condition is meet AND the item is in the parent status
- An item enters the status
- An item leaves the status
- Time has passed while an item was in this status
Timed actions
The time specified is relative to a value of the item
- Creation date
- Last change
- Last status update
- Dynamic date field
Time is specified in days and can assume both negative and positive values.
Action types
Notification
This action sends an email for one or more users.
Various options for the target email exists, including
- Raw email: Static reference
- Field value: The contents of another field
- User: A specific user in the database
The email body may contain dynamic values in the tag format {FIELD}, which will be populated with field values for the item in question.
Other tags exist to help out with values not in the item
- {LINK}
- {NOLINK}
If neither {LINK} nor {NOLINK} is found within the email body, the link for item will be appended to the bottom of the email.
If no interface is chosen, a normal show link for the item will be generated. Otherwise a token link will be generated, requiring the interface to be of the type UPDATE.
Task create
This will dynamically create new tasks for any 'Task list' fields found in the solution.
Codeunit
This action triggers the execution of a special codeunit: Codeunit/Statusaction.
Except for timed actions you would implement this inside a Codeunit/Formevents.
Export
The template is optional: If no template is found raw XML will be generated (FTP/mailto will not work).
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 | Syntax example |
File system | local filesystem path | c:\exportFolder\{GROUP}\{TITLE}.docx |
FTP server | ftp connection string | ftp://username:password@acme.com/exportFolder |
Send by mail | "mailto:" + [email] + ":" + [subject] + ":" + [filename] | mailto:boss@acme.com:Attention:your_2013_report |
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.