Event Framework
R24 AMR | Min(s) read

Inflow Signal Event

If an Inflow request is failed, then the client has to view the IF_INFLOW_MESSAGE_FAILED table to understand the details of the failure, which is a tedious process.

In addition to the IF_INFLOW_MESSAGE_FAILED table failure details, It provides the failure details available in IF.EVENTS.INTERFACE.TABLE to provide a better understanding of the failure, that is, if a failure occurred in Transact and all the retries for the corresponding failure are exhausted then a signal event is triggered and sent to IF.EVENTS.INTERFACE.TABLE stating the request has failed in Transact.

The below scenarios describe the different types of failure requests:

Scenario 1

This section explains a failure scenario for an application based request. The below request does not have a sector named 1001435.

As a result of executing the above request, it fails due to an invalid sector and moves to IF_INFLOW_MESSAGE_FAILED. When all the retries are exhausted, then a signal event triggers and displays it in IF.EVENTS.INTERFACE.TABLE.

Inflow without PW

Updated to False

One event is generated after updated as False (False indicates all retries are exhausted)

Scenario 2

This section explains a failure scenario for process based request. The below request does not have any valid sector.

As a result of executing the above request, it fails due to an invalid sector and moves to IF_INFLOW_MESSAGE_FAILED. When all the retries are exhausted, then a signal event triggers and displays in IF.EVENTS.INTERFACE.TABLE.

Scenario 3

This section explains a failure scenario for GENERIC-OFS request. The below request does not have any valid sector.

As a result of executing the above request, the request fails due to an invalid sector and moves to IF_INFLOW_MESSAGE_FAILED. When all the retries are exhausted, then a signal event triggers and displays in IF.EVENTS.INTERFACE.TABLE.

Scenario 4

Similarly, a signal event triggers if any issue occurs with bulk requests too. For all the application based bulk request failures, a signal event triggers for each failed request and displays the details in IF.EVENTS.INTERFACE.TABLE.

Before Event Generation

After Event Generation

For all the process based bulk request failures, a signal event triggers for each failed request and displays the details in IF.EVENTS.INTERFACE.TABLE.

Similarly, for all the failures in Bulk OFS requests, a signal event triggers for each failed request and displays the details in IF.EVENTS.INTERFACE.TABLE.

Before Event Generation

After Event Generation

Copyright © 2020- Temenos Headquarters SA

Published on :
Monday, May 27, 2024 4:29:32 PM IST