HDPI-6501-Caseworker-Review-Dates-Automation

[PadmaDeenadayalan]

Jira link

See HDPI-6501

Change description

Automate ExUI CaseWorker Review dates Screens

Testing done

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]

DB breaking change scan

Recommended reading: HMCTS zero-downtime database deployments

No potentially breaking database changes were detected in the changed Flyway migration .sql files.

This check only scans changed .sql files under src/main/resources/db/migration and flags high-risk DDL patterns. It does not replace a full migration review.

Run details: https://github.com/hmcts/pcs-api/actions/runs/29736688409?check_suite_focus=true

[github-actions]

CCD diff summary

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

AuthorisationCaseState.json

UserRole	CaseStateID	CRUD
+circuit-judge	+CASE_ISSUED	+R
+ctsc	+CASE_ISSUED	+CRU
+fee-paid-judge	+CASE_ISSUED	+R
+judge	+CASE_ISSUED	+R
+leadership-judge	+CASE_ISSUED	+R
+wlu-admin	+CASE_ISSUED	+CRU

CaseField.json

RegularExpression	Max	Searchable	Min	FieldTypeParameter	HintText	Label	ID	FieldType
+	+	+	+	+	+	+---	+addCaseReviewDate-line-separator	+Label
+	+	+	+1	+ReviewDate	+	+Review date	+reviewDates	+Collection

AuthorisationCaseEvent/AuthorisationCaseEvent.json

UserRole	CaseEventID	CRUD
+circuit-judge	+addCaseReviewDate	+R
+ctsc	+addCaseReviewDate	+CRUD
+ctsc-team-leader	+addCaseReviewDate	+R
+fee-paid-judge	+addCaseReviewDate	+R
+hearing-centre-admin	+addCaseReviewDate	+CRUD
+judge	+addCaseReviewDate	+R
+leadership-judge	+addCaseReviewDate	+R
+wlu-admin	+addCaseReviewDate	+CRUD
+wlu-team-leader	+addCaseReviewDate	+R

AuthorisationCaseField/wlu-team-leader.json

UserRole	CaseFieldID	CRUD
+wlu-team-leader	+addCaseReviewDate-line-separator	+CR
+wlu-team-leader	+reviewDates	+RD

AuthorisationCaseField/wlu-admin.json

UserRole	CaseFieldID	CRUD
+wlu-admin	+addCaseReviewDate-line-separator	+CR
+wlu-admin	+reviewDates	+CRUD

AuthorisationCaseField/leadership-judge.json

UserRole	CaseFieldID	CRUD
+leadership-judge	+addCaseReviewDate-line-separator	+CR
+leadership-judge	+reviewDates	+RD

AuthorisationCaseField/judge.json

UserRole	CaseFieldID	CRUD
+judge	+addCaseReviewDate-line-separator	+CR
+judge	+reviewDates	+RD

AuthorisationCaseField/hearing-centre-admin.json

UserRole	CaseFieldID	CRUD
+hearing-centre-admin	+addCaseReviewDate-line-separator	+CR
+hearing-centre-admin	+reviewDates	+CRUD

AuthorisationCaseField/fee-paid-judge.json

UserRole	CaseFieldID	CRUD
+fee-paid-judge	+addCaseReviewDate-line-separator	+CR
+fee-paid-judge	+reviewDates	+RD

AuthorisationCaseField/ctsc.json

UserRole	CaseFieldID	CRUD
+ctsc	+addCaseReviewDate-line-separator	+CR
+ctsc	+reviewDates	+CRUD

AuthorisationCaseField/ctsc-team-leader.json

UserRole	CaseFieldID	CRUD
+ctsc-team-leader	+addCaseReviewDate-line-separator	+CR
+ctsc-team-leader	+reviewDates	+RD

AuthorisationCaseField/circuit-judge.json

UserRole	CaseFieldID	CRUD
+circuit-judge	+addCaseReviewDate-line-separator	+CR
+circuit-judge	+reviewDates	+RD

CaseEvent/addCaseReviewDate.json

Description	EndButtonLabel	ID	Name	PostConditionState	PreConditionState(s)	Publish	ShowEventNotes	ShowSummary
+Add review date	+Submit	+addCaseReviewDate	+Add review date	+CASE_ISSUED	+CASE_ISSUED	+N	+N	+Y

ComplexTypes/ReviewDate.json

ElementLabel	FieldType	HintText	ID	ListElementCode
+Date of review	+Date	+For example 16 4 2021	+ReviewDate	+date
+Reason	+FixedRadioList	+ReviewReason	+ReviewDate	+reason
+Description of review	+TextArea	+You can enter up to 500 characters	+ReviewDate	+description

CaseEventToFields/addCaseReviewDate.json

CallBackURLMidEvent	CaseEventID	CaseFieldID	DisplayContext	PageColumnNumber	PageDisplayOrder	PageFieldDisplayOrder	PageID	PageLabel
+http://localhost:3206/callbacks/mid-event?page=addCaseReviewDate&eventId=addCaseReviewDate	+addCaseReviewDate	+addCaseReviewDate-line-separator	+READONLY	+1	+1	+1	+addCaseReviewDate	+Review dates
+addCaseReviewDate	+reviewDates	+COMPLEX	+1	+1	+2	+addCaseReviewDate	+Review dates	+Y

FixedLists/ReviewReason.json

ID	ListElement	ListElementCode
+ReviewReason	+Dismiss case	+DISMISS_CASE
+ReviewReason	+General order	+GENERAL_ORDER
+ReviewReason	+Lift a stay	+LIFT_STAY
+ReviewReason	+Other	+OTHER
+ReviewReason	+Stay a case	+STAY_CASE
+ReviewReason	+Unless order	+UNLESS_ORDER

[srinijg]

Since changes made to common actions pls run full regression

[Gautham059]

Do we need these manual validations since we have auto content validation?

[SameenaHMCTS]

lgtm

[Gautham059]

Action needed for future:

1. Error validation needs to be improved as the data files are having logic info rather than pure data.
2. Action files are meant for having the page level actions and all the functional tests like error validation must not be tightly coupled with the e2e flow. This is an important action to maintain the uniformity across the repos.
   @PadmaDeenadayalan please create stories for these on the QAI board and will discuss these in our next improvements meeting.