CaseFabric Reference Guide

CaseFabric Reference Guide

  • Overview
  • Getting Started
  • Training
  • CMMN
  • Case Designer
  • Case Engine
  • Extensions
  • API Reference
  • DCM for Mendix
  • Releases

›Releases

Overview

  • CaseFabric
  • A short introduction
  • Product Overview

Getting Started

  • Introducing CaseFabric Demo
  • Generic UI
  • How to use task UI rendering
  • Two business applications
  • Obtaining CaseFabric Demo

Training

  • Introduction
  • Obtaining the CaseFabric Demo
  • Chapter 1
  • Chapter 2
  • Chapter 3
  • Chapter 4

Some CMMN

  • What is CMMN
  • Modelling the Case Plan
  • Modelling the Case File
  • Modelling the Case Team
  • Other things to model

Case Designer

  • An IDE?
  • Designing
  • Tasks and Parameters
  • Expressions
  • Deploying
  • Debugging

Case Engine

  • The CaseFabric Engine
  • Authentication
  • Authorization
  • Pictorial overview
  • Configuration
  • Logging
  • Repository

Extensions

  • Do we need extensions?
  • Fault Handling
  • Workflow
  • Business Identifiers

API Reference

  • Introducing the API
  • Joining the platform
  • Start a Case
  • Case Team membership
  • Executing the case
  • Retrieving cases and tasks
  • Casefile requests

DCM for Mendix

  • Overview
  • DCM Add-On Architecture
  • Design Case Models
  • Interact with Cases
  • FAQ
  • Releases

Releases

  • Overview
  • 1.1.43
  • 1.1.42
  • 1.1.41
  • 1.1.40
  • 1.1.39
  • 1.1.38
  • 1.1.37
  • 1.1.36
  • 1.1.35
  • 1.1.34
  • 1.1.33
  • 1.1.32
  • 1.1.31
  • 1.1.30
  • 1.1.29
  • 1.1.28
  • 1.1.27
  • 1.1.26
  • 1.1.25
  • 1.1.24
  • 1.1.23
  • 1.1.22
  • 1.1.21
  • 1.1.20
  • 1.1.19
  • 1.1.18
  • 1.1.17
  • 1.1.16
  • 1.1.15
  • 1.1.14
  • 1.1.13
  • 1.1.12
  • 1.1.11
  • 1.1.10
  • 1.1.9
  • 1.1.8
  • 1.1.7
  • 1.1.6
  • 1.1.5
  • 1.1.4
  • 1.1.3
  • 1.1.2
  • 1.1.1
  • 1.1.0

Case Engine Release 1.1.42

Storage & performance

This release contains major changes to the way the case engine is storing information and processing it internally. This leads too great savings on the storage side, as well as considerable performance improvements.

Savings on your existing database can be achieved as well.

A tool is available that can do this for you, even on a live production system.
Contact us for more information about the database conversion tool.

Dependency updates

Updates that fix security issues in the underlying dependencies of the case engine have been applied in this release. This includes database driver versions, Apache Pekko libraries, authentication libraries and more. All have been updated.

Less events

When something happens in the case plan, e.g. a task becoming active, it would to many events on that same task. In this release, a major change has been applied on the case plan events, ensuring that no more than one event per task (or stage, milestone, timer, etc.) is generated. Also the names of the events are much more descriptive.
As an example, a task becoming active would generate an event PlanItemTransitioned. This has become straightforward TaskActivated, which is more functional and to the point.

Less storage

Perhaps this should read "way less storage". In the classic events, the XML based information containing the case definition was printed again and again in events. For large case models, this can make a database grow fast.
In this release, the unique case definitions are stored with a special hash in a database table, and the events only carry the hash. This leads to massive storage savings.

Better performance

Case Engine projections that run in-memory are now updated directly after the events have been persisted. This leads to improved response times on queries that are ran after the events got persisted. This option is enabled by default.

Release 1.1.39 introduced an additional tag on every event containing root actor id. The purpose of which is to be able to retrieve all events of a case chain in one shot.
Customers reported a negative performance impact with this, and from this release onwards that functionality is dropped.

Housekeeping, improvements & fixes

Various small improvements and fixes have made it to the release.
Some of the improvements:

  • Major refactoring happened "under the hood" in the sentry network.
    This enabled fixing issues related to Case File Items of type array.
  • Duration parsing has extended
    • Every task that has a due date set now also carries a duration, based on the due date of that task.
    • It is now possible to give both a fixed date & time as well as a duration to timers, and also to task due dates.
  • More migration scenarios are now supported.
  • Low level log messages have been improved on clarity and readability.

Tickets closed

TicketDescription
#562EntryCriteria listening to both 'update' and 'create' fails after bootstrap events have been released
#566Case Migration should be more friendly on comparison of references to CaseFileItems (in expressions and parameters)
#576TimerEvent should not recalculate targetMoment upon resume
← 1.1.431.1.41 →
  • Dependency updates
  • Less events
  • Less storage
  • Better performance
  • Housekeeping, improvements & fixes
  • Tickets closed