Process-controlled interaction between systems

Workflow instructions, workflow-controlled communication between systems, data transfers, process synchronisation, using WebService and MQ services

Process-controlled interaction between systems

Some complex processes may require information from different systems of the company and certain workflow steps may need to perform activities in other systems. For this reason, the case management system must interact with other systems, typically in line with a SOA architecture. CRAFT supports several tools which enable inter-system communication. The most frequent forms of such communication are WebService calls, messaging via WebSphere MQ and communication through database tables. In addition to using these as a basis to implement custom system connections, the system also offers tools enabling the principal to define and to set up parameters for inter-system messages, which can then be used to initiate data transfers and data queries from the workflow or to implement points for synchronisation with workflows running in other systems.

Features

  • Transfer or receive data based on WebService calls
  • Transfer or receive data based on WebSphere MQ messages
  • Transfer or receive data through database tables
  • Messages can be defined by the principal's staff
  • Mandatory data transfers can be defined for workflow steps
  • Transfer data generated during administration
  • Transfer data included in initial documents and product folders
  • Mandatory data queries can be defined for workflow steps
  • Waiting for messages from other systems

Advantages

When managing cases launched in connection with a document, all necessary data can be conveniently entered based on the document image and can be automatically transferred to the systems processing them.

Data required for administration and available in other systems can be queried easily, without having to access these other systems.

Administration workflows can wait at certain points while activities to be performed in other systems are completed, and then they can automatically resume when those activities are finished.

Workflows requiring the interaction of multiple systems can be implemented without involving the developers.

General features

  • Bespoke solutions
  • Reliable systems tailored to the needs of financial institutions
  • Processes and data content can be designed by the principal
  • Solutions working closely with other systems used by the company