-
Type:
Story
-
Status: Closed (View Workflow)
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: CFA 2022R2
-
Component/s: None
-
Labels:None
-
Sprint:2022.R2 New Features Sprint 2, 2022.R2 New Features Sprint 3, 2022.R2 New Features Sprint 4
-
SCRUM Team:Brotherhood of Mutants
-
Story Points:5
-
Work Type Classification:Sustaining
Story
As an admin, I would like to recognize operators in the Operator_All file that are imported into a “DFL” store and, instead of creating those operators at the master level of the hierarchy, create store level users with full operator permissions in the store to which they are assigned.
AC
- When the Operator_All file is imported, check the store listed with the operator to see if the store is a “DFL” location.
- If the store is a DFL location, import the operator as a store level user.
- Elevate the user permission of the newly created store level user to “Operator”
- Do not create a Master level hierarchy header for this operator. Only the store level user.
- If the store is not a DFL store, import the operator as we do today and proceed using the existing import functionality.
- DFL stores should always reside below the “DFL Master” header in the hierarchy and should not change hierarchy locations when operators are imported.
- All other imports continue to function as expected.
- implements
-
CFAMX-18499 INF-12298 Ability to link Multiple Operators to a single location
-
- Open
-
- relates to
-
CFAMX-19307 DFL: Operator import not working for non DFL stores
-
- Done
-
There are no Sub-Tasks for this issue.
