HDPI-5535 Page - View the response

[mazzopardi2]

Jira link

See HDPI-5535
See [HDPI-6457] (https://tools.hmcts.net/jira/browse/HDPI-6457)

Change description

• New “view defendant response” flow - Defendants can load a submitted response via CCD event
• Read mapping - Submitted response data is mapped from Postgres into the case payload the frontend uses.
• date submitted and statement-of-truth details are stored on submit.
• Claim issued date - New claim_issued_date on the claim; set when the issue fee is paid.
• Claimant details on view - Claimant name and address for service are added to the view payload from case parties.

Testing done

-added unit tests and manual testing

Security Vulnerability Assessment

CVE Suppression: Are there any CVEs present in the codebase (either newly introduced or pre-existing) that are being intentionally suppressed or ignored by this commit?

• Yes
• No

Checklist

• commit messages are meaningful and follow good commit message guidelines
• README and other documentation has been updated / added (if needed)
• tests have been updated / new tests has been added (if needed)
• Does this PR introduce a breaking change

[github-actions]

CCD diff summary

👉 Full report: https://github.com/hmcts/pcs-api/actions/runs/28284865557?check_suite_focus=true

CaseField.json

RegularExpression	Max	Searchable	Min	FieldTypeParameter	HintText	Label	ID	FieldType
-	-	-	-	-	-	-	-claimantNames	-Text
-	-	-	-	-	-	-	-dateIssued	-DateTime
-	-	-	-	-	-	-	-dateIssuedString	-Text
-	-	-	-	-	-	-	-defendantNames	-Text
-	-	-	-	-	-	-	-postCode	-Text

WorkBasketResultFields.json

Label	CaseFieldID
+Property Address	+propertyAddress
-State	-[STATE]
-Claimant names	-claimantNames
-Date issued	-dateIssuedString
-Defendant names	-defendantNames
-Postcode	-postCode
-Case number +Case Number	[CASE_REFERENCE]

AuthorisationCaseField/wlu-admin.json

UserRole	CaseFieldID	CRUD
+wlu-admin	+propertyAddress	+R
-wlu-admin	-claimantNames	-R
-wlu-admin	-dateIssuedString	-R
-wlu-admin	-defendantNames	-R
-wlu-admin	-postCode	-R

AuthorisationCaseField/hearing-centre-admin.json

UserRole	CaseFieldID	CRUD
+hearing-centre-admin	+propertyAddress	+R
-hearing-centre-admin	-claimantNames	-R
-hearing-centre-admin	-dateIssuedString	-R
-hearing-centre-admin	-defendantNames	-R
-hearing-centre-admin	-postCode	-R

AuthorisationCaseField/ctsc.json

UserRole	CaseFieldID	CRUD
+ctsc	+propertyAddress	+R
-ctsc	-claimantNames	-R
-ctsc	-dateIssuedString	-R
-ctsc	-defendantNames	-R
-ctsc	-postCode	-R

AuthorisationCaseField/caseworker-pcs.json

UserRole	CaseFieldID	CRUD
+caseworker-pcs	+propertyAddress	+R
-caseworker-pcs	-claimantNames	-R
-caseworker-pcs	-dateIssuedString	-R
-caseworker-pcs	-defendantNames	-R
-caseworker-pcs	-postCode	-R

AuthorisationCaseField/caseworker-pcs-solicitor.json

UserRole	CaseFieldID	CRUD
-caseworker-pcs-solicitor	-claimantNames	-R
-caseworker-pcs-solicitor	-dateIssued	-CRU
-caseworker-pcs-solicitor	-dateIssuedString	-R
-caseworker-pcs-solicitor	-defendantNames	-R
-caseworker-pcs-solicitor	-postCode	-R

AuthorisationCaseField/DEFENDANTSOLICITOR.json

UserRole	CaseFieldID	CRUD
-[DEFENDANTSOLICITOR]	-claimantNames	-R
-[DEFENDANTSOLICITOR]	-dateIssued	-CRU
-[DEFENDANTSOLICITOR]	-dateIssuedString	-R
-[DEFENDANTSOLICITOR]	-defendantNames	-R
-[DEFENDANTSOLICITOR]	-postCode	-R

AuthorisationCaseField/DEFENDANT.json

UserRole	CaseFieldID	CRUD
-[DEFENDANT]	-claimantNames	-R
-[DEFENDANT]	-dateIssued	-CRU
-[DEFENDANT]	-dateIssuedString	-R
-[DEFENDANT]	-defendantNames	-R
-[DEFENDANT]	-postCode	-R

ComplexTypes/PossessionClaimResponse.json

ListElementCode	ID	FieldTypeParameter	FieldType	ElementLabel
+claimantServiceAddress	+PossessionClaimResponse	+	+AddressUK	+Address for service
+claimIssuedDate	+PossessionClaimResponse	+	+Date	+Date issued

ComplexTypes/4_DefendantResponses.json

Max	ListElementCode	ID	FieldTypeParameter	FieldType	ElementLabel
+	+statementOfTruthCompletedBy	+DefendantResponses	+	+Text	+

[hmcts-jenkins-j-to-z]

Plan Result (aat)

⚠️ Resource Deletion will happen

This plan contains resource delete operation. Please check the plan result very carefully!

Plan: 0 to add, 0 to change, 1 to destroy.

• Delete
  • module.postgresql.azurerm_postgresql_flexible_server_configuration.pgsql_server_config["pg_qs.query_capture_mode"]

Change Result (Click me)

  # module.postgresql.azurerm_postgresql_flexible_server_configuration.pgsql_server_config["pg_qs.query_capture_mode"] will be destroyed
  # (because key ["pg_qs.query_capture_mode"] is not in for_each map)
  - resource "azurerm_postgresql_flexible_server_configuration" "pgsql_server_config" {
      - id        = "/subscriptions/1c4f0704-a29e-403d-b719-b90c34ef14c9/resourceGroups/pcs-data-aat/providers/Microsoft.DBforPostgreSQL/flexibleServers/pcs-aat/configurations/pg_qs.query_capture_mode" -> null
      - name      = "pg_qs.query_capture_mode" -> null
      - server_id = "/subscriptions/1c4f0704-a29e-403d-b719-b90c34ef14c9/resourceGroups/pcs-data-aat/providers/Microsoft.DBforPostgreSQL/flexibleServers/pcs-aat" -> null
      - value     = "top" -> null
    }

Plan: 0 to add, 0 to change, 1 to destroy.