CaseFabric Reference Guide

CaseFabric Reference Guide

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

›DCM for Mendix

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

DCM Frequently Asked Questions

Supported databases

In order to use the DCM module, you need to have Postgres (preferred) or MS SQL Server.

Start Case cannot find my case

When you create a new case model and want to use it, you need to Deploy the model inside the DCM editor. See Deploy the model for all the details. Note that you do not need to restart after pressing the deploy button.

WaitFor issues

You cannot use the WaitFor token in the same transaction

When a WaitFor action is used, you use the WaitForToken returned by a previous java action. These java actions change the state of the Case Instance and need processing time to handle the transaction in full.

The microflow responsible for calling a java action that changes state cannot contain the WaitFor java action. When you call both in the same microflow, they will execute in the same transaction. That results in a block inside the DCM module and the WaitFor will timeout.

You have to use the WaitFor in a separate transaction. When you build user interface components, use a nano flow that calls the microflow with the state changing action and another nanoflow that will execute the WaitFor action.

The Testframework can be used in a way that it starts a separate transaction in a microflow. Take a look at the documentation on Unit Testing.

← Interact with CasesReleases →
  • Supported databases
  • Start Case cannot find my case
  • WaitFor issues