Page History

Table of contents

Persistency management

Persistency management is the term used in Blueriq to address everything that has to do with persisting (or saving, storing) information and later on retrieving, displaying, updating and deleting this information.

...

Aggregates

Within Dynamic Case Management solutions, multiple cases can work with a common set of shared information. See the example below.

...

Shown are three different cases that are part of a single business model of an insurance company, one about a medical insurance, one about a dental insurance and one about a home insurance. These cases use and share information. The medical and dental case both use the medical information and the person information, whereas the home insurance makes use of the person information and house information. These information objects are called aggregates in Blueriq and will typically exist of a couple of entities with their endogenous relations. The reason that different aggregates can be created has to do with design, reuse as well as performance. It makes no sense to use information about a house when deciding about a dental insurance. On the other hand, it is not wanted that a medical insurance case and a dental insurance case each use their own medical information. Finally, unnecessary information used in a case will result in unnecessary actions that will have a negative impact on performance.

Aggregate definition

So, aggregates are used to combine information that belongs together. In Blueriq, information that belongs together is modeled in an entity. Aggregates simply combine entities.

...

Lists

Aggregates - like instances, tasks and cases - can be viewed in a list. A standard container AQ_Aggregate_List is available which can be used to display aggregates in run time.

Create/Read/Update/Delete

For each CRUD-action a standard service is available.

...