Versions Compared

Old Version 4

changes.mady.by.user Deny Raatgever

Saved on

compared with

New Version Current

changes.mady.by.user Deny Raatgever

Saved on

Key

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

When the case has reached its goal, it's archived. Reaching the goal could for example be that the resulting product is stored in the back office, or the change has been altered in a register application. It is time to archive the now completed case.

There are different types of data that could be useful for later. Most of the time the data could be classified in the following categories:

  1. Case Trigger data, what triggered the case? What did the applicant request in the first place?
  2. Case Resulting data, what is the result of the case? A decision? A product? 
  3. Case process data, what happened in the case? How did the the trigger lead to the result? What steps have been taken?

...

Info

Please note that the actual case data (case document + process + case dossier) are both deleted when the case is completed.

...

There are different ways of storing information from a Blueriq application. All of thos come with their own pros and cons. At the moment Blueriq does not contain a plug-and-play out of the box archiving function that serves all needs (if this is even possible). 

SolutionDescriptionSuitable forproscons
Document generationA document could be generated based on profile data. An archive document could be modelled containing all relevant information to be stored, Could be used for example for storing case process data.Case Process Data
  • Data is stored in a human readable format
  • Data can be viewed without a specific Blueriq model
  • For each change in the Blueriq model, the document model might be changed as well
  • Data cannot be consumed by other systems
  • Data cannot be searched easily
Reporting serviceThe reporting service can be used to store a profile (or selection) to a database. The result is an XML blob in the database containing profile informationCase Process Data
  • Can be used to store a complete profile
  • Does not necessarily depend on a model, so it would store all "new" information without explicitly changing the reporting service definition
  • Data is only readable for technical users (XML format)
  • Searching the data is difficult
AggregatesAn aggregate store can be used to store data in the database. Which can be loaded in a Blueirq model again for later use.

Case Process Data,

Trigger data,

Resulting data

  • Can be loaded into the working Blueriq model later
  • Data is ONLY valid when loaded into the same Blueriq model
  • No guarantees that the profile is similar to the store situation when loaded later (model changes)
  • Searching data is very limited and can only be done at the predetermined metadata
  • Cannot be used to query multiple cases

The DCM-Foundation models have implemented an example of all the possible solutions described above. Which (of course) could be altered to fit your specific needs.

...