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

Case Engine Release 1.1.35

More multitasking

This release brings a major extension to the Task API for case instances. Furthermore it comes with some internal refactoring, small bug fixes and enhancements.

Extended task information on cases

The API to fetch tasks for a case has been extended to include a lot more usable information. It is now possible to read tasks from not just the case, but also from all subcases of that case - provided the user has access to the subcase. Furthermore, a new property mayPerform is added to each human task, indicating whether the user has the rights to perform the task.

Housekeeping

The core engine architecture consists of 2 major components. First and foremorst the pure case handling, and in addition the tenant registration. The tenant registration is intended to support the precise authorization structures in the case handling. In most use cases such a registration is also done outside of the engine, and this leads to cumbersome data duplication. This release prepares a next step to make the registration more pluggable to avoid data duplication.

Tickets closed

TicketDescription
#476Empty case plan name causes NullPointerException when starting the case
#478Creating a case gives an weird error "Cannot access a property ..."
#482Cannot find a consentgroup with id...
← Overview1.1.34 →
  • Extended task information on cases
  • Housekeeping
  • Tickets closed