Add file name info and record sequence number for records posted direct via API

RCA Group

None

Description

Purpose: When records are posted directly to SRS via the API, they do not have a file name. Thus, the log information is difficult to access. This story assigns a default for the file name and ensures that the log summary screen includes sequence numbers for the records that were posted

Scenarios

  1. Scenario 1

    • Given the Data Import landing page

    • When a completed job in the log list represents records that were posted directly to SRS via the API

    • Then assign a label of No file name in the file name column of the log list entry

    • And whatever job profile was selected for the import

  2. Scenario 2

    • Given the Data Import "View all" log screen page

    • When a completed job in the log list represents records that were posted directly to SRS via the API

    • Then assign a label of No file name in the file name column of the log list entry

    • Then make sure that the "Record" field in the results lists is populated with "1" (currently shows "NaN"

  3. Scenario 3

    • Given the log summary screen that shows the list of records imported during a single job

    • When the list of records is the result of posting directly to the SRS API

    • Then make sure that the "Record" field in the results lists is populated with a sequential number for each record posted in the sesson

  4. Scenario 4

    • Ensure this story passes Accessibility testing

  5. Scenario 5

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

 move the No file name part to , and leave the sequence part here

Check with Theo to see if he is populating the field properly; already have examples in our docs per Oleksii (see details in MODCOPYCAT story)

Environment

None

Potential Workaround

None

Checklist

hide

TestRail: Results

Activity

Show:

Theodor Tolstoy (One-Group.se) April 14, 2021 at 6:08 AM

 From this test, is there anything I need to change in my process in order to make adopt any changes here? Or have we validated that my current process works?

Theodor Tolstoy (One-Group.se) April 12, 2021 at 6:15 PM

But I am glad that it works!

Theodor Tolstoy (One-Group.se) April 12, 2021 at 6:15 PM

Works for me too. Annoying. I wonder if every first edit will have that error

Ann-Marie Breaux April 12, 2021 at 1:29 PM

Hi I just looked at the record on folio-snapshot, and was able to edit it in QM just fine. I think? all is well.

Theodor Tolstoy (One-Group.se) April 12, 2021 at 12:31 PM

Is there anything obvious missing?

 

Done

Details

Assignee

Reporter

Priority

Story Points

Sprint

Development Team

Folijet

Fix versions

Release

R1 2021 Bug Fix

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created February 24, 2021 at 8:09 AM
Updated June 14, 2022 at 6:23 AM
Resolved March 26, 2021 at 7:36 PM
TestRail: Cases
TestRail: Runs