LP#1779920 - Autorenewal Feature-Release Docs

Summary release notes for Autorenewal

Signed-off by: Cesar Velez <cesar.velez@equinoxinitiative.org>
Signed-off-by: Bill Erickson <berickxx@gmail.com>
Signed-off-by: Galen Charlton <gmc@equinoxinitiative.org>

diff --git a/docs/RELEASE_NOTES_NEXT/Circulation/Autorenewal_Feature.adoc b/docs/RELEASE_NOTES_NEXT/Circulation/Autorenewal_Feature.adoc
new file mode 100644 (file)
index 0000000..b620830
--- /dev/null
+++ b/docs/RELEASE_NOTES_NEXT/Circulation/Autorenewal_Feature.adoc
@@ -0,0 +1,9 @@
+Autorenewal Feature
+^^^^^^^^^^^^^^^^^^^
+Two new action triggers have been added to Evergreen that permit the Auto-Renew feature. They can be found, configured, and enabled in Administration>Local Administration>Notifications/Action Triggers. They are named **Autorenew** and **AutorenewNotify**.
+
+The **Autorenew** A/T definition uses the `checkout.due` hook to automatically validate and renew (in the reactor) circulations on the day they are due, grouped by user. The output events of this definition is is the input used by the related **AutorenewNotify** A/T that simply uses a new hook called `autorenewal` to notify patrons via email of their currently due or auto-renewed items.
+
+Circulation policies in Evergreen can now be configured to automatically renew certain items checked out on patron accounts. Circulations will be renewed automatically up to a custom limit (the `max_auto_renewal` field) and patrons will not need to log in to their OPAC accounts or ask library staff to manually renew materials.
+
+In the webstaff's Patron Items Out page, the new column `AutoRenewalsRemaining` indicates how many autorenewals are available for a particular circulation.