Time-Triggered Transaction Reference

The Sterling Warehouse Management System provides a collection of time-triggered transactions, which are utilities that perform a variety of individual functions, automatically and at specific time intervals.

Time-triggered transactions perform repetitive actions on a scheduled basis, typically performing database updates, raising events, or calling APIs. In one type of transaction, monitors are designed to watch for processes or circumstances that are out of bounds and then raise alerts. Often, but not always, they retrieve tasks from the task queue or work off the pipeline.

Some transactions enable you to collect statistical data regarding the application's health. This data is collected periodically, using the value specified for the yantra.statistics.persist.interval attribute in the yfs.properties file. By default, statistics collection set to "on."

For more information about statistics persistence, see the Considerations for performance management. For more information about the specific statistics parameters used, see the applicable time-triggered transactions.

The time-triggered transactions described in this chapter are unique transactions, that may or may not be document type specific. For document specific transactions, the nomenclature helps define which unique transaction it is based on: a transaction ID is in the format Unique_Transaction_ID.Document_Type_Code. For example, the transaction ID for Purge Return is PURGE.0003, indicating that it is based on the unique transaction PURGE, for document type 0003, which is Return Order. Therefore, in order to be able to configure Purge Return, you should look for the PURGE transaction ID in this chapter, which is Order Purge.

Sterling Selling and Fulfillment Foundation provides the following types of time-triggered transactions: