Clear case view cache when cancelling an edit flow#2179
Open
jamescatto-cgi wants to merge 2 commits into
Open
Conversation
…page is cancelled
chrisjones-hmcts
previously approved these changes
Jun 3, 2026
|
6 tasks
chrisjones-hmcts
approved these changes
Jun 4, 2026
anthonydummer
approved these changes
Jun 4, 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
3 participants
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 link (if applicable)
https://tools.hmcts.net/jira/browse/POFCC-214
Change description
When a case is edited there can be some changes to the case that are not submitted. This happens in some scenarios when the case is validated. Since the case is not submitted, the normal mechanism of clearing the cached
CaseViewin theCaseNotifieris not triggered. Thus, any amendments are not seen, e.g. in theSummarytab.To resolve this and avoid undue cache clearing, the cache is cleared when a cancellation is performed. This was thought sufficient since the
CaseNotifiercache is not used before then.Does this PR introduce a breaking change? (check one with "x")