Transformation-Domain: Transformation environments tab

About Transformation environments

What the Transformation environments tab shows

Using the Transformation environments tab

Creating and removing Transformation environments

Redirecting to Processing-Context-Outs

About Transformation environments

A Transformation environment activates one or more Transformation-Domains. Each activated Domain can then execute the Phases that it contains.

By default, AccountingIntegrator Enabler creates the BATCH Transformation environment to activate a Domain. You cannot delete this default environment, but you can use the Transformation environments tab to redirect it to a specific Processing-Context-Out.

What the Transformation environments tab shows

The Transformation environments tab is illustrated schematically below.

Transformation environments defined for the current Transformation-Domain

Drop-down list of Processing Context-Outs associated with a given Transformation environment

Icon bar to add or delete Transformation environments

Using the Transformation environments tab

Use the Transformation environments tab to:

The information you enter on this tab dynamically completes the >Environment_Transformation< section of the ctx.mvt configuration file. AccountingIntegrator Rule Engine uses this section to:

  • Retrieve the list of Transformation-Domains activated by each Transformation environment and consequently, which Transformation-Phases to apply.
  • Redirect the Input-Events to a given output file for each specified Processing-Context-Out.

For more information, refer to AccountingIntegrator EnablerReference Manual.

Creating Transformation environments

Each Transformation-Domain must have at least one Transformation environment. To add a Transformation environment to the current Transformation-Domain:

  1. Place the cursor in the Transformation environment column and click .
  2. Composer adds a new line to the Transformation environment table.
  3. Enter a name for the Transformation environment. You can use a maximum of 25 characters.
  4. Create a reference link between the Transformation environment and a specific Processing-Context-Out. Complete the Processing-Context-Out field with either of the following options:

Removing Transformation environments

To remove a Transformation environment from a Transformation-Domain, select the Transformation environment and click .

Redirecting to a Processing-Context-Out

You can link a Transformation environment to one or more Processing-Context-Outs. This action redirects the Input-Events contained in the Phases executed by the Domain that the environment activates, to the given Processing-Context-Outs.

Note: When you associate a Transformation-Environment to a Processing-Context-Out, you only create a reference link, not a physical one.

Redirection rules

AccountingIntegrator Enabler applies the following redirection rules:

  • Only redirects an Input-Event if all the Phases of the current processing are completed successfully.
  • If the Input-Event is placed in anomaly or rejected, AccountingIntegrator Enabler cancels redirection for the Input-Event concerned.
  • If you activated exits, AccountingIntegrator Enabler redirects the Input-Event as modified by the exits.

    The only exception to this principle is the exit applied to enrich the Event prior to Transformation-Rule.

Example

An Input-Event that is processed in real-time at the bank counter can only be processed for other applications during the overnight batch run. This scenario requires that you make a copy of the Input-Event after real-time processing.

Back to top

Related Links