Event Framework
R24 AMR | Min(s) read

Fields in IF.EVENTS.INTERFACE.TABLE

Read this topic to familiarize yourself with the fields in IF.EVENTS.INTERFACE.TABLE.

All the fields in this application are No Input fields.
  • EVENT.DATA

    This field holds the current Integration Framework generated event data in XML format.

  • OLD.EVENT.XML

    This field holds the Integration Framework generated previous image event data in XML format. This XML will be generated only when the option “Include Previous Image” is selected during flow creation.

  • EVENT.XML.NAME

    This multi-value field holds the name of the data elements which make part of the event. The values for these element names are recorded in the associated field Field Value and in Old Field Val.

  • OLD.FIELD.VAL

    This multi-value field holds the previous image values of the data elements which make part of the event. The names for these elements are recorded in the associated field EVENT.XML.NAME.

  • FIELD.VALUE

    This multi-value field holds the values of the data elements which make part of the event. The names for these elements are recorded in the associated field EVENT.XML.NAME.

  • COMMON.XML.NAME

    This is a multi-value field that holds the data element names that are the part of the event common section.

  • COMMON.XML.VALUE This is a multi-value field that holds value of the data elements that are the part of the event common section.
  • EVENT.TYPE

    This field holds the type of the event represented by this record. It corresponds to the data flow name that was chosen for the events during the design stage.

  • EVENT.TIMESTAMP

    This field holds the time stamp at which the event was delivered through any of the available delivery mechanisms. An event record with this field having a non-empty value indicates that the event is already delivered and the record is ready for archival.

  • LOCAL.TRANSFORM

    This field stores data that indicates that the message has been transformed using a custom stylesheet and that the transformation has been successful. This field can hold the following values:

    • NO_XSLT_TRANSFORMATION – Indicates that no custom stylesheet has been applied and the IF generic transformation is used.
    • XSLT_TRANSFORMATION_SUCCESS – Indicates that a custom stylesheet has been applied and the transformation has been successful.
    • XSLT_TRANSFORMATION_FAILURE – Indicates that a custom stylesheet has been applied and the transformation has failed.
    This field is filled in only for delivery of integration events provided via the Delivery Exit point type.
  • DELIVERY.STATUS

    This field indicates the status of the event after the execution of Integration Service. This field can have the following values:

    • DELIVERY_SUCCESS – Event was delivered to queue successfully.
    • TRANSFORM_ERROR_CUSTOM – Custom style sheet was applied but the transformation failed
    • TRANSFORM_ERROR – Integration Framework default transformation failed.
    • EVENT_FILTERED – The Integration Framework event is filtered and will not be delivered to queue.
    • TRANSMIT_ERROR – There was an issue while delivering the event XML to the JMS queue.
    This field is filled in only for delivery of integration events provided via the Delivery Exit point type.
  • STATUS.REASON

    This field provides more information about the delivery status (DELIVERY.STATUS) of an event.

    This field is filled in only for delivery of integration events provided via the Delivery Exit point type.
  • CREATION.TIME

    This field holds the time stamp of the event created by Integration Framework.

  • CREATION.DATE

    This field hold the event creation date in T24 date format.

  • EVENT.PRIORITY

    The field holds the event priority of the event record. This value is taken from the EVENT.PRIORITY field of IF.INTEGRATION.FLOW.CATALOG.

Copyright © 2020- Temenos Headquarters SA

Published on :
Monday, May 27, 2024 4:37:59 PM IST