Events and Event Definitions
Redwood Server is an event-driven process automation tool. This means that it is possible to start processes (or chains) using events, rather than just having them happen at a particular time. This event-driven nature makes it possible to create efficient processes that do not rely on time at all. When certain conditions are met, a Redwood Server event is raised.
An event is raised, for example, when any of the following happens:
- A process or chain completes.
- A step or process completes.
- A monitor exceeds a threshold, or drops below a threshold.
- A process takes too long to complete.
- A file raises the event.
- You raise an event manually.
Processes (and chains) can wait for one or more events to occur, and may even be automatically submitted if an event occurs. Processes (and chains) can also raise events when they complete, allowing event-driven flows to be created.
Events (like process definitions) have a definition separate from the event itself. An event definition can have zero or more actual events associate with it. The definition stores information like the name and the trigger for the individual events. Process definitions, monitors, and other objects are connected to the definitions of events that they depend upon, and the definitions of the events that they raise.
Each time an event occurs, a new event is created (or raised). Each event can then be individually monitored and managed, and remains visible as historical data even after all tasks related to the event have completed.