Purpose: To be able to edit existing settings for match profiles.

Notes:
This story is very similar to UIDATIMP-132, which creates a new job profile setting. This story should be able to reuse much of what was built in UIDATIMP-132.
This story builds the edit screen and functionality. It is then connected to the UI's Edit buttons in the 4th pane via story UIDATIMP-134.

As a staff person
I want to be able to update settings related to job profiles for the Data Import app
So that they will be accurate

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 for Job profiles

   • When a User wants to update an existing job profile

   • Then they should be able to access an Edit job profile screen

2. Scenario 2

   • Given the Edit job profile screen

   • When a User views the screen with no edits

   • Then it should appear like this (based loosely on the attached 29-Settings Job profiles Job profile details.png)

     • Header: Edit [job profile name]

     • "Save" button at the top right of the header, which is greyed out until data has been filled in, then turns to blue once the screen is dirty (has some data in it)

     • Top of detail record:

     • First accordion header: Summary [default to open]

       • Name [required data element, cannot duplicate an existing job profile name]

       • Accepted data type [dropdown options for Delimited, EDIFACT, and MARC; only allow one option to be selected] [required data element]

       • Description [free text field, no length restriction]

       • NOTES

         • For any required data element, make sure the field name has an asterisk next to it

         • There is no "Imports with this profile" section in the Edit jobs profile screen

     • Second accordion header: Overview [default to open]

       • Leave this section blank for now [will contain basic info and links to match, action, and data mapping profiles] See UIDATIMP-152 for details

     • Standard end of record icon and wording - but OK , we'll add when we add the Overview section

3. Scenario 3

   • Given the Edit job profile screen

   • If data is missing from any required field and the User 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 Edit job profile screen

   • If the job profile name duplicates and existing job profile name or there are connection issues, when a User clicks the Save button

   • Then the user should remain on the record

   • And the record should not be saved

   • And there should be a red toast saying Record not saved and then the reason it wasn't saved, e.g. Record not saved. Job profile [this name] already exists Or Record not saved. Connection problem.

5. Scenario 5

   • Given the Edit job 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

6. Scenario 6

   • Given the Edit job profile screen

   • When a User clicks the caret to the left of the first accordion (Summary)

   • Then the caret should reverse direction and the accordion should be toggled closed

7. Scenario 7

   • Given the Edit job profile screen

   • When a User clicks the caret to the left of the second accordion (Overview)

   • Then the caret should reverse direction and the accordion should be toggled closed

8. Scenario 8

   • Ensure automated testing coverage for this new code is 80% plus and confirm with screenshot