Staff Slips
(UXPROD-19)
|
|
| Status: | Draft |
| Project: | UX Product |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None | Parent: | Staff Slips |
| Type: | New Feature | Priority: | TBD |
| Reporter: | Stephanie Buck | Assignee: | julie.bickle |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | staff_slip_other, staff_slips | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||
| Potential Workaround: | Refreshing the browser, or tab will result in the correct report being generated. | ||||||||
| Release: | Not Scheduled | ||||||||
| Epic Link: | Staff Slips | ||||||||
| Development Team: | None | ||||||||
| PO Rank: | 0 | ||||||||
| Rank: Cornell (Full Sum 2021): | R1 | ||||||||
| Description |
|
Current situation or problem: ** If a user runs the "Print pick slips for.. " report, having previously ran the "Print pick slips for.." report, without refreshing the page they receive the same results. It appears that the call to /circulation/pick-slips/UUID is being made when the page first loads. The report is then generated from this initial call. The desired action would be the preceding url be called again to refresh any information before the report is generated. See: API Calls on Load.jpg Since some units have FOLIO open on a dedicated supervisor station where the page may not be refreshed, this issue could result in duplicate requests being printed or requests not being printed at all. The same issue would be present at units that have very low transactions or during breaks. In scope The underlying identified is that the API call to generate the report runs once, when the page loads, rather than when the button is clicked. It was implemented this way because folks complained about the performance of generating the report on-demand when people clicked the menu item. At the time, there was a discussion about moving this to an async process, e.g. "Click this button and :magic: get notified when the report is ready for download" or "Click thus button and :magic: it will be emailed to you as an attachment". Note that we have no :magic: at present, i.e. there is no system in place that we can hang such features from; there would potentially be quite a bit if infrastructure work to do before we could even begin the feature work. Out of scope Use case(s) Proposed solution/stories Links to additional info UIREQ-661
|