Details
-
Bug
-
Status: Closed (View Workflow)
-
P1
-
Resolution: Done
-
None
-
-
3
-
Folijet Support
-
R2 2021 Hot Fix #2
-
Yes
-
Hotfix approved in release_bug_triage channel 9/9/21
-
MO State
-
Implementation coding issue
Description
Overview: When removing an action profile from a job profile, sometimes that will cause that action profile to be removed from all job profiles it is associated with. It seems to be happening when the action profile is indented under a match or submatch
Current workaround: Remember, or take a screenshot, of all of the job profiles an action profile is associated with, before deleting that action profile from the job profile. Then check all other job profiles that had that action profile and re-add. Not an easy or viable workaround
Steps to Reproduce:
- Log into FOLIO-snapshot-load as diku_admin
- Go to Settings/Data import
- Create the following profiles, all MARC-based, details don't matter. No field mapping profiles needed
- Match profile 1
- Match profile 2
- Action profile: Create instance 1
- Action profile: Create instance 2
- Action profile: Create holdings 1
- Action profile: Create holdings 2
- Action profile: Create item 1
- Action profile: Create item 2
- Create the following job profiles
- Job profile 1, and attach
- Action profile: Create instance 1
- Action profile: Create holdings 1
- Action profile: Create item 1
- Job profile 2
- Match profile 1
- If matched
- Action profile: Create instance 2
- Action profile: Create holdings 2
- Action profile: Create item 2
- Job profile 3
- Match profile 1
- If matched
- Action profile: Create instance 1
- Action profile: Create holdings 1
- Action profile: Create item 1
- Job profile 4
- Match profile 1
- If matched
- Action profile: Create instance 1
- Action profile: Create holdings 1
- Action profile: Create item 1
- If not matched
- Action profile: Create instance 2
- Action profile: Create holdings 2
- Action profile: Create item 2
- Job profile 5
- Match profile 1
- If matched
- Match profile 2
- If matched
- Action profile: Create instance 1
- Action profile: Create holdings 1
- Action profile: Create item 1
- If not matched
- Action profile: Create instance 2
- Action profile: Create holdings 2
- Action profile: Create item 2
- Job profile 1, and attach
- Scenario 1:
BF
- Edit Job profile 1 and remove Action profile: Create holdings 1
- Check job profiles 3,4,5 to see if the Create holdings 1 action is still attached
- Scenario 2:
BF
- Edit Job profile 2 and remove Action profile: Create instance 2
- Check job profiles 4 and 5 to see if the Create instance 2 action is still attached
- Scenario 3:
BF
- Edit Job profile 5 and remove Action profile: Create item 1
- Check job profiles 1, 3, 4 to see if the Create item 1 action is still attached
- Scenario 4:
BF
- Edit Job profile 5 and remove Action profile: Create item 2
- Check job profiles 2 and 4 to see if the Create item 2 action is still attached
Expected Results: Action profiles should stay attached to any job profiles that use them, except for the particular job profile that the user is removing the action profile from
Actual Results:
- Scenario 1: Create holdings 1 action profile stayed attached to all job profiles it was supposed to be attached to
- Scenario 2: Create instance 2 action profile was removed from Job profile 2 as it should be, but was also incorrectly removed from Job profiles 4 and 5
- Scenario 3: Create item 1 action profile was removed from Job profile 5, and the other job profiles were fine, Note that this action profile was one level deeper in the outline than in any other profiles
- Scenario 4: Create item 2 action profile was removed from Job profile 5 as it should be, but was also incorrectly removed from Job profiles 2 and 4
Additional Information: See attached video
Interested parties: Raegan
TestRail: Results
Attachments
Issue Links
- blocks
-
MODDICONV-205 Release v1.11.3 (R2 Juniper HotFix #2)
-
- Closed
-
- defines
-
UXPROD-3041 NFR: Data Import (Batch Importer for Bib Acq) R3 2021 Kiwi Technical, NFR, & Misc bug work
-
- Closed
-