Angular: Patron Triggered Events Port

[Kyle Huckins]

Evergreen: master

We’ll be porting the Triggered Events sub-UI from the Patron Interface to Angular. Triggered Events refers to the IDL class “atul,” short for Action Trigger User Log. The data being collected comes from multiple sources: Action Trigger Event Definitions(atevdef), Action Trigger Event(atev), Targeted Circs(targ_circ), and Action Trigger Hooks(ath); There isn’t a separate table soley for the User Log to draw from.

This UI is a Grid UI with robust filtering options. It has the ability to Reset, Cancel, and Print(all and selected) Events. Reset and Cancel are API calls, and the Print functionality will likely piggyback off of existing printing functionality such as Hatch. We’ll need to create our own data for events.

This UI is also used in Item Details.

The original code lives in /home/opensrf/Evergreen/Open-ILS/src/templates/actor/user/event_log

[Galen Charlton (gmc)]

Since the overall patron app that the Dojo triggered events page is embedded in is currently AngularJS, are you contemplating that the new Angular triggered events page would also be embedded via an iframe? Or would the Triggered Events / Notifications menu item on the patron app just open a new tab?

[Kyle Huckins (khuckins)]

My team set this aside for the moment after some discussion with regards to just that. There are two DOJO UIs present in the Patron interface, and we initially considered using an iframe, but the caveat being that there may be a need for refactoring once the Patron interface is converted to Angular. We felt it may be worth holding off until an Angular Patron interface is in progress.

[Andrea Neiman (aneiman)]

Marking this as a duplicate of bug 1207533 since part of that work includes angularizing this interface.