[Eg-newdevs] Action trigger for Hemlock push notifications

[Dan Briem]

If I suggested opt-in settings aren't working, that was not my intention,
sorry about that.

I just meant that, if hemlock.push_notification_data is a string token,
that particular setting won't work as an opt-in setting, because it won't
be strictly true.

But, maybe we can use an additional boolean setting, like Michele's, as an
opt-in setting, and use hemlock.push_notification_data in the CallHTTP
template.

As for the question of whether opt-in settings work at all in active hooks,
I believe they do. I think the method with the ignore_opt_in suffix is only
used for certain situations, for example sending an email checkout receipt
from the staff client:
https://github.com/evergreen-library-system/Evergreen/commit/7e3a8e2c61f4ee24317d11d478930851671b1c1d
.

On Thu, Jan 23, 2025 at 11:46 AM Ken Cox via Eg-newdevs <
eg-newdevs at list.evergreen-ils.org> wrote:

> On Thu, Jan 23, 2025 at 11:31 AM Morgan, Michele via Eg-newdevs
> <eg-newdevs at list.evergreen-ils.org> wrote:
> > As I reported earlier, I did have success using the opt-in setting in an
> action trigger definition using the checkout.due hook.
> > The difference in my test was the value field in actor.usr_setting was
> set to the string true.
> > ...
> > So setting the value for the hemlock.push_notification_data to the
> string true should work for action triggers using passive hooks.
>
> So that explains it!  Interesting experiment, but not practical for
> this purpose, because the hemlock.push_notification_data contains the
> actual Firebase Cloud Messaging token needed to send a notification to
> a specific device.
>
> Ken
> _______________________________________________
> Eg-newdevs mailing list
> Eg-newdevs at list.evergreen-ils.org
> http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/eg-newdevs
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.evergreen-ils.org/pipermail/eg-newdevs/attachments/20250123/f489c483/attachment.htm>