When running a DCM application, many different sources of data are kept track of. Most of them have a lifecycle similar to the case itself. They will be deleted when the Case is finished. Some sources remain when the Case is finished, leaving it for the maintainers of the application to decide what to do with the information.
Data during case execution
Below is a table containing different types of data with the lifespan of the case itself. When case if finished (process has finished its last node), this data will be deleted.
| Data | Component | Datasource |
|---|---|---|
| process and tasks | Case Engine | process-sql-store |
| case document | Case Engine | Case Engine mongo store |
| metadata aggregate | Customerdata service | aggregregate store |
| dossier aggregate | Customerdata service | aggregate store |
| case and user tasks | DCM Lists service | DCM Lists mongo store |
Data with manual lifecycle
Other datasources will remain in the database, and should be actively maintained by a user to keep the system running smoothly. The data remains to offer the possibility to archive the data after the case has been finished.
| Data | Component | Datasource |
|---|---|---|
| process and tasks | Case Engine | process-sql-store |
| case document | Case Engine | Case Engine mongo store |
| metadata aggregate | Customerdata service | aggregregate store |
| dossier aggregate | Customerdata service | aggregate store |
| case and user tasks | DCM Lists service | DCM Lists mongo store |
Overview
Content Tools