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

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

    XMLWordPrintable

    Details

    • Template:
    • Sprint:
      EPAM BatchLoader Sprint 16
    • Story Points:
      5
    • Development Team:
      Folijet

      Description

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

      As a staff person
      I want to be able to create match profiles that define how incoming records should match to existing FOLIO records, for the Data Import app
      So that I can reuse those match profiles as a component of job profiles, without having to recreate the match profile every time

      Live prototype:
      https://xd.adobe.com/view/0bb2d8ab-aabd-4ff6-4d5a-faa59a93368e-7d83/

      Brief video walk-through
      https://www.dropbox.com/s/3slcv4v49qm92rv/2018-11-06-data-import-19.mp4?dl=0

      Scenarios

      1. Scenario 1
        • Given the Data Import Settings Match profiles
        • When a User clicks the New button in the third pane
        • Then the New match profile screen should open
      2. Scenario 2
        • Given the New match profile screen
        • When a User views the screen with no edits
        • Then it should appear like this (based loosely on the attached 41a-Settings Match profiles Match profile details.png)
          • Header: New match 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 match profile
          • First accordion header: Summary (not Basic Info, like it shows in the wireframe) [default to open]
            • Name [required data element; cannot duplicate other match profile names]
            • 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 incoming record type and its match field(s), existing FOLIO record type and its match field(s), and how the matching is to be done. See UIDATIMP-175 for details
          • NOTE: The match profile details screen has a section showing the job profiles that use this match profile. This section will not exist in the New match profile screen. Match profiles will be associated with job profiles from the Job profile New/Edit screen. Once a match profile is associated with a job profile, then the job profile will appear at the bottom of the match profile detail screen.
      3. Scenario 3
        • Given the New match 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
      4. Scenario 4
        • Given the New match 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
      5. Scenario 5
        • 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:
                abreaux Ann-Marie Breaux
                Reporter:
                abreaux Ann-Marie Breaux
                Tester Assignee:
                Ann-Marie Breaux Ann-Marie Breaux
                Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved:

                    TestRail: Runs

                      TestRail: Cases