Angular: Patron Triggered Events Port
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
New
|
Undecided
|
Unassigned |
Bug Description
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(
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/
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?