Architecture of Business Events

EB.EVENT.TYPE is the touchpoint between the actual event happening in Temenos Transact and the TEC.ITEMS configuration. Temenos Transact Model Bank supplies several touchpoints which indicates the occurrence of an event.

Most of the touchpoints are instances where a table gets updated. But there are some touchpoints, which are not triggered from the table update.

When an EB.EVENT.TYPE is called, the instruction is delivered from this event type with an EB.ACTIVITY value. This is linked to an EB.ADVICES record, which is linked to the DE.MESSAGE functionality.

This table handles both technical alerts, which are the errors in processing and business alerts, which is the information for customers and account officers about business events.

It is likely that the overall touchpoint is too high-level to be of use for determining an event.

Using TEC.ITEMS, banks can fine-tune the nature of the event based on the requirement. An event can be generated every time a touchpoint, EB.EVENT.TYPE is triggered but possibly under specific circumstances. Users can subscribe to these fine-tuned circumstances. TEC.ITEMS clarifies the nature of the Event through the following settings:

• Subscriber

  This setting indicates that the medium the alert is sent when an event occurs. Model Bank comes configured with the functionality to communicate this over the DELIVERY system. In future, other subscribers such as Process Workflow or a Business Activity Monitoring mechanism also be included.

• Event Type

  This setting describes the underlying touchpoint and it is set in the EVENT.TYPE field.

• Subscription Type

  This setting describes the type of subscription whether this is monitored by customer or accounts officer or both of them and is it a mandatory field for everyone. This is set in the SUBSCRIPTION.LEVEL field. There are queries in Model Bank and validation to ensure that the internal subscribers such as account officers cannot subscribe to external events and vice-versa.

• Field Level Specification

  This setting is the main source of events such as where an event relates to entry into a Temenos Transact table and what sort of checking the system should perform to ascertain whether an event has taken place.

  Events are related to an update to the ACCOUNT table, so update to ACCOUNT is a touchpoint but different events are derived from this. It depends on whether it is WORKING.BALANCE or ACCOUNT.INACTIVE or even CURR.NO fields on account.

  Following are the additional considerations:

  • An event occurs depending on the updates to two or more fields.
    An event is triggered if the WORKING.BALANCE field changes and the CATEGORY.CODE is in 1000–1999 range.
  • Operands: Event functionality compares new values with old values to determine whether an event has occurred. Therefore, along with the usual operands such as greater than, less than, begins with, ends with, equals, does not equal, is/is not in the range of and so on, there are also comparative operands such as changed, changed from and changed to.
  • If the EVENT.TYPE is based on a table, the same table should be entered in the TABLE field.
  • An event is also defined by a KEYWORD.

    At times, it is impossible to determine whether an event has happened purely by looking at the fields and their values.

    An event being raised during the following scenarios:

    • A record is reversed so the event based on FUNCTION is used.
    • A particular VERSION is used.
    • After the FIRST authorizer (not necessarily the final authorizer).
    • A particular CHANNEL is used so an event occurs if channel A is used but not channel B.
    • A particular APPLICATION is used.

    For the above requirements, Keywords are used rather than a specific table. Following are the Keywords allowed:

    • - !APPLICATION (Application)
    • - !V$FUNCTION (Function)
    • - !PGM.VERSION (Version of the Application)
    • - !CHANNEL (Channel defined in ofs.source)
    • - !AUTH.NO (Number of Authorizers)

Following are the parameters in TEC.ITEMS: