A Transformation-Phase is a set of transformation processes on segments of an Input-Event, that run independent to transformations defined in other Phases.


You can have two Phases:

  • Phase 1: Processing general accounts with checks linked to the bank, for example verify the existence of internal accounts
  • Phase 2: Processing client accounts

In this instance, you can still run the client account processing even if the checks on the general accounts are invalid.


If you apply several Rules to an Input- Event within the same Phase and the system detects an anomaly in one of the Rules, it places the Input-Event in anomaly and does not generate any Output-Events in this Phase.

Input-Event aggregation occurs outside the Phase

In mono-Phase processing, if the system detects an anomaly, it rejects the Input-Event.

In multi-Phase processing:

  • If the system detects an anomaly, it places the Input-Event and Phase in anomaly and then proceeds with processing in the next Phase.
  • If all Phases are in anomaly, the system rejects the Input-Event. You can recycle a specific Phase if required. You set the name of the Phase you want to recycle in a field and define it as the Phase anomaly code.

Related Links