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

Create data import settings page's 3rd pane for Match Profiles

    XMLWordPrintable

    Details

    • Template:
    • Sprint:
      EPAM BatchLoader Sprint 15, EPAM BatchLoader Sprint 16
    • Story Points:
      8
    • Development Team:
      Folijet

      Description

      Purpose: To be able to create and save match profiles, so that they can be applied to saved and ad hoc job profiles used in Data Import

      As a staff person
      I want to be able to create and store match profiles for the Data Import app
      So that I can assemble them, along with action and mapping profiles in various configurations of job profiles
      And so that I do not have to reconstruct these configurations every time I import a new file

      Notes:

      • This story is only for creating the outline of the match profile pane on the settings screen. There will be additional stories for creating the create/edit screens for matches and for the detailed configuration of matches.

      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

      Sample data: https://docs.google.com/spreadsheets/d/1sMiwp6nbb08H9SOD-zxIsJ1i5d0e8RXZ_mliIw9mmDA/edit#gid=1212064214

      Scenarios

      1. Scenario 1
        • Given the Data Import Settings
        • When a User clicks the Match profiles setting in the second pane
        • Then the Match profiles option in the second pane should turn grey with white text and
        • A third pane should open, displaying a list of the existing match profiles
        • As shown in attachment 40-Settings Match profiles.png
      2. Scenario 2
        • Given the Match profiles third pane
        • When displaying the pane
        • Then the format of the pane should be as follows, as shown in attachment 40-Settings Match profiles.png
          • Header: [match profile icon] followed by Match profiles followed by a down caret [No action for now - action is covered by future story]
          • Subheader: # profiles, where # is the number of match profiles in the results list
          • New button (no plus sign) on right side of header [No action for now - action is covered by future story]
          • Top of results list: search box [No action for now - action is covered by future story]
          • Results list column headers
            • Check box [Can check and uncheck the checkboxes, but no action for now; top checkbox does not yet affect the individual line checkboxes for now, and all action is covered by future story]
            • Name
            • Match
            • Tags
            • Updated
            • Updated by
          • Results list data elements per row (alternating rows in white and grey)
            • Check box [No action for now - action is covered by future story]
            • Match profile icon followed by match profile name (row 2 in sample data) [NOTE: Match profile name must be unique]
            • Icon for FOLIO record type being matched (see list of record types attached) followed by brief summary of match, which consists of
              • FOLIO record type (row 14 in sample data)
              • Centered dot
              • Match field from incoming record (row 16 or 20 in sample data)
              • Right arrow
              • Field label for FOLIO record field being matched to (row 31, 35, or 36 in sample data)
              • NOTE: make sure the arrow and construction will reformat properly when screen changes from LTR to RTL (use Arabic localization setting to check)
            • Tag icon followed by tags; multiple tags are separated by comma [space], e,g. first, second, third (row 11 in sample data)
            • Edit pencil icon followed by most recent update date (row 4 in sample data)
            • User icon followed by most recent updater's name (firstname lastname) and username in parentheses, e.g. John Doe (johndoe) (row 5 in sample data)
          • Default sort order should be alphabetical A-Z by profile name
          • User should be able to sort and reverse sort by clicking on any of the column headers
          • End of list component (icon and wording)
      3. Scenario 3
        • Include standard automated testing coverage; add screenshot or other details to confirm test coverage is in place

      NOTES

        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:
                4 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved:

                    TestRail: Runs

                      TestRail: Cases