Status actions
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
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
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.
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.