CaseFabric Reference Guide

CaseFabric Reference Guide

  • Overview
  • Getting Started
  • Training
  • CMMN
  • Case Designer
  • Case Engine
  • Extensions
  • API Reference
  • DCM for Mendix
  • Releases

›Training

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

Training

  • Introduction
  • Obtaining the CaseFabric Demo
  • Chapter 1
  • Chapter 2
  • Chapter 3
  • Chapter 4

Some CMMN

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

Case Designer

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

Case 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

DCM for Mendix

  • Overview
  • DCM Add-On Architecture
  • Design Case Models
  • Interact with Cases
  • FAQ
  • Releases

Releases

  • Overview
  • 1.1.38
  • 1.1.37
  • 1.1.36
  • 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

Chapter 3: Case Team

Use Case Step

Until now, we have tested our model with a single user. However, searching the house is obviously done by someone from the Civix organization. Taking the decision on acceptance of the proposed house must be done by the client. In general, we see that most cases are worked on by a group of people collaborating to complete the case. This group of people is referred to as the Case Team. Every case instance has its own case team. This means, that for each house search we should also assign the team of people that will work on the case.

lijn

Step 1: Filling the case team

Solution support step

Add multiple users to a case

Start a new case, and then click on the “Team” tab

teamtab

In this tab, we see all the users that are in the team that work on this case. This is only Lana.

caseteamlana

Suppose we want to also give access to our colleague Hank. He can help Lana to divide the workload. Let’s first logout as Lana and login as Hank, with username “hank” and password “hank”.

logoutlana

loginhank

We see that Hank has no cases. The reason for this, is that Lana did not add Hank to any of the cases yet.

nocases

Let’s add Hank to a case. For this we need to login again as Lana, start a new case and navigate to the Team tab. In the “Case team users” section, we see a drop down where we can add Hank to the team, and press the Submit button

caseteam-users

If this is completed, we can login again as Hank, and now we see the case as well.

hankcase

lijn

Use Case Step

We have seen that we can add multiple users to the Case Team. Now we need to add roles to the users in the team. Not all users can do all tasks. Civix employees enter the client details and search a house, but the client has the task to accept the house.

Step 2: Defining Case roles

Solution support step

Defining the different responsibilities in a case can be done by setting up Case Roles.

Open the case model and go to the Case Team halo.

caseteamhalo

Add a role named Employee, and a role named Client.

employeeclient

Deploy the case and update the definition of the existing case instance. The case then understands the new roles that are defined.

updatedefinition

lijn

Step 3: Assigning Case roles

Solution support step

Assign a role to a user in the CaseTeam.

Let’s assign the Employee role to both Lana and Hank (note: this can only be done by Lana as she is the case owner. So you should be logged in as Lana). Go to the Case Team tab, add the role Employee to both Lana and Hank, and press the submit button. Note that the role names are case sensitive.

employeerole

We can also make the client part of the case team. Let’s assume suzy is the client. So we will add Suzy to the case team, with the Client role. Then press the submit button.

clientcaseteam clientcaseteamsubmit

lijn

Step 4: Applying Case roles in Tasks

Solution support step

Setting the HumanTask Performer role.

In the case model, we can now start using the case roles to determine task authorizations. Go to the workflow properties of the task “Enter client details”.

performerrole

In the dropdown of the Performer property, we can now select the role “Employee”. By doing this, we ensure that the task can only be done by users in the team that have this role.

performerroleemployee

We can do the same for the other tasks in the case model. Add the role Employee also to the task “Search house”, and the role Client to the task “Accept house”.

lijn

Chapter 3b: 4-eyes principle

Use Case Step

In some situations, two different tasks must be done by different users – even if they have the same role within the case. This is referred to as the 4 eyes principle. It takes 4 eyes to complete the work. In our example, we will simply say that the Employee that enters the client details cannot also search for the house.

lijn

Step 1: Defining 4 eyes on tasks

Solution support step:

Define 4-eyes on the combination of “Enter client details” and “Search house”.

Open the workflow properties of both tasks. If the popups overlap, you can move the popups a bit to show them next to each other.

workflowproperties

On the task “Enter client details”, check the 4-eyes box. This will show a list of other tasks in the model that you can select.

4eyesbox

Select the task “Search house” as 4-eyes with this task. When you do this, you will see that at the same time, 4-eyes got enabled on the task “Search house”, and automatically the ”Enter client details” task was selected.

taskselect

Try to run the case and play with how the 4-eyes principle works.

← Chapter 2Chapter 4 →
  • Step 1: Filling the case team
    • Solution support step
    • Use Case Step
  • Step 2: Defining Case roles
    • Solution support step
  • Step 3: Assigning Case roles
    • Solution support step
  • Step 4: Applying Case roles in Tasks
    • Solution support step
  • Chapter 3b: 4-eyes principle
    • Use Case Step
  • Step 1: Defining 4 eyes on tasks
    • Solution support step: