CaseFabric Reference Guide

CaseFabric Reference Guide

  • Overview
  • Getting Started
  • CMMN
  • CaseFabric IDE
  • CaseFabric Engine
  • Extensions
  • API Reference
  • Releases

›Some CMMN

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

CaseFabric IDE

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

CaseFabric 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

Releases

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

Other things to model

Discretionary items

In CMMN, a Discretionary Item identifies a Plan Item of which instances can be planned to the “discretion” of a Case worker that is involved in planning. Only Stages, Human Tasks and Case Tasks can be discretionary. You can attach an Authorization Role to an Discretionary Item, being the Roles that can plan the item.

Also, a Discretionary item can be Non Blocking, meaning that it is not waiting for work to complete and completes immediately, upon instantation.

Discretionary items are part of the Planning table of the Stage or Case in which they are modelled. The Planning Table can be restricted by Applicability Rules. Applicability Rules contain a Case File Item and an Expression.

In CaseFabric, you can model Human Tasks, Case Tasks, and Stages as Discretionary using the Properties Palette; you can also model it as Non Blocking. Once you modelled a Discreationary Item, the Planning Table icon is shown in its parent Plan Item. Clicking on this icon, you can add an Applicability Rule.

Sentries

In CMMN, a Sentry “watches out” for importants situations to occur (or “events”) which influence the further proceedings of a Case. In CMMN, important situations to occur are a lifecycle transition of a Plan Item or a Case File Item and the triggering of Event Listeners. In this way, a Sentry allows us to describe when a task, stage, or milestone should be available for execution (entry criteria), or when a case (case plan), stage, or task should terminate abnormally (exit criteria).

In CaseFabric, you can drag Entry and Exit Sentries from one item to another item. In its properties, you can declare an On Part and an If Part. In the On Part you can select an Plan Item and/or a Case File Item and one of their lifecycle transactions. In the If Part you can select a Case File Item and express an Expression​.

Sentries can be used for plan items as follows:

Sentry Case Stage Task Milestone
Entry √ √ √
Exit √ √ √

Expressions

In CMMN, you can add to parameters Expressions. Expressions are String objects. Expressions operate over Properties and Case File Items in the Case File.

In CaseFabric, you can express your Expressions in Spring Expression Language (SpEL).

← Modelling the Case TeamAn IDE? →
  • Discretionary items
  • Sentries
  • Expressions