Integration Framework Designer
The topics in this
You can create Integration flows in Event Designer under a project of type T24 Integration Project and you store the artefacts as XML documents with .event and .flow extensions.
Editing Flows Without Using Event Designer
Integration Framework provides various exit points to capture business events and data events. Each exit point has associated flow. These flows defines the data to capture and the parameters that defines where to route the captured data, priority of events, etc. To edit the flows, one need Event Designer including the parameters that require changes based on the deployments. Event Designer is licensed and Designers are not allowed in production environments. This section shows you how to edit flows without using the event designer.
Using Conditional Event Generation
Conditional Event Generation is an option in Integration Framework that holds a set of conditions based on which an integration event can be saved. When you publish a flow, an IF.EXIT.EVENT.FILTER record is created for that particular flow. If any of these conditions are evaluated to be true, then the records are not created in IF.EVENTS.INTERFACE.TABLE.
Enriching Integration Events with Temenos Transact Subroutine or API Results
You can create an API definition based enrichment for any exit point except for Inflow.
Defining and Using Custom Common Section Values
Integration Framework allows events to contain the EventCommon section in the event XML file. The feature has a customizable event common subsection in Integration Framework event XML where additional system-wide data can be set and further used when processing the events.
Defining and Using a Complex Join Feature
Integration Framework allows flows to be designed with join definitions to enrich events with data from relevant tables.
Defining an Event for an Activity or Activity Class
Activity or Activity Class exit point type allows you to define an exit point for AA Activity or Activity Class.
Defining Events for a Component Service
This section describes how to define and trigger events for a Component Service (EE).
Defining Events for a TSA Service Exit Point
Use Event Designer to define events for TSA services. The Events can be linked to TSA services to emit messages from Transact during COB or by using services.
You can create an exit point to support event capture for D, L, W and T type of files and also for any AA Application or version except AA.ARRANGEMENT.ACTIVITY and AA.SIMULATION.CAPTURE.
Creating Banking Framework Events
Banking Framework Event exit point type allows you to define exit point for a Banking Framework event.
Defining an Event for Delivery Message
The first step to support MX ISO20022 messages is to define a delivery exit point using Event Designer. This section provides steps for defining an Event for Delivery, an option that is added to support triggering events for MX messages.
External systems needs signals from Transact to start some processes. These signals need to be triggered.
This section explains how to define the integration events from the delivery module of Transact.
Deleting Events and Flows from Transact Using a Command Line Utility
This section describes how to delete events and flows from Transact using a command line utility.
Posting Transact Messages Directly to the Queue
When you design a flow, you have the option in Event Designer to Post Directly to Queue.
Defining and Using Outward Landing Table
The IF.OUTWARD.DESIGN.LANDING table can be defined for any exit point type. This table is used as a source table for Workbench event designer and also becomes a source for IF Events and flow packaging without making the IF.EXIT.POINTS and IF.INTEGRATION.FLOW.CATALOG table editable.
In this topic