Details
-
Story
-
Status: Closed (View Workflow)
-
P3
-
Resolution: Done
-
None
-
Folijet Sprint 93
-
5
-
Folijet
Description
Purpose: To provide additional validation for repeatable fields on Instance, Holdings, and Item field mapping screens
As a staff person working with field mapping profiles
I want tighter validation on the options for repeatable fields
So that it's more difficult to make a mistake
Scenarios
- Scenario 1
- Given a repeatable field on an Instance, Holdings, or Item field mapping profile
- When the user selects the option Add these to existing, Delete all existing and add these, or Find and remove these
- Then keep the "Add" button enabled
- And allow the user to create one or more repeatable fields for that value
- See Scenarios 1-2.PNG attached
- Scenario 2
- Given a repeatable field on an Instance, Holdings, or Item field mapping profile
- When the user selects the option Add these to existing, Delete all existing and add these, or Find and remove these
- And tries to save the field mapping profile
- But has not added one or more fields for that value
- Then do not allow the field mapping profile to be saved
- And outline the field in red and show red error message for the field: One or more values must be added before the profile can be saved.
- Scenario 3
- Given a repeatable field on an Instance, Holdings, or Item field mapping profile
- When the user selects the option Delete all existing values
- Then disable the "Add" button so that the user cannot add any values
- See Scenarios 3-4.PNG attached
- Scenario 4
- Given a repeatable field on an Instance, Holdings, or Item field mapping profile
- When a user adds one or more values
- And then selects the option Delete all existing values
- Then disable the "Add" button
- And delete any of the values in that field of the mapping profile
- Scenario 5
- Ensure automated testing coverage for this new code is 80% plus and confirm with screenshot
NOTE This applies to all areas on Instance, Holdings, and Item record screens where there are repeatable fields. See the complete list of repeatable fields in UIDATIMP-518. .
A-M: Test imports where
- Repeatable fields are added
- Repeatable fields are completely removed
- Repeatable fields are removed and replaced with the mapped one
- Only the mapped repeatable field is removed
Additional Information: See attached screenshot
Per OleksiiKuzminov no additional backend story required
TestRail: Results
Attachments
Issue Links
- defines
-
UIDATIMP-360 New UI components for field mapping details
-
- Closed
-
-
UXPROD-2446 Finish & cleanup MARC Field Mapping Profiles Details for Inventory records
-
- Closed
-
- has to be done after
-
UIDATIMP-518 Change placement of repeatable decorator in the Inventory field mapping screens
-
- Closed
-
- is required by
-
UIDATIMP-619 Cannot create a holdings field mapping profile on Goldenrod bugfest
-
- Closed
-
- relates to
-
MODDICORE-70 Actions in mapping profile don`t work correctly.
-
- Closed
-
-
UIDATIMP-501 withRepeatableActions decorator doesn't work in some sections of Instance profile
-
- Closed
-
-
UIDATIMP-596 Inconsistent in Holding schema between UI and Backend.
-
- Closed
-
-
MODDICORE-61 Field mappings: Repeatable fields dropdown action without subfields support
-
- Closed
-
-
MODDICORE-72 Holdings field mapping: Create holdings fails because mapping for holdings statement is not working
-
- Closed
-
-
UIDATIMP-401 Data Import field mapping profile details: Repeatable field dropdown component
-
- Closed
-
- requires
-
UIDATIMP-596 Inconsistent in Holding schema between UI and Backend.
-
- Closed
-