Versions Compared

Key

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

DCM, DCM 2.0, Dynamic Case management, Case-Modelling

Type of accelerator

A quick start for a Dynamic case management (DCM) project

How to get
CompatibilityBlueriq 1517.11 10 and higher

Description

Configuration

Model configuration

The package can be loaded in a new or existing repository. After loading errors will occur, since some of the projects should be internal libraries. Edit the project structure for the projects below, ang check the "is library" option.

Basis_Proces

  • Basis_Zaak

  • Basis_ZaakDomeinMetadata

  • Globals

Also the AquimaLibraries BlueriqLibraries need to be imported (one of the default packages to import from Studio, they can be found at BlueriqCompleteLibraries Package (import the CaseModelling package, not the ProcessModelling package).

After performing the steps above, the model should not have any validation errors anymore.

Property configuration

The Main_Dashboard project relies on external flows to start any case type. One case type is included in the package ZaakType_A and needs to be configured. The minimal settings need one external flow to be configured, and one shortcut. Example configuration.

The external flow from Case Type A starts a shortcut:

Code Block
titleapplication-external-flow.properties
blueriq.connection.start_ZaakType_A.external-flow.shortcut-name=ZaakType_A

The shortcut definition:

Code Block
titleapplication.properties
blueriq.shortcut.ZaakType_A.flow=StartExternalFlow
blueriq.shortcut.ZaakType_A.languageCode=nl-NL
blueriq.shortcut.ZaakType_A.project=studio-DCMFoundation-ZaakType_A
blueriq.shortcut.ZaakType_A.theme=material
blueriq.shortcut.ZaakType_A.ui=angular
blueriq.shortcut.ZaakType_A.version=0.0-V4_9_10<version_number>

The startflow of the Main Dashboard project depends on two different roles to login: Aanvrager and Behandelaar. When using basic authentication, sample users could be:

Code Block
titleusers.properties
aanvrager={noop}Aanvrager,Aanvrager
behandelaar={noop}Behandelaar,Behandelaar
Info

Note, the beta development installation script described on DCM 2.0 beta installation Blueriq DCM Development Installation configures most settings for you. Most likely the only change to make is the shortcut, which should point to your studio model (repository/branch/project).

Version History

ChangesVersion

Compatibility minimal

Blueriq version

PackageDownlaods
  • Changed all message events
  • updated
  • to work with the
  • new version of DCM_CaseCreate service
  • merged intake and implementation module, so only one process datamapping is needed, and the structure is less complex
  • deleted unnecessary value list case-type from MainDashboard
  • deleted unused ERD's
  • Changed inputs of Statistics container from Date to DateTime
  • Updated Baars GetCase with new information (whether the reminder has been sent already)
4.9.1015.11download
  • added statistics based on the static instances of case types
  • improved dashboard flow (readability)
  • deleted broken entity-relation-diagram
4.9.915.8download
  • some namechanges, tidying up to comply at BMA rules.
  • Webservice endpoint added for setting the involvement of an employee
  • Webservices to search cases first count, and then retrieves
  • MainDashboard changed, each case type consists of a static instance of "ZaakType",
    adding such an instance + shortcut is enough to add a case type to the dashboard
4.9.815.2download
  • migrate to the latest version of the AquimaLibraries, DCM_ services require a process id's from this version on
  • audit logging attributes moved to dedicated entity in the model
  • audit logging, retrieve taskname at the start of a task
4.9.715.1download
  • MessageEvent FlowType
4.9.1817.10
  • fixed process-types with archiving. New validations pointed out a small error in the structure
  • simplified document upload using the latest container changes
  • added the flowtype "automatic task" to all automatic task implementations
4.9.1717.7
  • Changed the way the documents upload work. documents are the functional items needed in the case,
    files are attached to documents to match the requested documents. Documents stay in the dossier,
    while files move to the DMS eventually.
  • Documents and files are part of the dossier, and moved to the case details screen
  • Moved Baars interface to an internal library, for easy sharing to other models
  • Fixed broken webservices my including the right modules under Webservice
  • Fixed archive aggregate type
4.9.1617.3


  • added example of using the "SearchTaskByName"
  • added example of a notification for lock status (GetCaseInfo)
4.9.1517.1download
  • changed pattern for processing incoming message events using the GetCaseInfo service
  • introduced the "reference" as standard field in the lists
  • CaseTypes field uses valuelist for display purposes (possibly different languages)
  • Task Names are used as display name on top of the widget
  • Audit model references deleted since they are no longer needed
  • Added a 2-man-rule example (Beoordeling Controleren)
  • cases that need a specific type of involvement can be derived and shown in a caselist
4.9.1416.8download
  • Moved process modules to project-context and deleted process library
  • Search Baars implemented with the DCM_CaseSearch
  • Added roles to Baars endpoints
  • Added example model migration endpoints
  • removed unused GetRequestParameter services
  • Deleted unused dummy process module in the MainDashboard
4.9.1316.4download
  • Updated to work with new BlueriqLibraries
4.9.1216

First working version for DCM beta version

  • Statistics work with Case Type A
  • BMA checks processed
  • Aquima Libraries compatible with BQ 15.0
  • Sample archiving step added, after archiving, the case will be closed and deleted as default
  • Blueriq logo (GIF) adjusted to work with the new document renderer
  • Project structure altered, separate module for dossier, metadata and process domain
4.9.615.0download