Disclaimer

Your use of this download is governed by Stonebranch’s Terms of Use.

Version Information

Template Name	Extension Name	Version	Status
Informatica Cloud	ue-informatica-cloud	1 (1.0.0)	Fixes and new Features are introduced

‎ ‎ ‎

Overview

Informatica Cloud is a cloud‑native data management platform that enables organizations to integrate, transform, and orchestrate data across on‑premises and multi‑cloud environments.

This integration enables users to trigger and control Informatica Cloud Taskflows, Processes and Jobs from the Controller.

Key Features

Feature	Description
Trigger and Monitor Taskflows	Trigger and Monitor an Informatica Cloud Taskflow, with the option to provide required input and fault action strategy.
Trigger Processes	Trigger Processes in a synchronous way, with the option to provide input for the executed process.
Trigger and Monitor Jobs	Trigger and Monitor Linear Taskflow Job, Synchronization Task, PowerCenter Task, Replication Task, and Mapping Task.
Input Options	Flexibility to provide input as JSON Text or JSON Script
Output Options	Flexibility to provide Activity Log and Session Log on STDOUT and Activity Log on EXTENSION Output. It is also possible for Users to retrieve Activity Logs on demand when required.

‎ ‎

Requirements

This integration requires a Universal Agent and a Python runtime to execute the Universal Task.

Area

Details

Python Version

Requires Python 3.11. Tested with Agent bundled python distribution.

Universal Agent Compatibility

Compatible with Universal Agent for Windows x64 and version >= 7.6.0.0.

Compatible with Universal Agent for Linux and version >= 7.6.0.0.

Universal Controller Compatibility

Universal Controller Version >= 7.6.0.0.

‎ ‎

Supported Actions

Action: Run Taskflow

The "Run Taskflow" action enables a Taskflow to be executed on Informatica Cloud. The necessary credentials, the Point of Deployment (POD) region associated with the Informatica Cloud login URL, the path of the desired Taskflow, and additional execution parameters must be provided by the task author. It can be specified whether the task should merely initiate the Taskflow, or also wait until a final success or failure state is reached. The latest activity of the Taskflow can be included in the Extension Output, while the Run ID, Status, and Last Update On are displayed as output fields during task instance execution.

Configuration examples

Simple Taskflow triggering

The Taskflow is triggered with the "API Name" set as the Path, and the task instance does not wait for its completion.

Taskflow Is Triggered With Custom Name and Login URL

The Taskflow is executed using a custom name that is applied to the task instance and a login URL. Additional parameters, such as fault action and output options, are not applied because completion is not awaited.

Taskflow Is Executed with Custom Name and Additional Configuration

The Taskflow is executed with a custom name applied to the task instance, and the task instance waits for its completion. Additional parameters, such as fault action and output options, are applied. We also include additional input as JSON text provided directly in the field.

Taskflow Is Executed with Custom Name and Awaited Completion

The Taskflow is executed with a custom name applied to the task instance, and the task instance waits for its completion. Additional parameters, such as fault action and output options, are applied. We also include additional input as a script.

Action: Run Process

The "Run Process" action enables a Process to be executed on Informatica Cloud. The necessary credentials, the Point of Deployment (POD) region associated with the Informatica Cloud login URL, the path of the desired Process, and optional execution configuration can be provided by the task author. This task operates synchronously, requiring either an indefinite wait until the Process completes, or the setting of a timeout which, if reached, will result in task failure.

Configuration examples

Process Is Executed Without Timeout

The Process is executed with the "API Name" set as the Path, and the task instance does not wait for its completion.
Note: In the Informatica Cloud Application Integration, the default timeout for synchronous operations is 600 seconds (10 minutes).

Process Is Executed with Timeout and Script Configuration

The Process is executed using the provided path as a UAC Variable, with a specified timeout, and we also include the additional input, as a script.

Action: Run Job

The "Run Job" action enables a Job to be executed on Informatica Cloud. The necessary credentials, the Point of Deployment (POD) region associated with the Informatica Cloud login URL, the path and the type of the desired Job, and additional execution parameters can be provided by the task author. It can be specified whether the task should merely initiate the Job, or also wait until a final success or failure state is reached. The latest activity of the Job can be included in the Extension Output, while the Run ID, Task ID, Status, and Last Update On are displayed as output fields during task instance execution.

Configuration examples

Linear Taskflow Job Is Executed with Specified Path

The Job of type Linear Taskflow is executed using the provided path.

Job Is Executed with Specified Name and Completion Wait

The Job is executed using the provided path as a UAC Variable, and the task instance waits for its completion. Upon completion, the selected output options are displayed.

Action Output

Output Type

Description

Examples

EXTENSION

The extension output provides the following information:

exit_code, status_description: General info regarding the task execution. For more information, see the exit code table.
invocation.fields: The task configuration used for this task execution.
result.activity_log: Type: JSON Object. Shows the latest activity and status of the Job or Taskflow. Applicable for actions: Run Taskflow, Run Job. The contents of this JSON Object may vary depending on the target Informatica Cloud Version.
result.errors: List of errors that might have occurred during execution.

Successful Job Execution

{
    "exit_code": 0,
    "status_description": "Task executed successfully",
    "invocation": {
        "extension": "ue-informatica-cloud",
        "version": "1.0.0",
        "fields": {
            "action": "Run Job",
            "job_type": "Synchronization Task",
            "credentials": {
                "user": "username",
                "password": "****",
                "token": "****",
                "key_location": null,
                "passphrase": "****"
            },
            "pod_region": "US - United States",
            "login_url": null,
            "use_login_url": false,
            "path": "qa_synchronization_task",
            "timeout": 0,
            "custom_name": null,
            "fault_action": null,
            "provide_input": null,
            "input_json": null,
            "input_script": null,
            "wait_for_success_or_failure": true,
            "polling_interval": 5,
            "max_number_of_polls": 0,
            "output_options": [
                "Activity Log on STDOUT",
                "Session Log on STDOUT",
                "Activity Log on Extension Output"
            ],
            "run_id": null,
            "task_id": null,
            "status": null,
            "last_update_on": null
        }
    },
    "result": {
        "activity_log": [
            {
                "@type": "activityLogEntry",
                "id": "0135GFC1000000001F8W",
                "type": "DSS",
                "objectId": "0135GF0I00000000000B",
                "objectName": "qa_synchronization_task",
                "runId": 224,
                "startTime": "2025-02-19T07:18:46.000Z",
                "endTime": "2025-02-19T07:18:51.000Z",
                "startTimeUtc": "2025-02-19T12:18:46.000Z",
                "endTimeUtc": "2025-02-19T12:18:51.000Z",
                "state": 1,
                "UIState": 1,
                "failedSourceRows": 0,
                "successSourceRows": 4,
                "failedTargetRows": 0,
                "successTargetRows": 4,
                "startedBy": "username",
                "runContextType": "REST_API_V2",
                "entries": [
                    {
                        "@type": "activityLogEntry",
                        "id": "2943558702",
                        "type": "DSS",
                        "objectName": "My_Customer_target",
                        "runId": 224,
                        "agentId": "00800000000003X",
                        "runtimeEnvironmentId": "025000000000002",
                        "startTime": "2025-02-19T07:18:46.000Z",
                        "endTime": "2025-02-19T07:18:51.000Z",
                        "startTimeUtc": "2025-02-19T12:18:46.000Z",
                        "endTimeUtc": "2025-02-19T12:18:51.000Z",
                        "state": 1,
                        "UIState": 1,
                        "failedSourceRows": 0,
                        "successSourceRows": 4,
                        "failedTargetRows": 0,
                        "successTargetRows": 4,
                        "errorMsg": "No errors encountered.",
                        "startedBy": "username",
                        "runContextType": "REST_API_V2",
                        "entries": [],
                        "subTaskEntries": [],
                        "logEntryItemAttrs": {
                            "CONSUMED_COMPUTE_UNITS": "0.0",
                            "DTM_PDO_TYPE": "NONE",
                            "ERROR_CODE": "0",
                            "IS_SERVER_LESS": "false",
                            "OBJ_LOCATION": "Stonebranch QA\\Job",
                            "REQUESTED_COMPUTE_UNITS": "0.0",
                            "SERVICE_TYPE": "CDI",
                            "Session Log File Name": "s_dss_32R3zxpqNVSdtt5Zsa476o_4.log",
                            "TASK_UUID": "32R3zxpqNVSdtt5Zsa476o",
                            "releaseVersion": "4800"
                        },
                        "sessionVariables": {},
                        "totalSuccessRows": 0,
                        "totalFailedRows": 0,
                        "stopOnError": false,
                        "hasStopOnErrorRecord": false,
                        "isStopped": false,
                        "transformationEntries": [
                            {
                                "@type": "transformationLogEntry",
                                "id": "5419628509",
                                "txName": "SQ_My_Customer_source",
                                "txType": "SOURCE",
                                "successRows": 4,
                                "failedRows": 0
                            },
                            {
                                "@type": "transformationLogEntry",
                                "id": "5419628510",
                                "txName": "My_Customer_target",
                                "txType": "TARGET",
                                "successRows": 4,
                                "failedRows": 0
                            }
                        ]
                    }
                ],
                "totalSuccessRows": 0,
                "totalFailedRows": 0,
                "stopOnError": false,
                "hasStopOnErrorRecord": false,
                "isStopped": false
            }
        ]
    }
}

Successful Taskflow Execution

{
    "exit_code": 0,
    "status_description": "Task executed successfully",
    "invocation": {
        "extension": "ue-informatica-cloud",
        "version": "1.0.0",
        "fields": {
            "action": "Run Taskflow",
            "job_type": null,
            "credentials": {
                "user": "username",
                "password": "****",
                "token": "****",
                "key_location": null,
                "passphrase": "****"
            },
            "pod_region": "US - United States",
            "login_url": null,
            "use_login_url": false,
            "path": "qa_taskflow_basic",
            "timeout": 0,
            "custom_name": null,
            "fault_action": "-- None --",
            "provide_input": "-- None --",
            "input_json": null,
            "input_script": null,
            "wait_for_success_or_failure": true,
            "polling_interval": 5,
            "max_number_of_polls": 0,
            "output_options": [
                "Activity Log on STDOUT",
                "Activity Log on Extension Output"
            ],
            "run_id": null,
            "task_id": null,
            "status": null,
            "last_update_on": null
        }
    },
    "result": {
        "activity_log": {
            "assetName": "qa_taskflow_basic",
            "assetType": "TASKFLOW",
            "duration": 11,
            "endTime": "2025-02-19T12:16:45Z",
            "errorMessage": null,
            "location": "Stonebranch QA\\Taskflow",
            "runId": 1076839709661396992,
            "runtimeEnv": "application-integration-0.application-integration.taskflow-prod-usw3.svc.cluster.local:8443",
            "runtimeEnvName": null,
            "startedBy": "username",
            "startTime": "2025-02-19T12:16:34Z",
            "status": "SUCCESS",
            "subtasks": 0,
            "updateTime": "2025-02-19T12:16:45Z",
            "subtaskDetails": null
        }
    }
}

Successful Process Execution

{
    "exit_code": 0,
    "status_description": "Task executed successfully",
    "invocation": {
        "extension": "ue-informatica-cloud",
        "version": "1.0.0",
        "fields": {
            "action": "Run Process",
            "job_type": null,
            "credentials": {
                "user": "username",
                "password": "****",
                "token": "****",
                "key_location": null,
                "passphrase": "****"
            },
            "pod_region": "US - United States",
            "login_url": null,
            "use_login_url": false,
            "path": "qa_process_basic",
            "timeout": 60,
            "custom_name": null,
            "fault_action": null,
            "provide_input": "-- None --",
            "input_json": null,
            "input_script": null,
            "wait_for_success_or_failure": false,
            "polling_interval": 0,
            "max_number_of_polls": 0,
            "output_options": null,
            "run_id": null,
            "task_id": null,
            "status": null,
            "last_update_on": null
        }
    },
    "result": null
}

Failed Execution

{
    "exit_code": 40,
    "status_description": "Polling Timeout",
    "invocation": {
        "extension": "ue-informatica-cloud",
        "version": "1.0.0",
        "fields": {
            "action": "Run Job",
            "job_type": "Synchronization Task",
            "credentials": {
                "user": "username",
                "password": "****",
                "token": "****",
                "key_location": null,
                "passphrase": "****"
            },
            "pod_region": "US - United States",
            "login_url": null,
            "use_login_url": false,
            "path": "qa_synchronization_task",
            "timeout": 0,
            "custom_name": null,
            "fault_action": null,
            "provide_input": null,
            "input_json": null,
            "input_script": null,
            "wait_for_success_or_failure": true,
            "polling_interval": 1,
            "max_number_of_polls": 1,
            "output_options": [
                "Activity Log on STDOUT",
                "Session Log on STDOUT",
                "Activity Log on Extension Output"
            ],
            "run_id": null,
            "task_id": null,
            "status": null,
            "last_update_on": null
        }
    },
    "result": {
        "errors": [
            "Polling Timeout"
        ]
    }
}

STDOUT

Depending on the configuration of the Output Options field and type of workload running, STDOUT can provide the Session Log and/or Activity Log.

STDERR

Shows the logs from the execution of the task instance based. The verbosity is controlled by the Task configuration Log Level.

‎ ‎

Input Fields

Name	Type	Description	Version Information
Action	Choice	The action performed upon the task execution. Run Taskflow Run Process Run Job	Introduced in 1.0.0
Type	Choice	Defines the type of job that will run. Available types: Linear Taskflow Synchronization Task PowerCenter Task Replication Task Mapping Task Available if the selected Action is "Run Job".	Introduced in 1.0.0
Credentials	Credential	Credentials for Informatica Cloud. The Credentials definition should be as follows: Username as "Runtime User". Password as "Runtime Password".	Introduced in 1.0.0
Point Of Deployment (POD) Region	Choice	When this field is visible, the region is required as an input, and the Login URL is inferred based on the region. Otherwise, the Login URL needs to be provided. The available regions are: US: Refers to the United States region. AP: Refers to the Asia-Pacific region. EM: Refers to the Europe, Middle East, and Africa region	Introduced in 1.0.0
Login URL	Text	When this field is visible, the full login URL needs to be provided. The Login URL follows the format: `https://dm-[POD REGION].informaticacloud.com` For example, for the US region, the URL is `https://dm-us.informaticacloud.com` Required when Use Login URL is checked.	Introduced in 1.0.0
Use Login URL	Boolean	When checked, Login URL field should be populated. Otherwise, Point Of Deployment (POD) Region needs to be selected.	Introduced in 1.0.0
Path	Text	The path to the Taskflow, Process, or Job. If no duplicate names exist across folders, providing just the object name should suffice.	Introduced in 1.0.0
Timeout (sec)	Integer	When a timeout value is specified, the task instance will stop waiting for a response after the designated duration and the task instance will fail. If no timeout value is set, the request will wait indefinitely until the process completes. Available if the selected Action is “Run Process“.	Introduced in 1.0.0
Custom Name	Text	Custom names can be assigned to Taskflow instances. Available when selected Action is “Run Taskflow“.	Introduced in 1.0.0
Fault Action	Choice	Defines the way executed Taskflow should respond if a fault is encountered in one of its tasks. Possible options: -- None -- Retry Fault Skip Fault During the initial run, the specified fault action is executed once on the first task within the Taskflow that fails. It is also possible to be modified on task instance level prior to a task instance re-run. Available when the selected Action is “Run Taskflow“. Note: This setting is applicable only if Wait For Success Or Failure is checked. It has no impact when the task’s purpose is solely to trigger the Taskflow.	Introduced in 1.0.0
Provide Input	Choice	Presents the user with an option to select the input type. Available options are: As JSON Text As JSON Script Available when the selected Action is not “Run Job“.	Introduced in 1.0.0
Input (JSON)	Text	Provides a text field within the application where the user can directly input JSON data. Available when field Provide Input is set to “As JSON Text”.	Introduced in 1.0.0
Input (Script)	Script	Allows the user to include a predefined script, which can be added to the extension to define specific behaviors or configurations. Available when field Provide Input is set to “As JSON Script”.	Introduced in 1.0.0
Wait For Success Or Failure	Boolean	If selected, the task will continue running until the Job reaches the "SUCCESS" or "FAILED" state. "SUSPENDED" and "CANCELLED" are also considered "FAILED" states. Available if the selected Action is not “Run Process“.	Introduced in 1.0.0
Polling Interval (sec)	Integer	The polling interval in seconds for the activity check. Defaults to 60 seconds. Required when Wait for Success or Failure is checked.	Introduced in 1.0.0
Max Number Of Polls	Integer	Maximum number of polls. Can be used to control the approximate expected duration of the action (in relation also to Polling Interval (sec)). If left empty, the UAC Task will poll indefinitely, checking whether the Flow Run completed or resulted in failure. If the Maximum Number of Polls is reached, the exit code of the task will be 40, and the task instance will result in a failed state. Available if Wait for Completion is checked.	Introduced in 1.0.0
Output Options	Choice	The content of the Extension Output and STDOUT can be controlled with the following options: “Activity Log on STDOUT”: The latest Activity Log retrieved from Informatica Cloud is displayed on STDOUT. “Session Log on STDOUT”: The latest Session Log retrieved from Informatica Cloud is displayed on STDOUT. “Activity Log on Extension Output”: The latest Activity Log retrieved from Informatica Cloud is displayed on the Extension Output. Multiple options can be selected. Available if the selected Action is not “Run Process“.	Introduced in 1.0.0

‎ ‎

Dynamic Commands

Dynamic Command “Retrieve activity log” is available in various task instance statuses. While its primary purpose is to retrieve the Activity Log from the Taskflow or Job, it can also help in the following scenarios:

While a Task Instance is in “Running” state: The dynamic command can be executed during Taskflow or Job execution to retrieve activity logs in real-time, which is especially useful for monitoring the status of longer-running tasks.
When a Task Instance reaches “Success” or “Failed” state: Once the Task Instance has completed with success or failure, the dynamic command can also be applied to retrieve activity logs. This could be useful if the task is not configured with the required Output Options. It is a prerequisite for the retrieval that the Taskflow or Job has been successfully initiated.

Output Fields

The following output-only fields provide better visibility during the execution of Universal Task Instances.

Field	Type	Description	Introduced in Version
Status	Text	The status of the Taskflow / Job	1.0.0
Run ID	Text	The Run ID of the Taskflow / Job	1.0.0
Task ID	Text	The Task ID of the Job	1.0.0
Last Update On	Text	Date and time when the last update occurred	1.0.0

‎ ‎

Cancelation and Rerun

In case of cancellation, the Job, Taskflow or Process is not canceled on Informatica Cloud.

During a re-run of a Taskflow Action, the Run Id and Status output fields are preserved. Depending on the Fault Action (which can be modified between re-runs on Task Instance Level), the Taskflow can be resumed accordingly.

Exit Codes

Exit Code	Status	Status Description	Meaning
0	Success	“SUCCESS: Task executed successfully.“	Successful Execution
1	Failure	“Execution Failed: <<Error Description>>”	Generic Error. Raised when not falling into the other Error Codes.
20	Failure	“Data Validation Error: <<Error Description>> “	Input fields validation error.
40	Failure	“Polling Timeout“	The Flow Run is executed out of the normal duration boundaries.

‎ ‎

Environment Variables

Environment Variables can be set from Environment Variables task definition table. The following environment variables can affect the behavior of the extension.

Environment Variable Name

Description

Introduced in Version

UE_HTTP_TIMEOUT

Specifies the timeout (in seconds) for HTTP requests made by the Task Instance. A higher value allows for slower responses, while a lower value enforces stricter time constraints. If not set, a default of 60 seconds is used. When a timeout happens the Task Instance ends up with failure.

UE_HTTP_TIMEOUT is not affecting the synchronous execution of a Process where the timeout is controlled by Timeout (sec) field

1.0.0

‎ ‎

STDOUT and STDERR

STDOUT is used for displaying log information, like the session logs and the activity logs, and its controlled with the Output Option field.

STDERR provides additional information to the user, the detail of it is tuned by Log Level Task Definition field.

Backward compatibility is not guaranteed for the content of STDOUT/STDERR and can be changed in future versions without notice

How To

Import Universal Template

To use the Universal Template, you first must perform the following steps.

This Universal Task requires the Resolvable Credentials feature. Check that the Resolvable Credentials Permitted system property has been set to true.
To import the Universal Template into your Controller, follow these instructions.
When the files have been imported successfully, refresh the Universal Templates list; the Universal Template will appear on the list.

Modifications of this integration, applied by users or customers, before or after import, might affect the supportability of this integration. For more information refer to Integration Modifications.

Configure Universal Task

For a new Universal Task, create a new task, and enter the required input fields.

Integration Modifications

Modifications applied by users or customers, before or after import, might affect the supportability of this integration. The following modifications are discouraged to retain the support level as applied for this integration.

Python code modifications should not be done.
Template Modifications
- General Section
  - "Name", "Extension", "Variable Prefix", and "Icon" should not be changed.
- Universal Template Details Section
  - "Template Type", "Agent Type", "Send Extension Variables", and "Always Cancel on Force Finish" should not be changed.
- Result Processing Defaults Section
  - Success and Failure Exit codes should not be changed.
  - Success and Failure Output processing should not be changed.
- Fields Restriction Section
  The setup of the template does not impose any restrictions. However, concerning the "Exit Code Processing Fields" section.
  1. Success/Failure exit codes need to be respected.
  2. In principle, as STDERR and STDOUT outputs can change in follow-up releases of this integration, they should not be considered as a reliable source for determining the success or failure of a task.

Users and customers are encouraged to report defects, or feature requests at Stonebranch Support Desk.

Document References

This document references the following documents:

Document Link	Description
Universal Templates	User documentation for creating, working with and understanding Universal Templates and Integrations.
Universal Tasks	User documentation for creating Universal Tasks in the Universal Controller user interface.

‎ ‎

Changelog

ue-informatica-cloud-1.0.0 (2025-02-27)

Initial Version

Integrations

Informatica Cloud

Analytics

Disclaimer

Version Information

Overview

Key Features

Requirements

Supported Actions

Action: Run Taskflow

Configuration examples

Simple Taskflow triggering

Taskflow Is Triggered With Custom Name and Login URL

Taskflow Is Executed with Custom Name and Additional Configuration

Taskflow Is Executed with Custom Name and Awaited Completion

Action: Run Process

Configuration examples

Process Is Executed Without Timeout

Process Is Executed with Timeout and Script Configuration

Action: Run Job

Configuration examples

Linear Taskflow Job Is Executed with Specified Path

Job Is Executed with Specified Name and Completion Wait

Action Output

Input Fields

Dynamic Commands

Output Fields

Cancelation and Rerun

Exit Codes

Environment Variables

STDOUT and STDERR

How To

Import Universal Template

Configure Universal Task

Integration Modifications

Document References

Changelog

ue-informatica-cloud-1.0.0 (2025-02-27)

Related content