IDIOM Transaction Engine

IDIOM Transaction Engine

A complete digital platform, already optimized for decision centric transactions, and ready to plug-in the business algorithm – a few other configurations and adjustments, and deploy as a finished application for any domain in 100days, guaranteed!


Deploy into Azure PaaS, RedHat OpenShift, a Virtual Machine, or any combination. Totally secure, totally agile, web enabled, unlimited scale, highly configurable business transaction processing.



 IDIOM Transaction Engine: best practice integration of IDIOM products in a complete Digital Platform



  • Admin Portal for domain users to manage the system and access all back-end and Admin functions
  • Dashboard Portal for third-party business intelligence tools and reporting
  • Public Portal for non-domain users – password-less, authenticated user access, and anonymous users
  • IDIOM Dialog Manager for decision-controlled conversations with mobile form factors – very large business concepts managed in very small sound-bites configured for mobile devices
  • IDIOM Forms for large and complex webforms that are decision-enabled with large scale algorithms and decision-controlled field visibility and functions. Very large business concepts – thousands of input fields, dozens of tabs, 100s of decision events – for fast, interactive use by expert users
  • Batch Jobs (webjobs) for file passes and asynchronous processing of inbound/outbound records
  • Data agility is achieved using schema defined ‘Entity XML’ to hold the entity data, stored in a single XML table/column – a million or more nodes per entity is routine, with the RDB providing indexes and generic supporting data that includes workflow, communications, history, and decision models
  • The Core has exclusive ownership of and access to the Entity XML, for security, integrity, and consistency
  • The Core uses decision models to manage overall workflow, including external integration services, future dated bring-ups, operator tasks and interventions, workflow monitoring
  • Service Adapters provided for a wide variety of realtime or asynchronous integration end-points – web services, queue services, bespoke services, file management
  • IDIOM Document Generator is used to generate correspondence and agreements for customers and third parties under the control of decision models; plus, emails and SMS. All automatically composited, sent, indexed, and archived by the Communications Handler
  • Scheduler for automated operations
  • Process state is held in a meta document, so every component is stateless, can scale without limit


Pivotal role of the Core:

  • Single Point of Control – only the Core can:
    • decrypt/encrypt the context data, which is the Entity XML that describes the business entity, their products, and all their related data
    • change the state of the Entity XML using IDIOM Decision Models
    • transform the Entity XML (inbound/outbound) for use by non-core actors, including dialogs, forms, documents, and integration services
  • Fully Automated Workflow – For each and every state change in the Entity XML, the Core will be directed by IDIOM Decision Models to:
    • record a complete before and after history, process logs, user and system level activity logs, and generate and distribute documents
    • update all human and future system tasks, send communications to all parties, and update database, incl. reporting and search meta data
    • Support the digital integration hub by generating and managing update vectors for all first order related systems, internal and external e.g. legacy, financial, regulatory, management, intermediary, reinsurer, other third-party systems