Sensitive case registering unit - #196
Merged
Merged
Conversation
renjithabby
marked this pull request as draft
August 3, 2026 13:46
|
renjithabby
marked this pull request as ready for review
August 3, 2026 17:09
bridgesr
approved these changes
Aug 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
2 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.
https://cpsgovuk.atlassian.net/browse/FCT2-21047
https://cpsgovuk.atlassian.net/browse/FCT2-21128
FCT2-21128 - issue was caused by no registering unit added for sensitive cms. Now registering unit is added just like area for sensitive cms
FCT2-21047 - removed change action for area and registering unit in the case of sensitive cms
Since both are related covered in the same pr and added new integration test