Details
-
Story
-
Status: Closed (View Workflow)
-
P2
-
Resolution: Done
-
None
-
customfield_11100 32508
-
EPAM BatchLoader Sprint 36, EPAM BatchLoader Sprint 37
-
3
-
Folijet
Description
Purpose: Document the changes needed in Job profile tree logic to limit static value matches to submatches only
As a staff person
I want to be able to create a job profile that uses a static value match, but that match is disallowed as a primary match (can only be a submatch)
So that the overall match logic is not disrupted
See overview PPT at https://docs.google.com/presentation/d/1r-MLsfgzrjdxhMm6z0AKCXWxr3b8B-yG35KgPzkG47g/edit#slide=id.p1
Scenarios
- Scenario 1
- Given the Create/Edit screen for Job profiles
- When a user selects a Match action at the topmost/primary level of the tree component
- Then in the match profile picker, display all available match profiles except ones with Incoming record type value = Not applicable - match to static value
- So that a static value match cannot be used as a primary match
- Scenario 2
- Given the Create/Edit screen for Job profiles
- When a user selects a Match action at a level other than the topmost/primary level of the tree component (so secondary, tertiary, etc)
- Then in the match profile picker, display all available match profiles, including the ones with Incoming record type value = Not applicable - match to static value
- Scenario 3
- Ensure automated testing coverage for this new code is 80% plus and confirm with screenshot
See attached screenshots
Per Kateryna Senchenko, new query is not needed; she will provide example
May need to add record type to the enum
TestRail: Results
Attachments
Issue Links
- defines
-
UIDATIMP-342 Create complete Job Profiles creation/save process
-
- Closed
-
-
UXPROD-2208 Remaining Job and Match profile work, part 3
-
- Closed
-
- relates to
-
MODDICORE-29 Support matching by STATIC_VALUE
-
- Closed
-