Traditionally, trigger events define the transition of some entity from one state to another. The status of a scheduled activity describes where that activity is in its life cycle. Therefore, a status in a scheduling interface transaction is only truly meaningful if the transaction was generated by the application assigning or maintaining that status. This chapter defines two kinds of reasons used with transactions . The second is an event reason that describes why a particular trigger event has been generated.
Reasons tend to be static, whereas statuses tend to change.
In contrast, trigger events describe an action to be performed. Appointment reasons tend to be relatively static for the life of the scheduled activity. Event reasons are static as well, but only for the life of a particular trigger event. This information tends to be administrative in nature.