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.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.41

Cluster Support

The case engine has always trusted the powerful runtime provided through Apache Pekko. This release enables more and more of the powerful features inside Pekko.
Most significantly the case engine now features support for clustering through Pekko.
If you want to use this option, do not hesitate to contact us for support. Clustering with an actor model driven system requires specific configuration settings.

Robustness

Error handling on instable and changing network connections has improved. The restart settings that can be configured inside the engine are now not only applied on the event journal, but also for connectivity issues in the query part of the house.

JDBC Database support

The Case Engine relies on JDBC databases for queries, and leverages the configurable Pekko persistence plugins for event journaling. The engine is tested against a number of combinations upon every commit. Specific testing is done with PostgreSQL and Microsoft SQLServer as query database. The testing is now extended with support for the Oracle database system as well.

Tickets closed

TicketDescription
#557When an case command does not lead to state changes, it should not store the debug event asynchronously
#560Projections do not recover when there is something wrong outside the source that is already wrapped with a Backoff.
← Overview1.1.40 →
  • Robustness
  • JDBC Database support
  • Tickets closed