All PPR documents are generated through the new report API #13161
Comments
RFK250
changed the title
|
@doug-lovett to add more detail |
|
Please add your planning poker estimate with Zenhub @doug-lovett |
|
Large search format example: |
|
Mail amendment and discharge verification examples:https://app.zenhub.com/files/157936592/298c7d47-faf1-4e79-b5c2-218fd35ba3f6/download |
|
Verification amendment example: |
|
Move to staging until 13860 development is complete. |
|
@doug-lovett Is that necessary? Releasing this ticket as is would still be an improvement over the status quo, would it not? i.e. we'll still see some manual file retrievals from large requests, but fewer than we're currently seeing. Am I missing something? I ask because I don't know when we'll get to 13860. |
|
@RFK250 we can move this to RFQA for the non-large reports. I was thinking that the 13860 change would go into DEV within the next few days. Release management is different for significant PPR API changes. After internal QA we release to the SANDBOX environment for at least 1 week before PROD to give the API clients an opportunity to test the change. With this change we will also run some load tests in the SANDBOX environment. |
|
@doug-lovett Okay, let's do RFQA on this ticket for the non-large reports, and we'll QA the large ones with 13860 assuming that you expect to get to it soon. That way we'll have at least partially implemented in the event we aren't able to get to 13860 soon as we hope. cc @chdivyareddy |
|
@forgeuxGH5 - tagging you here to review with Doug |
tlebedovich
assigned tlebedovich and forgeuxGH5 and unassigned tlebedovich and forgeuxGH5
|
@RFK250 - we ran out of time to review so far - if you want to move this along, we can do UXA as a separate spin off UXA ticket if you want to create a new one and leave it in this column? |
|
Thanks @tlebedovich - I'll do that, as I'd like to move it along minus the large reports. |
|
@chdivyareddy Please note: This ticket should be QA'd only for non-large reports, and UXA is still to do but there's a separate ticket #13972 for that. |
|
@doug-lovett , Quick question - When the search result is added to the table 'i' icon is displayed, can the user click on the i icon to generate PDF once it is ready? Currently, when the i icon is clicked, the 'Unable to open document' modal is displayed and only once the user reloads the dashboard, then the PDF gets generated: Is there UI work required here? Can you please take a look, thanks! |
|
@chdivyareddy nice catch. The search report generation is now identical to that of verification reports. The search completion now returns without waiting for the report generation to complete. The report request is queued and there is slight delay (in most cases) before the report is available for download. So the UI behaviour should probably be updated (and maybe the messaging) as you suggest. |
|
Ooo sounds like a good opportunity to make a tech debt ticket like we talked about at retro! :) @chdivyareddy I would do it myself except I wouldn't be sure what to include in the AC - do you mind making that ticket please? |
|
@doug-lovett Thanks for confirming:) |
|
Awesome, thanks @chdivyareddy ! :) |
|
I thought we had this handling already for ppr - I thought it was working like the registrations table with the spinner on a timer and it would check for the reports while spinning. If we need that re-spec'd I can see if I can find the old ticket. |
|
Thanks @forgeuxGH5 that's a good idea and would be helpful. |
|
@doug-lovett @chdivyareddy @forgeuxGH5 Being mindful of Kaine's attention on this right now, I still think we should aim to get non-large reports into the next release if at all possible. There's clearly an operational need to mitigate things as soon as practicable. Is there any reason we can't do that for Monday? |
|
@RFK250 We can probably get this into the next release, I'll get some examples from Doug on Monday to test various scenarios and 13980 should also be fixed to get this through. |
|
@chdivyareddy 13860 is in review but already deployed to test for unit testing. You can now test large search results > 700 registrations. Also, I reverted the dashboard search history behaviour with saving to doc storage. The first time a download is requested it is saved to doc storage. Subsequent requests will download the doc storage report. By not changing the search report request behaviour there is no impact to the direct API clients so we can get this change into PROD more quickly. |
|
@doug-lovett Sure, will take a look, thanks!! |
|
DEV: MV Serial Numbers: Sample Output of MV Serial Number: 00003526 (including similar matches) |
|
Individual Debtor searches from PROD: Sample Output of Individual Debtor search: "first": "RYAN", "second": "DANIEL", "last": "VANDAMME" https://app.zenhub.com/files/157936592/1ff16ce7-e879-453e-8a22-7124b2d09d9d/download |
|
Some business debtor searches from PROD: Sample Output of Business Debtor search: "MEDI-TRAN SERVICES (1993) LTD." (Includes similar search) https://app.zenhub.com/files/157936592/80124807-7c78-4520-b1dd-4f4a622fd683/download |
|
@forgeuxGH5 @tlebedovich , Sample outputs for the non-large reports for each category were added above from DEV. I took random examples added by Doug to verify and added checkmarks for the ones which I verified and successfully downloaded reports. Please take a look at the attached examples for UXA review or can use the BCREG0057 account in DEV to download more examples, thanks!! |
|
@doug-lovett @chdivyareddy - thanks for the examples! I just added UXA for the non-large PPR outputs into the new UXA specific ticket #13972 |
|
Moving this to RFQA since the UXA was done in ticket #13972 instead |
|
@tlebedovich , it's already in QA - you have moved it to Done 😉 Moving back to QA in progress as it is not in TEST env, thanks! |
|
hahha, oops. |
Note
Please check with Doug before taking this ticket.
AC
GIVEN I am a PPR user
WHEN I perform a PPR search (e.g. by owner name, by registration #, etc)
THEN My documents are generated via the new Report API (Gothenburg)
AND The table of contents includes page numbers and URLs
Requirements
Need to migrate these documents
Large search result report notes:
Total # of search requests in PROD: 690920
Total # over 700: 110
Total # over 1000: 48
Some of these are duplicates for failed attempts:
New large search report light format for reports containing over 700 registrations.
Performance:
843 registrations: time to generate 10:48, files size 19MB.
1333 registrations: time to generate 14:41, file size 32MB.
Note: removing page numbers and links from the TOC reduces the above time to generate significantly.
The text was updated successfully, but these errors were encountered: