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

Data import settings page's 3rd pane for Field Mapping Profiles: +New Action

    XMLWordPrintable

    Details

    • Template:
    • Sprint:
      EPAM BatchLoader Sprint 21
    • Story Points:
      3
    • Development Team:
      Folijet

      Description

      Purpose: To be able to create new settings for handling various types of Field mapping profiles.

      As a staff person
      I want to be able to create Field mapping profiles that define what mappings will be used to translate incoming records to FOLIO records, for the Data Import app
      So that I can associate those Field mapping profiles with Action profiles

      Scenarios

      1. Scenario 1
        • Given the Data Import Settings Field mapping profiles
        • When a User clicks the New button in the third pane
        • Then the New Field mapping profile screen should open
      2. Scenario 2
        • Given the New Field mapping profile screen
        • When a User views the screen with no edits
        • Then it should appear like this (based loosely on the attached 81c-Settings Field mapping profiles 4th pane.png)
          • Header: New field mapping profile
          • "Save" button at the top right of the header, which is white until data has been filled in, then turns to blue once the screen is dirty (has some data in it)
          • Top of detail record: New field mapping profile
          • First accordion header: Summary (not Basic Info, like it shows in the wireframe) [default to open]
            • Name [required data element; cannot duplicate other field mapping profile names]
            • Incoming record type with dropdown list of these values
              • MARC bibliographic
              • MARC holdings
              • MARC authority
              • EDIFACT invoice
              • Delimited
            • FOLIO record type with dropdown list of these values
              • Instance
              • Holdings
              • Item
              • Order
              • Invoice
              • MARC bibliographic
              • MARC holdings
              • MARC authority
            • Description [free text field]
          • Second accordion header: Details (not Overview, like it shows in the wireframe) [default to open]
            • Leave this section blank for now [will contain details about the action to be taken. See UIDATIMP-15 for details
          • Third accordion header: Associated action profile [default to open]
            • Leave this section blank for now [will contain details about the associated action profile, and a way to select the action profile to attach to the field mapping profile. See UIDATIMP-??? for details
          • NOTE: The other profile details screens have a section showing the job profiles that use the profile. This will not exist for Field mapping profiles, since they are always associated with a single Action profile, and travel with it.
      3. Scenario 3
        • Given the New New Field mapping profile screen
        • If a User has filled in any data on the screen and begins to navigate away from it without creating/saving it
        • Then the user should see the standard modal asking whether they want to continue or not, as shown in the attached Unsaved changes modal.PNG
      4. Scenario 4
        • Given the New Field mapping profile screen
        • If a User has filled in all required fields and presses the "Save" button
        • Then the record should be saved
        • And the details screen closed
        • And the user returned to the Field mapping profile list (with the new field mapping profile in the list, in alphabetical order), and with the Fourth pane details showing for the newly-created Field mapping profile
      5. Scenario 5
        • Given the New Field mapping profile screen
        • If a User has not filled in all required fields and presses the "Save" button
        • Then
          • The record should not be saved
          • And the missing required data element(s) should be outlined in red, with the cursor in the data entry box for the first missing required element, along with the standard warning message, as shown in the attached Missing Required Data.PNG
      6. Scenario 6 See UIDATIMP-248 for the bug fix for this
        • Given the attempt to save
        • If the new Field mapping profile's name duplicates an existing Field mapping profile name
        • Then do not save the record
        • And remain on the new Field mapping profile screen
        • And display a red unsuccessful toast: New record not created: Field mapping profile [Field mapping profile name] already exists similar to attached Duplicate job profile error message.PNG Functionality is correct, but there's a problem with the toast text. See attached Duplicate record toast
      7. Scenario 7
        • Given the attempt to save
        • If there is a communication issue with the backend, and the save is not successful
        • Then display a red unsuccessful toast: New record not created: Communication problem with server. Please try again, as per attached Communication problem with server.PNG
      8. Scenario 8
        • Include standard automated testing coverage; add screenshot or other details to confirm test coverage is in place

        TestRail: Results

          Attachments

            Issue Links

              Activity

                People

                Assignee:
                Oleksandr Yehorov Oleksandr Yehorov
                Reporter:
                abreaux Ann-Marie Breaux
                Tester Assignee:
                Ann-Marie Breaux Ann-Marie Breaux
                Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved:

                    TestRail: Runs

                      TestRail: Cases