07/10/2024 18:30 Defining the flow

You are here: Enterprise Frameworks > Integration Framework > Event Designer > Creating exit points in T24 using Event Designer >
Defining the flow

file:///D:/Temenos/R19 AMR Documentation/R19ID.htm#../Subsystems/R19TechUG/Content/Integration Framework/User Guides/Event Designer/… 1/5

07/10/2024 18:30 Defining the flow

Defining the flow

Click on the 'Flow' tab, to define the fields which holds the data that has to be sent out of T24. In the 'Flow name' field, specify the name for the
flow and click 'Edit'. Click on 'Browse' to attach an existing flow to the event.

Note: Attach only valid flows to the integrator. For example, attaching a FundsTransfer flow to a Teller version will result in a publish error, as the fields in
FundsTransfer are not be available in Teller.

Based on the Application/Version selected in the exit point, a list of all the fields in STANDARD.SELECTION is displayed in 'Field' box. Required
fields can be selected from the list. The selected fields appears in the Table section of the screen. The XML representation of the Table can be
viewed in the 'Source' tab. This XML file is an expert view of the project file.
A custom field can be used to define the event delivery options.
Click 'Add', to add the selected field to the flow.
Click on ‘Add All’, to add all the fields to the flow. Press the ‘Ctrl’ key and select the required fields, to select only the required fields. Press the
‘Shift’ key and click the last/first field, to select a continuous list of fields.
Click on 'Remove', to remove any added field.
Click 'Move Up' and 'Move Down', to modify the order of the added fields.

The option “Event Priority” is introduced to set the priority for event delivery of the event type that is under design when using integration
service. The default priority is 0 and can be edited to a positive integer. This value gets stored in the EVENT.PRIORITY FIELD OF
IF.INTEGRATION.FLOW.CATALOG
The “Include before image” option adds the existing transaction data to the generated event.
The "Process updates only" option includes only the changed field value for the current transaction to the event and ignores all other fields while
generating the event

file:///D:/Temenos/R19 AMR Documentation/R19ID.htm#../Subsystems/R19TechUG/Content/Integration Framework/User Guides/Event Designer/… 2/5

07/10/2024 18:30 Defining the flow
The "Include Digital Signature” option publishes the flow with a new attribute “Include Digital Signature” to the flow. This enables the event
messages to be digitally signed. The implementation for digitally signing the message need to be implemented by the user and the details are
available in the Inbound Security Service User Guide
The Display Name column in the Flow Enrichments is an editable column. Once a T24 field is added to the schema, this column allows to specify
a different name to the field only in the flow to make the names more meaningful. This does not change the field name in the underlying
application.
The option streaming event allows the IF events to be streamed to streaming systems and not be store in IF.EVENTS.INTERFACE.TABLE. Refer
streaming events user guide to know more about streaming events.
The option RAX_XML stores the IF Event as an internal XML representation of IF event XML. This option provides faster event delivery. The below
options cannot be used when using RAW_XML type of event:
1. Defining filters when using IIB Adapter
2. Adding IF Event Field Values in JMS Message header when running integration service
3. Modifying or filtering data when running integration service.

Note: The option “Include Before Image” and “Process Updates Only” is applicable only for Application, Version and TSA.SERVICE exit points. The option
STREAMING_EVENT and RAW_XML are mutually exclusive.

Join Field:

It is possible to add join field in the flow. A join field is a field that is used to retrieve the related information. To define a join field:

Select the field through which the join has to be defined. (Here CREDIT.ACCT.NO)
Select Join.
A popup window as shown below appears.
Select the application from 'Application' drop down box from which the join retrieves the data (Here ACCOUNT)
Select the field from the 'Field Name' drop down box. This is the field from where the join field gets the value. (Here SECTOR)
Click 'Add' to add to the join definition
Repeat step 4-6 till the join field is completed in the 'Join Definition' field.
Click 'Finish' to complete the join definition.

Join definition dialog has an option “Modify Key”. This option allows the user to define complex joins, to fetch data from two indirectly related or
un-related tables:

file:///D:/Temenos/R19 AMR Documentation/R19ID.htm#../Subsystems/R19TechUG/Content/Integration Framework/User Guides/Event Designer/… 3/5

07/10/2024 18:30 Defining the flow

To use this option, the user needs to select the “Modify Key” check box, before adding the field to the join. The application for which the key
need to be modified will be prefixed with # and an API implementation need to be written to resolve the key. This is described in the "How to
define Complex Joins" user guide.
The Source tab provides the XML based representation of the Flow as shown below.

This is the XML source of the event. This could be viewed from the Source Tab under the event

file:///D:/Temenos/R19 AMR Documentation/R19ID.htm#../Subsystems/R19TechUG/Content/Integration Framework/User Guides/Event Designer/… 4/5

07/10/2024 18:30 Defining the flow

Overrides can be specified using the Overrides tab. This helps in implementing DISPO.PROCESSING, such that a particular user can authorise the
record. Only Overrides with DISPO.PROCESSING set to FORCE are available. Overrides tab is enabled only for INPUT.ROUTINE exit point, as
override is inappropriate during Authorized stage.

Note: Override option is supported only for INPUT.ROUTINE type of exit point for Version and Application.

Published on: 25/04/2019

file:///D:/Temenos/R19 AMR Documentation/R19ID.htm#../Subsystems/R19TechUG/Content/Integration Framework/User Guides/Event Designer/… 5/5