CaseFabric Reference Guide

CaseFabric Reference Guide

  • Overview
  • Getting Started
  • CMMN
  • CaseFabric IDE
  • CaseFabric Engine
  • Extensions
  • API Reference
  • 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

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

Cafienne Engine Release 1.1.11

Maintenance Release - with some hidden gems

Version 1.1.11 is mostly a maintenance release. The Cafienne team has been busy with many smaller topics inside the engine and also some refactoring work in the Cafienne IDE. Nevertheless, this release ships with some interesting new features.

Dynamic classpath

The Docker image that is shipped with every release has been extended with a new classpath setting. This setting enables the creation of a directory external to the image in which you can add custom jar files that need to be loaded by the engine.

Publishing the jar files to Maven

From this release onwards, jar files of the Cafienne engine are published to maven, thereby enabling the new classpath feature to support custom implementations of e.g. process tasks or expression languages.

New Mail definition with support for iCal

The former SMTPCallDefinition class has been superseded by a new MailDefinition class that has better support for addressing mail messages to multiple recipients. In addition, the iCal4j library has been added to the Cafienne dependency chain enabling you to send out calendar invites from the MailDefinition process tasks. Last but not least, the mail server properties are no longer required inside each and every mail task, but instead can be configured once in a platform wide manner, including authentication to the mail server with user name and password.

Important - check the getting-started repository for an example configuration change

More CMMN1.1 compliance

  • The Cafienne now registers the default expression language set at the level of the <definitions> tag.
  • Input mappings now support binding refinements to have more control over repetitive plan items in relation to case file items with multiplicity 0..* and 1..*. Furthermore, it is now possible to pass a case file item by reference instead of by value, which is a recommended pattern for HumanTasks.

Explicit mappings for task failures and task completion.

In CMMN, the parameter mappings to be executed upon task completion or task failures is a straight list. This behavior has been extended to support exclusive mappings for either task completion or task failures. E.g., if a task fails and one of the expressions in the mappings relies on the output to succeed can now be separated out and prevented. Furthermore the engine now supports setting "static" output parameters, i.e., define and fill task output parameters even if the underlying task implementation does not hold the a corresponding output parameter. This functionality can be used to e.g. put a timestamp with the task completion date in a case file item.

Housekeeping

  • Internal build street has been extended to run more compatibility tests.

Tickets closed

TicketDescription
#172TaskCount should not include Completed and Terminated tasks for unclaimed
#173Filter on taskName is required
#174Filter on caseName is in API, but is not implemented
#178It should be possible to do conditional mappings for process task
#179User_role table misses index
#180Case engine chokes on CaseFileItem child output
#182When mapping multiple output properties to the same case file item, it is not reflected in the case file
#185Repeating task on case file item creation cannot map item's children in input mappings
#191When user is in many tenants, warning log message for wrong tenant is too large
#196Akka route concatenation has issues
#198TimerService should be more lenient to non-parent-subcase-team-members
← 1.1.121.1.10 →
  • Dynamic classpath
  • Publishing the jar files to Maven
  • New Mail definition with support for iCal
  • More CMMN1.1 compliance
  • Explicit mappings for task failures and task completion.
  • Housekeeping
  • Tickets closed