Cafienne Reference Guide

Cafienne Reference Guide

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

›Releases

Overview

  • Cafienne
  • A short introduction
  • Product Overview

Getting Started

  • Introducing Cafienne Demo
  • Generic UI
  • How to use task UI rendering
  • Two business applications
  • Obtaining Cafienne Demo

Some CMMN

  • What is CMMN
  • Modelling the Case Plan
  • Modelling the Case File
  • Modelling the Case Team
  • Other things to model

Cafienne IDE

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

Cafienne Engine

  • The Cafienne Engine
  • Authentication
  • Authorization
  • Pictorial overview
  • Logging
  • Configuration
  • Repository

Extensions

  • Do we need extensions?
  • 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.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.19

Fixpack

This release primarily holds a couple of fixes for the Case Team APIs with respect to consent group membership.

Furthermore this release holds a little extension on process task input mappings.

Richer sub process input mappings

Process task implementations, such as HTTPCall and MailDefinition expose string based parameter substitution. This has been extended with support for SPEL expressions. If the engine finds a string substitution ${ ... } it will try to parse the contents as a SPEL expression, and as an alternative provide the string value of the parameter.

Tickets closed

TicketDescription
307It must be possible to apply spel expressions on process task input parameters
308When sending invalid command types to a ModelActor, it should kill upon recovery
311BootstrapPlatformConfiguration gives unclear message when a tenant already exists
312CommitEvent should not be generated if it is already available
314Replacing case team consent group membership fails
315Replacing case team consent group membership does not validate group existence
316Replacing case team consent group with empty json leads to null pointer exception
317GET CaseTeam response has invalid content on consent group members
319Engine breaks on missing serializer for new response type ActorExistsFailure
← 1.1.201.1.18 →
  • Richer sub process input mappings
  • Tickets closed