-
Type: Story
-
Status: Closed (View Workflow)
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: None
-
Labels:None
-
Sprint:2022.R2 New Features Sprint 4, 2022.R2 New Features Sprint 5, 2022.R3 New Features Sprint 1
-
SCRUM Team:Brotherhood of Mutants
-
Story Points:3
-
Work Type Classification:Sustaining
Story
As an admin, I would like to recognize that when existing Master Level Operators are assigned a DFL Store Location in the Operator_All file, that the DFL Hierarchy relationship between the DFL Master/DFL Store is retained.
AC
- When an existing Master Level Operator is added to a DFL Store Location in the Operator_All file
- The Operator retains their Master Level hierarchy header
- The DFL Master continues to reside below the DFL Master header in the hierarchy and does not change when Operators are imported
- Do not create a Master level hierarchy header for new operators only assigned to a DFL store. Only the store level user.
- New Operators not assigned to a DFL Store will have a Master Level hierarchy created (existing functionality).
- New Operators assigned to multiple Stores including DFL will have a Master Level hierarchy created
- All other imports continue to function as expected.
- implements
-
CFAMX-18499 INF-12298 Ability to link Multiple Operators to a single location
- Open
- is blocked by
-
CFAMX-20024 DFL Operator is being Imported at the Master Level when Assigned to a Single DFL Store
- Done
- relates to
-
CFAMX-19897 DFL Master is not created when 1st DFL store is introduced from location import in Staging
- Done
-
CFAMX-19633 Master Operator unable to Access DFL Store
- Done
-
CFAMX-19724 2022 R2 Patchback CLONE - Master Operator unable to Access DFL Store
- Done
-
CFAMX-19749 2022 R2 Patchback CLONE - Master Operator unable to Access DFL Store
- Done