Developing

You can extend your IBM® Counter Fraud Management system to meet your business needs. For example, you can define your own fraud detection analysis, import actual data from your own system, or use the REST API to extend the Counter Fraud application.

IBM FCI Data Model Export
Building a fraud detection analysis
An analysis flow for IBM Counter Fraud Management, including analytics, registration, and assessment actions, occurs in three core areas of Counter Fraud: Data, Analysis, and Action.
Importing data into the IBM Counter Fraud Management system
IBM Counter Fraud Management uses the data from your environment and systems as the object for analysis, scoring, and subsequent action. The data that you choose to manage and how you map it into ICFM is a key factor in the effectiveness of your Counter Fraud application.
Implementing detection in ICFM (Analysis)
An analysis flow is invoked by the ICFM Analysis Director that is responsible for invoking the correct analysis flow for the data that is imported, or ingestion notification received. The Analysis Director then performs a specified set of analytics and produces a set of assessments.
Using the Data Import command line tool
Use the Data Import command line tool to automate the import of data into the Counter Fraud Management system. To begin, you must create a mapping file for the data that you plan to use during the import operation. Data Import can import data from CSV files, or directly by using a JDBC connection from a remote database, such as an Oracle database.
Working with business objects
The IBM Counter Fraud Management database tables and columns might not have names that reflect the industry that Counter Fraud is configured for. Business objects provide a method to define a mapping structure to the Counter Fraud database tables.
Publish/Subscribe messaging
Creating custom actions
You can create and implement actions and action handlers to provide custom actions for investigations in IBM Counter Fraud Management.
Restricting state transitions by using parent-child relationships
As an investigation moves through its lifecycle, the state of the investigation changes. You can create custom action handlers that use parent-child relationships to restrict state transitions.
Creating tasks automatically
You can create system-generated tasks when an investigation's status matches a specified state. You use the cffolio.assignment_template to create the tasks.
Calling secure ICFM REST services from IIB flows
You can configure a message flow to ensure secure connections. This process includes configuration for the message broker and developing the message flow.
IBM FCI REST API
Counter Fraud REST API
Creating a content pack using the mkcp utility
A Counter Fraud content pack, also known as a Counter Fraud Archive (CFAR) file, is a container (compressed file format) that is used to distribute one or more Industry UseCases (IUCs). An IUC provides the solution for an industry-specific or client-specific Counter Fraud scenario, and is designed to plug into the extension points of an ICFM client implementation.