Uploaded image for project: 'ui-inn-reach'
  1. ui-inn-reach
  2. UIINREACH-14

INN-Reach General Settings: Central Server Connection Configuration Save Form

    XMLWordPrintable

    Details

    • Template:
    • Development Team:
      Volaris

      Description

      Purpose:

      In order to integrate with an INN-Reach central server, FOLIO must store a the configurations necessary to connect to and communicate with the central server. This includes the name of the server, an optional description, the agency codes hosted by the FOLIO server (mapped to FOLIO library records), the FOLIO loan type to associate with items borrowed from other local servers in the consortium, the Central server base URL, the API key and secret for authenticating to the central server, and the API key and secret for the central server to use when communicating with FOLIO.

      User story statement(s):

      As a FOLIO administrator with permission to edit INN-Reach central server configurations, I want create, update, or delete a central server configuration INN-Reach settings, so that my FOLIO tenant can participate in the indicated INN-Reach consortium.

      Scenarios:

      1. Scenario:
        • Given the interface scenarios described in UIINREACH-13
        • When the "Create" or "Edit" screens for a central server configuration has all required fields filled
        • Then the "Save & Close" button becomes active
      2. Scenario
        • Given the previous scenario
        • When the user clicks the "Cancel" button or the "X" in the upper-left corner of the screen
        • Then a confirmation modal is presented with "Close without saving" and "Continue editing" buttons
      3. Scenario
        • Given the confirmation modal
        • When the user clicks "Continue editing"
        • Then they are returned to the in-progress form
      4. Scenario
        • Given the confirmation modal
        • When the user clicks "Close without saving"
        • Then the form is dismissed without post and the user is returned to the list pane described in UIINREACH-11
      5. Scenario
        • Given the completed form from Scenario 1
        • When the user clicks "Save & close"
        • The form is submitted to the backend API (Create: POST, Update: PUT)
      6. Scenario
        • Given the previous scenario
        • When the server returns a 200 response
        • Then a success toast appears with "Central Server configuration [created/updated] successfully" and the user is returned to the list pane from UIINREACH-11
      7. Scenario
        • Given the Scenario 5
        • When the server returns an error response (400/500 error)
        • Then an error toast is displayed with a description of the error

       

        TestRail: Results

          Attachments

            Issue Links

              Activity

                People

                Assignee:
                Unassigned Unassigned
                Reporter:
                brookstravis Brooks Travis
                Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved:

                    TestRail: Runs

                      TestRail: Cases