Difference between revisions of "Event Refactor"
From Freeside
ZelriCacel (talk | contribs) |
(reverting spam) |
||
| (2 intermediate revisions by one other user not shown) | |||
| Line 1: | Line 1: | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
= Introduction = | = Introduction = | ||
Latest revision as of 16:08, 25 July 2009
Introduction
The event refactor is new in 1.9. Previously, collection events were simple code fragments triggered after a small number of static conditions on invoices. Now, events are a flexible series of one or more conditions that trigger an action against invoices, customers or packages.
Developers
Conditions and actions are defined as Perl classes. See FS::part_event::Condition for information on creating new conditions, and FS::part_event::Action for information on creating new actions.
