PlatformApplicable to all products in Temenos Journey Manager. | All Personas | All versions This feature is related to all versions.
Temenos products support the separation of core products and client specific code via an Extensibility Framework.
An Extensibility Framework provides a clear delineation between core product and customizations. With a clearly defined boundary, Temenos can better support customers (does a fault lie in the core product?), as well as provide a simpler upgrade path (platform code is never modified).
Our customers benefit from the reduction in ambiguity this approach brings and enjoy operational benefits of by consuming new product features at a lower cost of upgrade.
Extensibility needs to be considered for Forms, Workflow, Services and Solutions provided by Temenos.
At its heart, Journey Manager is a smart form platform. Clients can create smart data collection journeys using Journey Maestro or OpenUX.
Any Form that is not packaged with Journey Manager is an extension. Forms that are neither created nor controlled by Temenos are not supported by Temenos.
Product Workflow is implemented via the Collaboration Jobs feature in Journey Manager. This often works in conjunction with Workspaces environment views configured for bank staff, applicants, and third-parties (brokers, for example).
Form Workflow is implemented via the Narratives feature that are managed by the by the server Narrator Service.
All these features are configured, not coded. Configuration is achieved using JSON definitions and the development artefacts are managed as a part of the development lifecycle of the form.
Any Collaboration Job, Workspace or Narrator that is not packaged with Journey Manager is an extension.
A Service is code written in the Groovy language, that runs on a Journey Manager server that provide small, self-contained, time-bound functions in a system. An example service might deliver a form payload to a RESTful API endpoint provided by a client.
Services are a fundamental part of the Journey Manager platform. They come in many flavors and support a wide range of features.
Services are implemented in Groovy because it allows Temenos to implement a range of security restrictions including:
Core services provided by Temenos are written and packaged as Groovy Services and are therefore subject to these security restrictions. There are many examples including Security Managers.
Any Service that is not packaged with Journey Manager is an extension. Services that are neither created nor controlled by Temenos are not supported by Temenos.
Journey Manager is sold to clients in two ways: as a standalone platform for building onboarding journeys; and, as a packaged solution for a particular banking need.
Packaged solutions are feature complete solutions that include Forms, Narratives, Collaboration Jobs, and Workspaces definitions. Theoretically, these products can be deployed and are usable out-of-the-box, although in practice, as a minimum, integration Services are required to deliver data payloads to downstream systems and, often, clients change form item order or make more substantial changes.
Temenos encourages clients to use these solutions as accelerators. Extensions follow the model already described for Forms, Workflow, and Services. These are delivered as supported features by Temenos.
Modifications are the purview of clients and are not supported by Temenos.
The limited set of APIs available to extension developers balances the needs of developers against requirements for security, operations, support, etc.
The clear demarcation provided by this framework also provides a foundation on which upgrades can be safely and efficiently undertaken. Temenos provided APIs, Forms, Services etc., are supported during the normal product lifecycle, however some APIs and features will be deprecated or removed as the platform evolves.
Next, learn about the complete range of software development technologies and programming languages you can use in our platform.