-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Exports should be prepared server-side #1100
Comments
Assigned to Halcyon in the March WO. |
There appear to be a number of pages with Export XYZ buttons on them that use the existing client-side
Please confim whether the above list is correct or not |
Hi @HalcyonJAC and @JeremykJAC the following pages are the ones to optimise (and I believe covers all of them):
The following, mentioned above, are all ok as the data being converted to xlsx is already pre-generated or created server-side:
|
For now I think let's keep them as xlsx downloads. |
Thanks @warrensearle ! |
Please leave for my return on 22/03 for testing and approval for release. |
@HalcyonJAC @JeremykJAC I have tested this and found the following: • Applications - Export Contacts: I was able to export the contacts. There was no refresh button, but i'm guessing that was because it doesn't fall under reports? as is the case with QT - Responses. • Reports – Handover: Refresh button was there and I was able to download the report. • Reports - Reasonable Adjustments: Refresh button was there and I was able to download, however the report listed two people within it, while the platform only listed one candidate as having reasonable adjustments (pictures below). • Qualifying Tests – Responses: Was able to dowload the responses. There was no refresh button - as above for applications - Export Contacts. |
Hi @KateMJAC I have spent some time today trying to replicate the problem you found with the Reasonable Adjustments report, on my workstation but have not managed to. This is could be down to my lack of knowledge on the lifecycle of an exercise and system workflow. I would have called one of the developers for help but didn't want to take much of their time up. In any case I have some changes to the exports so that the export button is no longer enabled unless there is actually data to export at least, to avoid other possible errors. I will speak to one of the dev team tomorrow and see if they can help me replicate this problem locally so I can get to the bottom of it. Darrel |
Positive result during testing by Tester User Group. I also tested with a positive result. This can move to reviewed, |
#1201 Include version number in UI and Sentry #1033 FIX TypeError: Cannot read property 'shareData' of undefined #1212 S9(1) type exercise functionality (ex 35) #1100 Exports should be prepared server-side #1081 Report improvements #1224 Fix: Tabs no longer function on application view #1237 Fix: Configure npm to use github packages for JAC Kit #1242 Fix: All candidates in stages tab moved to withdrawn Exercise 014 and 010
Currently we have a number of 'Export to XLSX' buttons in admin and these are all downloading full data to the client and then transforming it into the desired XLSX format. This is clunky. Instead we should be doing this on the server-side and perhaps saving the data to Google Drive as a Google Sheet instead of allowing a direct download.
The text was updated successfully, but these errors were encountered: