触发系统: Difference between revisions

<0 失败，0 没有执行任何操作，>0 成功

4) 代码开发完成后，只需在Dolibarr中触发触发事件即可进行测试。注意，函数 '''run_trigger''' 的调用被封装在事务中。如果触发器返回 KO 代码，调用函数可能会回滚事务（这取决于调用函数）。要在函数 '''run_trigger''' 中添加日志跟踪，用以确保代码运行良好。如果您愿意，可以使用函数 dol_syslog("my log message", LOG_DEBUG)；

=List of known triggers actions=

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 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 _.

=Manage and create a new trigger's action=

To manage events other than those above, you must modify the Dolibarr code to add the following sequence in the business methods of the classes of the objects handled:

It will then be possible to add in the run_trigger method of any trigger file, an if which allows you to manage this code. The run_trigger method would then be of the form: