## Tasks, transformations, and lineage

URL: https://docs.atlan.com/apps/connectors/etl-tools/informatica-cdi/faq/tasks-transformations-and-lineage

> Learn about supported tasks, transformations, and lineage generation in the Informatica CDI connector

Find answers to common questions about the Informatica Cloud Data Integration connector.

---

#### What types of tasks does this connector support?

The connector currently supports **Mapping Tasks**.

Variations of Mapping Task that don't alter the `export` API response structure are supported as well. For example:
- [Mapping Task (Advanced)](https://docs.informatica.com/integration-cloud/data-integration/current-version/mappings/mappings/mappings-in-advanced-mode.html)
- [Dynamic Mapping Tasks](https://docs.informatica.com/integration-cloud/cloud-data-integration/current-version/tasks/dynamic-mapping-tasks.html)

#### What supported features exist for dynamic mapping tasks?

A dynamic mapping task can contain multiple jobs, each with different source and target configurations. Atlan resolves lineage individually for every job—applying job-specific configurations and resolving parameter values independently. For a detailed breakdown of supported and unsupported scenarios, see [Dynamic mapping task lineage](https://docs.atlan.com/llms/connectors/informatica-cdi/dynamic-mapping-task-lineage/llms.txt).

#### What scenarios aren't supported for dynamic mapping task lineage?

The following scenarios aren't supported for lineage generation in dynamic mapping tasks:

- **Parameterized Single Object source:** Field details can't be derived from the Informatica API exports. Both field-level and object-level lineage are missing.
- **Parameterized Query with `SELECT *` source:** Atlan can't resolve individual fields from a wildcard query. Both field-level and object-level lineage are missing.
- **Partially Parameterized / Manual target field mapping:** These target field mapping types aren't processed for lineage.

---

#### What transformations are explicitly processed?

The following transformations receive special handling with detailed information extraction:

- Source 
- Target 
- Expression 
- Lookup 
- Joiner 
- Filter 
- Router 
- Aggregator 

#### What about transformations not in this list?

Transformations that aren't listed in the previous section are also processed and are taken into account for lineage calculations. 

#### How are Lookup transformations handled?

Lookup transformations work similarly to source transformations and generate lineage. 
For unconnected lookups, lineage is created based on the positioning of columns in the transformation.

---

#### Are parameter files processed for lineage?

Yes. When you upload parameter files to the Atlan Informatica workflow, the connector processes them to create accurate lineage connections.

#### Are taskflow-level parameters processed?

Yes. The connector processes parameters defined at the Taskflow level when you upload the corresponding parameter files to the workflow. 
See limitation around Taskflow parameter files below.

#### What content formats are supported for parameter files?

The connector supports parameter files that follow [IICS CDI guidelines](https://docs.informatica.com/integration-cloud/data-integration/current-version/mappings/parameters/parameter-files/rules-and-guidelines-for-parameter-files.html) for parameterization.

#### In what form must parameter files be uploaded?

Upload parameter files as a `.zip` archive with these supported MIME types:

- `application/zip` 
- `application/x-zip` 
- `application/x-zip-compressed` 

---

#### What source and target systems are supported for lineage?

Lineage is generated for sources and targets that are **relational** in nature, such as Snowflake and Oracle.

**Not supported:** Files, web services, and similar non-relational systems.

#### Is lineage generated at field level?

Yes. The connector creates lineage at the **field and column level** between sources and targets. 

To view field-level details, expand the source or target table in the lineage diagram.

#### If SQL override is used for source transformation, is lineage generated?

Yes. The connector parses SQL queries and generates lineage based on the parsing results.

---

#### What known limitations does this connector have?

**Parameter file handling limitations**

Parameter file names defined in Taskflows aren't always applied to Mapping Tasks correctly.

> *View supported and unsupported scenarios — see full content on the documentation site.*

**Other limitations**

- **Mapplets:** Treated as single transformations within mappings. Transformations within a mapplet aren't exposed as individual objects.
- **Incremental extraction:** Not supported. The connector scans all objects in each run based on the Project/Folder workflow configuration.
- **Self-Deployed Runtime:** The connector is currently not available to run on the Self-Deployed Runtime (SDR).
- **Authentication Types:** - The connector currently supports only basic authentication.

---