Components Overview

Temenos Infinity consists of a wide range of Fintech apps that provide customers with a single experience platform using open APIs and extensible architecture. These apps provide analytics to understand customer behavior and improve customer outcomes. All while reducing the speed-to-market in a boxed solution with flexibility to bring products and digital solutions to the market in a matter of months.

The apps are customized for the clients based on their business requirements. While the apps can be customized rapidly, Temenos Infinity keeps looking for ways to improve the ship-to-market timelines.

There are two types of components:

• Components with a contract.
• Components without a contract.

Components with a contract use the Quantum Visualizer Reference Architecture: a structured, modular framework based on the Model-View-Controller (MVC) architecture.

The contract is a JSON file that specifies the component's exposed properties, events, and methods. You can specify those properties, events, and methods within the Visualizer interface, and then define the behavior of custom properties, events, and methods by adding code to the component's controller module.

Infinity Components

Infinity components are the building blocks of the digital banking application. These are self-contained entities that represent a business module such as accounts, transaction details, beneficiary management and login. They support dynamic and responsive user interfaces across multiple channels – mobile, tablets, and desktops.

These are components with contracts, that control what is exposed to users of the component. Only the properties, events, and methods are exposed to the implementation partners, enhancing the ability to rapidly customize and implement Infinity for different clients.

Components bring down the development hours spent on customizing screens.

A Component Contract consists of four parts.

• Properties: Properties are used to define the behavior of the component and its user interface.
• Methods: Methods are used on a form or in other components to interact with the component.
• Events: Events are generated on a component and can be customized by the implementation teams to define the business logic and to program what happens in such events.
• Context: Context contains contextual object passed to the component.

Digital Banking components are two types:

• Business Components: Represent a business module with a pre-defined set of contracts using which, implementation teams can modify the behavior of the component such as Data Mapping and Formatting among other things
• Utility Components: Building blocks to design business components or a larger component with a higher purpose or used directly on a form.

Benefits to the implementation partners with components

• Zero to minimal code change: During implementation, components enable the developers to configure the required customizations, through the exposed properties, with zero/ minimal code changes
• Easy upgrades: Components has predefined user experience templates. It enables clients to pick an experience from the predefined templates rather than defining a new UX which might break the upgradability of the app. There by reducing the implementation cost & also preserves the easy upgradability of the app

The sub-sections in this guide will provide more details on Components and how to use them.