Overdue Log

Every overdue process has a log holding its history. Entries are added to the log when meaningful events occur, for example:

• When the process is created, a log entry is created to describe why the process was started.

• When an overdue event is activated, a log entry is created. These entries frequently contain a foreign key to the object that the event created so that users can easily drill down to the object from the log. For example, if an event creates a To Do entry, the To Do entry's foreign key is placed on the log and this allows a user to drill down on the log entry to see the To Do entry.

• When a process is canceled, a log entry is created to describe the circumstances of the cancellation (e.g., manual versus automated).

• Users can manually add log entries (you might want to think of these as "diary" entries) as desired.

Many of the base-product algorithms involved in overdue processing insert log entries so that a thorough audit trail is maintained. These algorithms have been designed to allow you to control the verbiage in each log entry by defining the desired message number using an algorithm parameter.

The log is viewable on the Overdue Process - Log page.