Skip to main content

Tasks, transformations, and lineage

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

What types of tasks does the connector support?​

The connector currently supports Mapping Tasks.

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 the above list?​

Transformations that are not listed above 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.

What IICS CDI API calls are executed by the connector?​

The following API calls are executed:

APIPayload DetailsDescription
/user/login{"@type":"login","username":"***","password":"****"}Login to IICS Cloud
/public/core/v3/objectsq=type=='MTT'
q=type=='PROJECT'
q=type=='FOLDER'
{{mappingTaskId}}/references?refType=usedBy		Get listing for different objects
/public/core/v3/export{"name":"","objects":[{"id":"{{mappingTaskId}}","includeDependencies":true}]}
{"name":"","objects":[{"id":"{{taskfFlowId}}","includeDependencies":false}]}		Run export job
/public/core/v3/export/{{jobId}}—Monitor export job
/public/core/v3/export/{{jobId}}/package—Download export job results
/api/v2/connection/name/{{connectionName}}
/api/v2/connection/		—Get connection object details

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.

What content formats are supported for parameter files?​

The connector supports parameter files that follow IICS CDI guidelines 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 the 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 a custom query (SQL override) is used for a source transformation, is lineage generated?​

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

What are the limitations?​

Parameter file handling limitations

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

View supported and unsupported scenarios

Supported scenarios:

  • Parameter and directory mentioned in Assignment transformation level and type as content
  • Parameter and directory mentioned in Data task level and type as content

Unsupported scenarios:

  • Parameter and directory mentioned in Start as input field

Workaround: Create a param.meta file and upload it with your parameter files. Format the content as key-value pairs:

<MappingName>=<Uploaded_Param_filename>

Other limitations

  • Mapplets: Treated as single transformations within mappings. Inner transformations aren't exposed individually.
  • SQL parsing: Has known limitations.
  • Incremental extraction: Not supported. The connector scans all objects in each run based on your filter configuration.
  • Secure Agent: The connector is currently not available to run as a Secure Agent application
  • Authentication Types: - The connector currently supports only basic authentication. Support for SAML based authentication is planned to be added.