This is not how you deal with a child re-entering DCS’ care. If a child's first case is closed, and they come back into the care of DCS, workers should open a new case, but use the same people that were created for the first case.
Revising a Closed Case
Once a case has been approved for closure, all workers can see a Make Revisions button at the bottom of the closed case.
After the Make Revisions button is clicked:
You will be able to edit the overall case just as if the case was active, including involvements, placements, and uploading more files.
The case will need to be resubmitted to a supervisor and approved before it can be closed again. After the case has been reclosed, another workflow event will be added to the history page which says "[User] finished making revisions."
The workflow progress bar will show that you are making revisions and then progress as the case is submitted and approved.
A workflow event will be added to the history page saying "[User] put the case back into a revisions state.
Reverse Case Closure
Supervisors and CEU workers will see a reopen button on the bottom of the case page. This will make it as though a case was never closed. This functionality would be used, for example, if a case was closed by mistake.
After the case closure has been reversed:
The history page should show no evidence of the case having been closed previously. The workflow events associated with the submission and approval should disappear.
The assigned FCM should receive an in-app notification that says, "<User xyz> reversed the closure on your <case name>. It is now open again and you are still the assigned case manager."
When it is time for the case to be closed, the case should be submitted for closure to a supervisor and approved normally. Each time the case is submitted for review, sent back for edits, approved, or reopened, the Case History page will document the action, and the user, date and time of each action.