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

Maintenance Release

Version 1.1.12 has a few additions that help mostly in the every day detail.

This includes topics such as more informative log messages, a better and more explicit API for usage inside expressions. Also a few new features such as support for anonymously starting cases. And a couple of detailed issues have been solved, such as adding an additional CORS related header in the HTTP traffic.

Experimental: Calculation Task

Some use cases require changes to the case file and the case plan based on certain conditions. E.g. a case file item array must be updated conditionally, depending on the outcome of a certain task. Until now, this required either extremely complex expressions (using engine internal APIs), or the creation of separate end points that can be invoked through ProcessTasks invoking HTTP endpoints. The new experimental Calculation Task can be invoked as a regular process task, but without any external dependencies. The task takes an arbitrary number of input parameters and produces output parameters based on a set of steps that run expressions on the input parameters (or the outcome of other steps). Output parameters are produced on a conditional basis, enabling simpler decisions in the case plan.

Start Case Anonymously

Most of the REST services API of Cafienne require authentication through the OIDC standard, with JWT tokens. In quite a few scenarios (e.g. a government portal where citizens can submit certain applications), the user requesting the case need not be part of the actual handling of the case, let alone be registered as a Cafienne Engine user. Through a new configuration option it is possible to start case definitions anonymously. Each type of case that can be started is given an identifier on the end point, and each type can configure it's own case team.

New Expression API

The CMMN enables the use of expressions in many different places, such as repetition rule conditions, or parameter transformations. The Cafienne Engine leverages the powerful Spring Expression Language (SPEL) as the default implementation (next to a few others). Up until this release, the SPEL language could be used to access engine internal APIs. From version 1.1.12 onwards, the internal API is no longer available, and replaced with a formally supported API to access e.g. a case id or a task id. More information on this new feature can be found in the expressions section of the Cafienne Guide

Tickets closed

TicketDescription
#203CaseAppliedPlatformUpdate event handling should also update the case_instance_definition table
#204Restarting an earlier failed ProcessTask should not have old exceptions in the output
#207It should be possible to complete an unassigned task
#208Case output parameters that refer to an array case file item must return complete array instead of current
#213Engine must return Access-Control-Expose-Headers
#215GetTenantUsers must not include in-active roles
#217Milestone transition behavior is executed in the wrong order
#219New expression API gives wrong Stage for a Task
#222Swagger documentation for setting case team is wrong
← 1.1.131.1.11 →
  • Experimental: Calculation Task
  • Start Case Anonymously
  • New Expression API
  • Tickets closed