Difference between revisions of "Status actions"

From TempusServa wiki
Jump to navigation Jump to search
old>Admin
old>Admin
Line 52: Line 52:
* Sent by email
* Sent by email


Please note that export actions are handled in seperate threads (performance), and there is no guarantee the operation succeds (tjeck the event log)
==== Values from record ====
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.


==== Values from record ====
Other special tags include
Other special tags include
* {SagID}
* {SagID}
Line 62: Line 64:




==== Usage exmples ====
==== Usage examples ====


{|
{|
Line 82: Line 84:
|-
|-
|}
|}
Please note that
* Export actions are handled in seperate threads (performance)
* There is no guarantee the operation succeds (tjeck the event log)


=== Shift status ===
=== Shift status ===

Revision as of 07:15, 22 February 2017

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.

The record resume has a special {RESUME} tag

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

Please note that export actions are handled in seperate threads (performance), and there is no guarantee the operation succeds (tjeck the event log)

Values from record

The target reference may contain field references in the {FIELD} format, that will be populated at runtime.

Other special tags include

  • {SagID}
  • {DataID}
  • {Resume}
  • {NanoTime}


Usage examples

Routing Syntax Syntax example
File system local filesystem path c:\exportFolder\{GROUP}\{TITLE}.docx
FTP server ftp location and connection string ftp://username:password@acme.com/exportFolder
Send by mail "mailto:"+[email]+":"+[subject]+":"+[filename] mailto:boss@acme.com:Attention:your_2013_report

Shift status

A status merely changes the status to a new value.

This type of action only makes sense to use in timed actions.