31,026
edits
Tag: 2017 source edit |
Tag: 2017 source edit |
||
| Line 96: | Line 96: | ||
Here is a quick view of the events that cause triggers to be searched and executed. An event is characterized by the value of the code ''$action'', with the type of the object received in ''$object''. | Here is a quick view of the events that cause triggers to be searched and executed. An event is characterized by the value of the code ''$action'', with the type of the object received in ''$object''. | ||
Note: The [[Module Agenda En|Module Agenda]] and [[Module Notification]] use the table [[Table llx c action trigger]] as a list of known triggers. This | Note: The [[Module Agenda En|Module Agenda]] and [[Module Notification]] use the table [[Table llx c action trigger]] as a list of known triggers. This avoid scanning the disk for this information, but this table is just a very limited list. | ||
In general, the trigger action code begins with the name of the module followed by the character _. | In general, the trigger action code begins with the name of the module followed by the character _. | ||