I would be happy to put a sql insert in the code for a "template" Action Trigger - but for reasons spelled out in the IRC discussion, I hesitate to edit the default action_trigger_filter.json file.
AKA { "stop_fines" : ["MAXFINES"] } needs to be { "stop_fines" : ["MAXFINES","LONGOVERDUE"] }. Someone implementing this, would/could have a separate action_trigger_filter.json config file for the cron jobs that intend to make items lost after they have already gone to longoverdue.
Cron example:
0 4 * * * . /etc/profile && /openils/bin/action_trigger_runner.pl --osrf-config /openils/conf/opensrf_core.xml --process-hooks --run-pending --custom-filters /openils/conf/action_trigger_filters_longoverdue_to_lost.json
Kathy,
I would be happy to put a sql insert in the code for a "template" Action Trigger - but for reasons spelled out in the IRC discussion, I hesitate to edit the default action_ trigger_ filter. json file.
AKA { "stop_fines" : ["MAXFINES"] } needs to be { "stop_fines" : ["MAXFINES" ,"LONGOVERDUE" ] }. Someone implementing this, would/could have a separate action_ trigger_ filter. json config file for the cron jobs that intend to make items lost after they have already gone to longoverdue. bin/action_ trigger_ runner. pl --osrf-config /openils/ conf/opensrf_ core.xml --process-hooks --run-pending --custom-filters /openils/ conf/action_ trigger_ filters_ longoverdue_ to_lost. json
Cron example:
0 4 * * * . /etc/profile && /openils/
Perhaps the documentations could bridge the gap?