Blocklisted Words Validation Across Registration Workflow #644
Description
User Story: Blocklisted Words Validation Across Registration Workflow
As a Registration Operator
I want the system to detect and prevent the use of blocklisted or prohibited words in demographic fields and critical review screens
So that the registration data remains clean, valid, and free from abusive, offensive, or restricted terms before submission.
Problem / Need
During data entry, operators may intentionally or unintentionally enter inappropriate, offensive, or disallowed words in fields such as name, address, or remarks. These errors may go unnoticed and can compromise data quality, cause audit failures, or violate compliance norms.
To ensure clean and safe demographic data, the system must have built-in validation to prevent the use of such blocklisted words at every key stage of the registration process.
Feature Description
The feature introduces an automated blocklist validation system that checks for prohibited words across the following pages:
Demographic Details Page
When operators enter demographic information (Name, Address, Parents’ Names, etc.), the system automatically checks user input against the blocklisted words repository.
If any blocklisted word is detected:
The field is highlighted.
An inline error message appears:
“This entry contains a prohibited word. Please correct the input.”
Operator cannot proceed until correction is made.
Acknowledgement Page
Before generating the acknowledgement slip, the system performs a final validation across all demographic fields.
If blocklisted content is found:
A modal alert appears with the list of fields containing prohibited content.
Operator must correct the fields in the Demographic Details Page before generating the acknowledgement.
Packet Approval Page
During operator or supervisor approval of the packet:
The system performs a last-stage blocklist validation before the packet is marked approved.
If prohibited content exists:
Approval is blocked.
An error message appears:
“Packet cannot be approved. Please revise demographic details to remove prohibited content.”
The operator is redirected to the specific field to make corrections.
Configuration & Flexibility
The blocklisted words are maintained in a centrally configurable list (JSON/YAML or server-managed configuration).
The list can be updated without code changes.
Supports multiple languages and case-insensitive matching.
Acceptance Criteria
AC1: Blocklist Validation
The system checks all demographic fields against the configurable blocklisted words.
AC2: Input Restriction on Demographic Details Page
If an operator enters a blocklisted term, inline validation prevents moving to the next step.
AC3: Validation on Acknowledgement Page
Blocklisted terms are flagged during acknowledgement generation.
The system blocks slip generation until resolution.
AC4: Validation on Packet Approval Page
Packet cannot be approved if any demographic field still contains blocklisted content.
AC5: Clear User Feedback
UI must display clear, actionable messages specifying which field contains prohibited content.
AC6: Configurability
Blocklist must be editable without deployment or code modification.
Supports Unicode, multilingual entries, partial matches, and regex-based patterns (if applicable).
AC7: Logging & Auditing
Any attempt to save or approve data containing blocklisted terms is logged for auditing.
User Flow Example
Operator enters address: “123 Fake Street - Test BadWord Colony.”
System detects "BadWord" from blocklist → shows inline error → operator corrects the input.
At Acknowledgement page, system revalidates → all clean → slip generated.
During Packet Approval, system performs final check → approval allowed only if all fields pass validation.