Before a case manager can be used by the X Engine and the console, it must be defined. This involves creating queues, status codes, list values, fields, selections, actions and tasks. It is relevant to mention this here, so that it is clear that the case manager described in this section is just one of many examples of how your specific case manager may be defined.

Defining a case manager can only be performed by an administrator. There are two ways to undertake this task: Setting it up manually through the console or importing an existing definition.

A case manager definition can be exported so that it can be used with other case managers. This may, for example, apply if you have one case manager per application, country or company division. Exported definitions can be downloaded and shared between consoles. Please see the section “Creating a Case Manager Definition” later in this manual for more details.

Composable Architecture Platform contains a flexible case manager to allow organizations to have a complete fraud and security solution. The console can control one or more of these case managers at once. Each case manager is stored in a database that must be simultaneously available to both the console and the X Engine.

To view the task on a given queue, simply click on it in the administration tree below the case manager.

In this list of tasks, those with no “Due for action” time are due immediately. Tasks that are assigned mean that someone has picked up that task and not yet returned it to the queue or completed it.

The in-built case manager in Composable Architecture Platform is intricately linked to the flight recorders. When a case is created by a rule, a flight recorder entry is always added too. If you need to have the system automatically collect additional flight recorder data for a case, you must use the Flight Recorder Add rule.

Other than that, the Case Manager Trigger rule is used in precisely the same way as the Flight Recorder Trigger rule.

The following shows a typical set of properties for a Case Manager Trigger rule:

The Case Data Base Name maps to the name specified in the configuration. Secondly, the initial task and queue for that task refers directly to IDs of those defined for the case manager. If you are creating rules and are unfamiliar with the defined tasks and queues, you will need to ask the system administrator to provide you with the task and queue names to use.

The optional field descriptions and case fields are a CSV list of fields and variables that are featured when the case is opened for review. These fields will also show in the flight recorder data, but through this method you can highlight them to the analyst reviewing the case.

If you are familiar with the Flight Recorder Trigger rule, you will notice that the last 8 parameters in the Case Manager Trigger map directly to it.

As an alternative to creating cases from the X Engine, you can create them manually through the console. From the case manager, click on Add Case.

You will get the option to add a new manual case, with a description, a customer ID, an initial task and a queue for the task.

A manual task will not be linked to any flight recorder data, so it is imperative to supply as much information as possible on the initial task and complete it immediately.

To complete a task, you must enter some basic case notes and complete all mandatory fields (marked with a “*”). You must then select an action to perform and click the Submit button.

If for some reason you are unable to complete the task or wish to move it to another queue (possibly a personal one or a queue that is assigned to an investigative specialist), then select a queue for the task and click on Return to queue.

You can also save a draft, which is useful if you are working on a case and need to leave it for some reason. The draft will store any text and field information already entered.

Once case managers have been defined, they are available in the administration tree, provided the user has authority to access them.

Below each case manager database are the queues for that case manager and the number of tasks pending on that queue.

To navigate the system, either click on the case manager itself to get the search functions, auto-pick and case creation options, or click directly on the queues to see the pending tasks.

Clicking on the link to the case number will display the case. We will discuss this a little later in this section.

From the case manager you can search tasks currently due.

Complete the search fields and click on Search. The result page will provide a result of all tasks across all of the queues.

You can pick a task to work on by selecting it directly from the queue. An alternative and better way is to auto-pick it by clicking on Next Task in the case manager.

Once you pick a task the case view will be presented.

This view gives you a summary of the case, when it was created, and the flight recorder data associated with it (effectively all of the variables visible in the X Engine at the time the case was created).

The job now is to complete the task and select an action to perform.

Once a task has been completed, it is added to the case view as history. The history is listed in descending order, meaning that the most recent history is shown at the top.

Importantly, you can edit the history of the tasks performed by clicking on the edit button for each task, which will go to the task history revision page.

Here you can alter any details that might have been mistakenly provided. However, an audit trail will always exist for the modified entry and in the case view a note will show that the history has been revised.

In addition to tasks, you can also search cases. This is typically to provide an update to a customer, police or legal counsel about the status of a case.

You can search on any of the criteria shown below:

The result will show the cases and their status.

From the case search you can go directly to the case view, but you will not see any pending tasks.