Uploaded image for project: 'ui-data-import'
  1. ui-data-import
  2. UIDATIMP-817

Log lite - Invoice JSON screen



    • Folijet Sprint 111, Folijet Sprint 112
    • 3
    • Folijet
    • R1 2021 Bug Fix


      Purpose: To show JSON for each invoice line that was created by an imported EDIFACT file

      As a staff person working with EDIFACT invoice data import jobs
      I want to see the JSON for all FOLIO invoice lines that were created by an incoming file
      So that I can inspect them for accuracy or errors

      NOTE: This replaces the MARC-JSON screen a user sees when they currently click an import file name in the Data Import log


      1. Scenario 1
        • Given the individual import job summary log screen for EDIFACT invoices (created in UIDATIMP-816)
        • When a User clicks the title of any row in the log
        • Then open a new browser tab with JSON for all records created or updated by the import job
      2. Scenario 2
        • Given this new JSON tab
        • When a User views it
        • Then format as follows:
          • Header
            • "Import log for record xxxxx-y (title), where xxxxx-y is the invoice and line number from the preceding log summary page and title is the title from the preceding log summary page
            • Followed by the word "Show:"
            • Followed by tabs for each of the FOLIO record types, in the same order as the record type columns on the summary page
            • And defaulted to the Invoice tab (if possible, rather than the SRS MARC Bib tab)
      3. Scenario 3
        • Given the Invoice tab
        • When viewing the details
        • Then display the Invoice line JSON for the line that was selected from the summary
        • Followed by the Invoice JSON
        • NOTE: This means all invoice lines for the same invoice will have the same Invoice JSON below the Invoice line JSON
      4. Scenario 4
        • Given the Invoice tab
        • When viewing the details for an invoice or invoice line that has an error
        • Then use the same styling and configuration as implemented in UIDATIMP-765
        • NOTE: If the error is at the invoice level, then JSON screens for all invoice lines should have the error styling and configuration
      5. Scenario 5
        • Ensure this story passes Accessibility testing
      6. Scenario 6
        • Ensure automated testing coverage for this new code is 80% plus and confirm with screenshot

      SME preference is invoice line data followed by separator followed by invoice data in the JSON screen; if that will cause problems, discuss options with Ann-Marie

      TestRail: Results


          Issue Links



                Mariia_Aloshyna Mariia Aloshyna
                abreaux Ann-Marie Breaux
                0 Vote for this issue
                3 Start watching this issue



                  TestRail: Runs

                    TestRail: Cases