To Do Entries May Be Routed Out Of The System
A To Do type can be configured so that its entries are interfaced to another system.
For example, a given To Do type can be configured to create an Email message whenever a new To Do entry is created. The following points describe how to do this:
Define the name of the background process responsible for interfacing the new To Do entries to another system on the respective To Do type. The base package contains a batch process called F1-TDEER that can be used for most situations. This batch process invokes the External Routing algorithms defined on each entry's To Do type.
Plug in an appropriate External Routing algorithm on the respective To Do type. The logic in this type of algorithm performs the interface efforts for a specific To Do entry. For example, if an Email message should be created for a To Do entry, the logic in the algorithm would compose and send the Email message(s) for a specific To Do entry.