ETL Post Processing

Overview

We are introducing the ability to perform actions after entities are loaded through ETL. After the load phase completes, a number of post-processing actions are available, including the recalculation of Dynamic Access Layers and Jurisdiction assignments for entities that were created or updated during the migration. This ensures that migrated data aligns with standard Fenergo platform rules for access control, policy scoping, and jurisdiction configuration. These actions run after the ETL load phase and can be enabled per migration project.

ETL Post Processing Capabilities

When using ETL Post Processing, users can apply automated recalculation logic to entities migrated via ETL to ensure consistency with entities processed through standard platform journeys.

Supported capabilities include:

• Recalculation of Dynamic Access Layers
• Recalculation of Jurisdiction assignments

Prerequisites to Using ETL Post Processing

Before using Dynamic Access Layer recalculation, the following tenant-level setting must be enabled:

• Enable Entity/Journey Dynamic Access Layers Assignment

important

If this setting is not enabled, the Calculate Dynamic Access Layers toggle will not display within the ETL project.

Configuring Post Load Actions

Post Processing actions are configured during ETL project creation or edit using Post Load Actions.

To configure Post Load Actions:

1. Create or open an ETL project.
2. Navigate to Project Details.
3. Enable one or more of the following options:
   • Calculate Dynamic Access Layers
   • Calculate Jurisdictions
4. Save the project configuration.
5. Run the ETL migration.

tip

Post Load Actions apply only to entities created or updated within the ETL project.

Post Load Actions Execution

Post Load Actions execute automatically after the ETL Load phase completes.

Execution flow:

1. ETL Load completes successfully.
2. Enabled Post Load Actions are triggered.
3. All eligible entities created or updated by the project are collected.
4. Recalculation logic is applied.
5. Results are persisted on the entity record.

Post Load Actions run asynchronously and do not block ETL project completion.

Monitoring Post Load Actions

Users can monitor Post Processing progress from the Post Load Actions tab within the ETL project.

The Post Load Actions tab displays:

• Post Processing Action name
• Execution status (Calculated, Failed and Unprocessed)
• Start and completion timestamps

If an action fails, the ETL load is not rolled back. Failed entities can be reviewed and addressed separately.

info

Entities with an In-Progress journey will fail Dynamic Access Layer recalculation.

Calculate Dynamic Access Layers

Dynamic Access Layers (DAL) provide rule-based access control driven by entity attributes, metadata, and related product information. When enabled, this Post Processing action recalculates DAL assignments for supported entities migrated via ETL.

This ensures migrated entities follow the same access governance rules as entities processed through standard platform workflows.

Capabilities (DAL)

• Evaluates and applies Dynamic Access Layer rules
• Ensures consistent access control for migrated entities
• Supports recalculation at entity level only
• Applies only when Dynamic Access Layers are enabled for the tenant

Supported Entity Types (DAL)

Entity Type	Supported	Notes
Individual	Yes	Included for Create and Update operations
Company	Yes	Included for Create and Update operations
Other	Yes	Included for Create and Update operations
Products	No	The Product team is currently working on this feature
Investment Account	No	Not currently supported
Bank Account	No	Not currently supported

Evaluation

Please refer to the Dynamic Access Layer User Guide: Access Management User Guide

Processing Behaviour (DAL)

• All supported entities in the ETL project are included automatically.
• Recalculation fails for entities with an In-Progress journey.

Calculate Jurisdictions

Jurisdiction assignment determines which jurisdiction-specific policies apply to an entity. This Post Processing action recalculates jurisdiction applicability for entities created or updated during ETL.

This ensures downstream journeys apply the correct jurisdiction configuration and policy version.

Capabilities (Jurisdictions)

• Re-evaluates jurisdiction applicability post migration
• Adds newly applicable jurisdictions
• Preserves existing jurisdictions
• Updates the policy version for the entity

Supported Entity Types (Jurisdictions)

All entity types created or updated during ETL are included in jurisdiction evaluation.

note

Entity-to-entity associations do not currently affect jurisdiction outcomes.

Inputs to Jurisdiction Determination

Please refer to the Policy and Jurisdiction User Guide: Policy and Jurisdiction User Guide

Processing Behaviour (Jurisdictions)

• All migrated entity IDs of type Individual, Company and Other are included in recalculation.
• Jurisdictions are added but not removed.
• Jurisdiction values shown on the entity profile reflect the most recent verification snapshot.