CaseFabric Reference Guide

CaseFabric Reference Guide

  • Overview
  • Getting Started
  • 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

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

Extended Migration Support

This release has extended the support for migration of case definitions on running instances

More migration support

The case engine is now able to detect plan items such as Tasks, Milestones or Stages that have moved into a different area of the case plan. A typical use case scenario is a case that started with a relatively simple HumanTask to do an intake, but over time the intake appears to be a somewhat more complex phase with multiple tasks is better expressed in a stage. Migrating running cases with an active Intake task now preserves the state of that task, whilst moving it to the newly introduced stage.

Also the other way around is possible, where a task is moved from a stage to a higher stage because it should be available earlier and perhaps in more places.

Housekeeping

Traditional housekeeping has taken place as well. We love a clean house.

Tickets closed

TicketDescription
#504Changes to LastModifiedRegistration lead to timeouts
#506Upon case migration, repetition rule should not be triggered again
#508During migration when a task no longer is repeatable, it crashes in StageAPI with NullPointerException
← Overview1.1.37 →
  • More migration support
  • Housekeeping
  • Tickets closed