<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Dear all,</p>
<p>We are on Evergreen 3.6.4 and are trying to make the following
trigger (notification email) work. We have some other notification
emails working correctly, so I suppose we probably have something
wrong with the trigger configuration itself rather than with the
email server.<br>
</p>
<p>This notification is supposed to send an email to users who have
not returned their checked-out item(s) in time - it should send
the message one day after the due date.</p>
<p>Currently, we have the following setup:<br>
</p>
<p><b>Owning Library</b>: JAB</p>
<p><b>Name: </b>1 Day Overdue Email Notification - Jabok</p>
<p><b>Hook:</b> checkout.due</p>
<p><b>Enabled:</b> True</p>
<p><b>Processing Delay:</b> 1 day</p>
<p> <b>Processing Delay Context Field:</b> due_date</p>
<p><b>Processing Group Context Field:</b> usr</p>
<p><b>Reactor: </b>SendEmail</p>
<p><b>Validator:</b> CircIsOverdue</p>
<p><b>Granularity:</b> Daily</p>
<p><b>Max Event Validity Delay:</b> 2 days</p>
<p><b>Template:</b></p>
<p>[%- USE date -%]<br>
[%- user = target.0.usr -%]<br>
To: [%- params.recipient_email || user.email %]<br>
From: [%- params.sender_email || default_sender %]<br>
Subject: Nevracene knihy<br>
<br>
Ctenar: [% user.family_name %], [% user.first_given_name %]<br>
<br>
Dovolujeme si Vas upozornit, ze uplynula vypujcni lhuta u
nekterych vypujcentych knihovnich jednotek. Na Vasem konte zacalo
nabyvat zpozdne ve vysi 2 Kc za knihovni jednotku a den.<br>
<br>
Vypujcky s uplynulou vypujcni lhutou jiz NELZE PRODLOUZIT a proto
je nutne je prinest k vraceni do knihovny (pokud nejsou
rezervovane jinym ctenarem, je pote eventualne mozne jejich
opetovne pujceni).<br>
Dokud nebudou vraceny (a zaroven dokud nebudou zaplaceny poplatky
za zpozdne), je ctenarske konto blokovano a NENI MOZNE PRODLUZOVAT
VYPUJCNI LHUTU zadnych vypujcenych knihovnich jednotek ani
PUJCOVAT NEBO REZERVOVAT ZADNE DOKUMENTY. Je take pozastavena
moznost splneni drive zadanych rezervaci nebo blokaci.<br>
<br>
<br>
Seznam knihovnich jednotech, u kterych jiz uplynula vypujcni
lhuta: <br>
<br>
[% FOR circ IN target %]<br>
[%- copy_details =
helpers.get_copy_bib_basics(circ.target_copy.id) -%]<br>
Nazev: [% copy_details.title %]<br>
Autor: [% copy_details.author %]<br>
Carovy kon: [% circ.target_copy.barcode %]<br>
K vraceni dne: [%
date.format(helpers.format_date(circ.due_date), '%Y-%m-%d') %]<br>
<br>
<br>
[% END %]<br>
</p>
<p>All other available fields are empty in our setup.<br>
</p>
<p>Compared to 7 Day Overdue Email Notification from
<a class="moz-txt-link-freetext" href="https://demo.evergreencatalog.com/eg/staff/admin/local/action_trigger/event_definition">https://demo.evergreencatalog.com/eg/staff/admin/local/action_trigger/event_definition</a>
(which is Evergreen 3.8.0), fields Context Bib Path, Context Item
Path and Context Library Path are missing from our interface. Have
they been added to the interface in some of the more recent
Evergreen versions? Or is it something we have lost along the way
when migrating from older Evergreen versions (during the upgrade
process)? This installation of ours is actually more than a decade
old and keeps being upgraded each year...</p>
<p>Also, I have noticed that our template actually does not include:</p>
<p>Date: [%- date.format(date.now, '%a, %d %b %Y %T -0000', gmt
=> 1) %]<br>
<br>
Auto-Submitted: auto-generated</p>
<p>However, we have another one that seems to be working fine where
these two lines are also omitted...</p>
<p>The aforementioned 3.8.0 Evergreen demo also has - compared to
what we have:</p>
<p><b>Opt-In Setting Type</b>: circ.default_overdue_notices_enabled</p>
<p><b>Opt-In User</b><b> Field:</b> usr</p>
<p>What is also different is that we have a daily granularity while
the demo installation does not have any. Also, the demo server has
a longer Max Event Validity Delay - 8 days - while we only have
two (maybe two days are not sufficient in this case?).<br>
</p>
<p>(I understand that the demo server may not include the pristine
setup of this trigger as anybody could change it so - probably in
theory rather than in practice - some non-default values might
have been inserted since it was last replaced with the original
demo/default data. However, I think it may be a good starting
point for making the comparisons anyway.)<br>
</p>
<p>Does anyone have any idea what should be wrong in our
configuration? Or where else should we look (like library opening
hours, granularity values accepted by the cron job or something
else entirely)?</p>
<p>Thank you in advance for sharing any tips!</p>
<p>Linda<br>
</p>
</body>
</html>