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

Data import settings page's 4th pane for Action Profiles: Header action for Delete



    • EPAM BatchLoader Sprint 20
    • 2
    • Folijet


      Purpose: To define the actions of the Data import settings Action profile 4th pane Header Actions. This story adds the Delete functionality. The Duplicate functionality is handled in UIDATIMP-148, and the Edit functionality is handled in UIDATIMP-149 and UIDATIMP-220

      As a staff person
      I want to be able to delete individual Action profiles via the options shown in the 4th pane header
      So that I can remove unneeded or obsolete Action profiles.

      Live prototype:

      Brief video walk-through

      NOTE: 4th pane header showing the caret next to the Action profile name and the edit pencil was created in UIDATIMP-146


      1. Scenario 1
        • Given the Data Import Settings/Action profile 4th pane, showing the details of an individual action profile
        • When a User clicks the down caret next to the name of the Action profile in the header
        • They should see three options in the caret menu (see 66a-Settings Action profile detail caret options.png)
          • Edit, preceded by the pencil icon
          • Duplicate, preceded by the duplicate (2 boxes) icon
          • Delete, preceded by the trashcan icon (even though the mockup doesn't show the trash can)
      2. Scenario 2
        • Given the action caret in the header of the Data Import Settings/Action profile 4th pane
        • When the user clicks the "Delete" option
        • Then a confirmation modal should appear, formatted as shown in 07-Settings Delete file extension modal.png
          • Except with the following text:
          • Header: Delete [Action profile name] action profile?
          • Body: Delete action profile?
          • Standard Cancel/Delete buttons, with Delete defaulted
      3. Scenario 3
        • Given the delete confirmation modal
        • When a user clicks Cancel
        • Then close the delete confirmation modal without deleting the action profile
      4. Scenario 4
        • Given the delete confirmation modal
        • When a user clicks Delete action profile and the action profile is not connected to any Job or Field mapping profile
        • Then delete the action profile
        • And remove the action profile from the list of action profiles
        • And return the user to the list (3rd pane) of action profiles, without the one that was just deleted
        • And display a standard green success toast with the wording: The action profile [action profile] was successfully deleted
      5. Scenario 5
        • Given the delete confirmation modal
        • When a user clicks Delete action profile and the action profile is connected to any Job profile or Field mapping profile (that is, you see any linked job profiles or field mapping profile at the bottom of the detail screen)
        • Then display an exception modal formatted as follows (similar to the attached Delete Not Allowed.png)
          • Header: Cannot delete Action profile
          • Text: This action profile cannot be deleted, as it is in use by one or more job or field mapping profiles.
          • Button: Close
        • And return the user to the action profile detail view
      6. Scenario 6
      7. Scenario 7
        • Ensure automated testing coverage for this new code is 80% plus and confirm with screenshot


      • When the action profile is deleted (at least from the UI perspective), still keep track of it, so that it can still be seen in the logs and associated with previous jobs/files that it was used for. Maybe consider an inactive flag/soft delete instead of deletion. We just don't want them to show in the UI list of action profiles any more.

      TestRail: Results


          Issue Links



                Oleksandr Yehorov Oleksandr Yehorov
                abreaux Ann-Marie Breaux
                Ann-Marie Breaux Ann-Marie Breaux
                0 Vote for this issue
                1 Start watching this issue



                  TestRail: Runs

                    TestRail: Cases