FPVTL-2392- Path finder changes for auto set#3660
Open
ravidoki-hmcts wants to merge 15 commits intomasterfrom
Open
FPVTL-2392- Path finder changes for auto set#3660ravidoki-hmcts wants to merge 15 commits intomasterfrom
ravidoki-hmcts wants to merge 15 commits intomasterfrom
Conversation
srochani
approved these changes
Mar 24, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Jira : https://tools.hmcts.net/jira/browse/FPVTL-2392
Auto‑set Pathfinder on Issue & Send (C100)
Description
Automatically set Pathfinder = Yes on C100 when “Issue and send to local court” is completed and the issuing court’s DFJ is an active Pathfinder area on the event date. Preserve manual overrides.
Scenarios
Scenario 1: Auto‑set Pathfinder = Yes for case inside DFJ area
Given a C100 case and the issuing court’s DFJ area is configured as Pathfinder
When a user submits Issue and send to local court
Then the system sets Pathfinder = Yes and records in the summary tab and a history entry is created saying 'Pathfinder Decision Yes'
Scenario 2: Auto-set Pathfinder =No for case outside DFJ area
Given a C100 case and the issuing court’s DFJ area is not configured as Pathfinder
When a user submits Issue and send to local court
Then the system sets Pathfinder = No and does not display in the summary tab
Scenario 3: Check Manual Pathfinder = Yes still works
Given an authorised user and a C100 case with Pathfinder unset or No
When they complete Next Steps → Pathfinder decision = Yes
Then Pathfinder = Yes is saved and a Summary tab and History entry is created saying 'Pathfinder Decision Yes'
Scenario 4: Check Manual Pathfinder override to No still works
Given a C100 case with Pathfinder = Yes (automatically set to Yes)
When an authorised user sets Pathfinder decision = No to manually saved as No
Then Pathfinder = No is saved and summary tab and a History entry is created saying 'Pathfinder Decision No'
Does this PR introduce a breaking change? (check one with "x")