Versions Compared

Old Version 1

changes.mady.by.user Deny Raatgever

Saved on

compared with

New Version 2

changes.mady.by.user Deny Raatgever

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

This internal library shares the "ZaakMetadata" or Case Metadata definition. This is an aggregate definition where the properties are stored which are relevant for various Case-Types. This definition could hold attributes like "Phase", "Status" or "Deadlines". This is modelled in the form of an aggregate definition. In all interaction models, this definition can be used to either determine the values of this metadata field for the specific case, or to use the metadata "labels" for searching on active cases (DCM_CaseSearch) or requesting lists (for example the DCM_WorkList or DCM_CaseList).

This library could be maintained in a separate branch, and imported to all interaction models as external library. Or it could be added to the Repository where the Main Dashboard is also maintained (one project for multiple Case-Types).

Dashboards: Foundation

This is the model used in the DCM-Dashoard application. There is one dashboard model for all Case-Types (with possibly different pages for each Case-Type).This project could be maintained in a separate branch, or it could be added to the Repository where the Main Dashboard is also maintained (one project for multiple Case-Types)

Info

At this moment, there is no way to actively reload this model from Encore to the Dashboarding Service. Make sure when altered, to update the export on the server and restart the service.

...

To make sharing easier, all projects are maintained in a single repository. For demo purposes it is convenient to just keep every model in one repository. When you start using the DCM Foundation to actually create your solution, please consider how the models should be maintained. You could start by splitting the projects into two repositories:

  • DCM-Main_Dashboard containing all models which are deployed once for all Case-Types. This repository could consist of the Main_Dashboard project, the Dashboards project (there is one dashboard for all Case-Types), Globals libary and Basis_ZaakMetadata internal library.
  • Case-Type_XXX containing an actual Case-Type. This model includes the Case-Type itself, and the Basis_ZaakMetadata as an external library. Together with an include of the Globals (external) library. You could duplicate this repository for each new Case-Type that needs to be added.