Table of Contents

Anchor
Disclaimer
Disclaimer
Disclaimer

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

Overview

Prefect is an open-source workflow management system designed to orchestrate data pipelines in Python. This integration provides the capability to trigger from UAC a Prefect Flow Run and monitor its execution providing useful metadata.

Key Features

...

Launch Flow Runs on Prefect Cloud and monitor until the flow gets completed with success or failure. Flow Run metadata can be provided as part of Extension Output.

Version Information

...

Anchor
Version Information
Version Information
Version Information

Template Name	Extension Name	Version	Status
Command Execution	ue-cmd	1 (Current 1.0.0)	Fixes and new Features are introduced.

Refer to Changelog for version history information.

...

Anchor
Overview
Overview
Overview

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

...

Python Version

...

It requires Python 3.11.

...

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.

...

Network and Connectivity

...

Network connectivity towards Prefect Cloud is required.

...

Prefect Cloud and Rest API versions

...

Compatible with Prefect Cloud version 2.18.1 with REST API version 0.8.4 . It should be compatible on later versions as long as backwards compatibility is guaranteed on the API level.

Supported Actions

Action: Prefect Cloud - Launch Flow Run

This action allows to launch a Flow Run on Prefect Cloud. The task author has to provide the required Credentials, the Workspace ID and the Deployment ID that relates to the Flow and some additional parameters related to the flow execution (more information can be found on the Fields Description section). Task author can decide whether the task will just launch the flow, or in addition wait until a final success or failure state is reached. The last execution Flow Run metadata can be published as part of the Extension Output, while the Flow Run ID, the Flow Run Name and the Flow Run State can be visible directly as output fields during task instance execution.

Configuration examples

...

Image Removed

...

Image Removed

...

Simple Launch Flow Execution using Workspace ID or Name and Deployment ID or Name as dynamic choice fields to retrieve the necessary names from the Prefect Cloud Platform.

...

Simple Launch Flow Execution using Workspace ID or Name and Deployment ID or Name as IDs that can be copy pasted from Prefect Console. For example purposes, dummy IDs are used.

...

Image Removed

...

Image Removed

...

Launch Flow and wait until the Flow ends in Success or in Failure. The latest Flow Run metadata is configured to be included as part of the Extension Output.

Action Output

...

EXTENSION

...

The extension output provides the following information:

exit_code, status_description: General info regarding the task execution. For more information users can refer to the exit code table.
invocation.fields: The task configuration used for this task execution.
result.flow_run_info: The latest Flow Run information provided by Prefect during the execution of the task. Populated in case task is configured to publish this information on Extension Output.
result.errors: List of errors that might have occurred during execution.

Code Block

title	Successful Scenario with latest Flow Run metadata as part of the Extension Output
collapse	true

{
    "exit_code": 0,
    "status_description": "Task executed successfully.",
    "invocation": {
        "fields": {...}
    },
    "result": {
        "flow_run_info": {
            "id": "c5feefe0-e932-4f1e-9055-03155561938d",
            "created": "2024-04-30T09:41:40.633550+00:00",
            "updated": "2024-04-30T09:41:40.628595+00:00",
            "name": "mydummyname",
            "flow_id": "6342cf22-2baa-4b4f-8c7f-85d731055af8",
            "state_id": "70736b0e-75e2-4156-8bca-8a21f4c538e4",
            "deployment_id": "ef8baf82-a14b-472f-9f8d-5424b66f232d",
            "work_queue_id": null,
            "work_queue_name": null,
            "flow_version": null,
            "deployment_version": "49e24154c00009d471e26e915271e743",
            "parameters": {
                "fail": false,
                "sleeptime": 5
            },
            "idempotency_key": null,
            "context": {
                "context1": "value1",
                "context2": "value2"
            },
            "empirical_policy": {
                "max_retries": 0,
                "retry_delay_seconds": 0,
                "retries": null,
                "retry_delay": null,
                "pause_keys": [],
                "resuming": false
            },
            "tags": [
                "telis 1",
                "telis 2",
                "testing"
            ],
            "parent_task_run_id": null,
            "state_type": "SCHEDULED",
            "state_name": "Scheduled",
            "run_count": 0,
            "expected_start_time": "2024-04-30T09:41:40.633473+00:00",
            "next_scheduled_start_time": "2024-04-30T09:41:40.633473+00:00",
            "start_time": null,
            "end_time": null,
            "total_run_time": 0,
            "estimated_run_time": 0,
            "estimated_start_time_delta": 0.049332,
            "auto_scheduled": false,
            "infrastructure_document_id": null,
            "infrastructure_pid": null,
            "created_by": {
                "id": "34e9ed52-f547-408e-b53d-02968ba97d64",
                "type": "USER",
                "display_value": "theta457-edison"
            },
            "work_pool_id": null,
            "work_pool_name": null,
            "state": {
                "id": "70736b0e-75e2-4156-8bca-8a21f4c538e4",
                "type": "SCHEDULED",
                "name": "Scheduled",
                "timestamp": "2024-04-30T09:41:40.633516+00:00",
                "message": null,
                "data": null,
                "state_details": {
                    "flow_run_id": "c5feefe0-e932-4f1e-9055-03155561938d",
                    "task_run_id": null,
                    "child_flow_run_id": null,
                    "scheduled_time": "2024-04-30T09:41:40.633473+00:00",
                    "cache_key": null,
                    "cache_expiration": null,
                    "untrackable_result": false,
                    "pause_timeout": null,
                    "pause_reschedule": false,
                    "pause_key": null,
                    "run_input_keyset": null,
                    "refresh_cache": null,
                    "retriable": null,
                    "transition_id": null,
                    "task_parameters_id": null
                }
            },
            "job_variables": {
                "var1": "value1",
                "var2": "value2"
            }
        },
        "errors": []
    }
}

Code Block

title	Flow Reached in a Failed State
collapse	true

{
    "exit_code": 0,
    "status_description": "Execution Failed: Flow run Reached CRASHED State",
    "invocation": {
        "fields": {...}
    },
    "result": {
        "flow_run_info": {
            "id": "4cbbeb73-2438-4155-8e20-196e5f53c558",
            "created": "2024-04-30T09:47:08.664604+00:00",
            "updated": "2024-04-30T09:47:22.588768+00:00",
            "name": "mydummyname",
            "flow_id": "6342cf22-2baa-4b4f-8c7f-85d731055af8",
            "state_id": "969d5d10-9e43-48f3-ba36-b81c9808687f",
            "deployment_id": "ef8baf82-a14b-472f-9f8d-5424b66f232d",
            "work_queue_id": null,
            "work_queue_name": null,
            "flow_version": "49e24154c00009d471e26e915271e743",
            "deployment_version": "49e24154c00009d471e26e915271e743",
            "parameters": {
                "fail": true,
                "sleeptime": 5
            },
            "idempotency_key": null,
            "context": {
                "context1": "value1",
                "context2": "value2"
            },
            "empirical_policy": {
                "max_retries": 0,
                "retry_delay_seconds": 0,
                "retries": 0,
                "retry_delay": 0,
                "pause_keys": [],
                "resuming": false
            },
            "tags": [
                "testing",
                "telis 1",
                "telis 2"
            ],
            "parent_task_run_id": null,
            "state_type": "CRASHED",
            "state_name": "Crashed",
            "run_count": 1,
            "expected_start_time": "2024-04-30T09:47:08.664475+00:00",
            "next_scheduled_start_time": null,
            "start_time": "2024-04-30T09:47:17.117950+00:00",
            "end_time": "2024-04-30T09:47:22.582148+00:00",
            "total_run_time": 5.464198,
            "estimated_run_time": 5.464198,
            "estimated_start_time_delta": 8.453475,
            "auto_scheduled": false,
            "infrastructure_document_id": null,
            "infrastructure_pid": null,
            "created_by": {
                "id": "34e9ed52-f547-408e-b53d-02968ba97d64",
                "type": "USER",
                "display_value": "theta457-edison"
            },
            "work_pool_id": null,
            "work_pool_name": null,
            "state": {
                "id": "969d5d10-9e43-48f3-ba36-b81c9808687f",
                "type": "CRASHED",
                "name": "Crashed",
                "timestamp": "2024-04-30T09:47:22.582148+00:00",
                "message": "Execution was aborted by Python system exit call.",
                "data": null,
                "state_details": {
                    "flow_run_id": "4cbbeb73-2438-4155-8e20-196e5f53c558",
                    "task_run_id": null,
                    "child_flow_run_id": null,
                    "scheduled_time": null,
                    "cache_key": null,
                    "cache_expiration": null,
                    "untrackable_result": false,
                    "pause_timeout": null,
                    "pause_reschedule": false,
                    "pause_key": null,
                    "run_input_keyset": null,
                    "refresh_cache": null,
                    "retriable": null,
                    "transition_id": "bcd4ea0a-f7e5-40ef-a492-5ce17bdd8651",
                    "task_parameters_id": null
                }
            },
            "job_variables": {
                "var1": "value1",
                "var2": "value2"
            }
        },
        "errors": [
            "Flow run Reached CRASHED State"
        ]
    }
}

Input Fields

...

The action performed upon the task execution.

Prefect Cloud - Launch Flow Run (default)

...

Introduced in 1.0.0

...

Credentials for Prefect Cloud. The Credentials definition should be as follows.

Account ID as "Runtime User".
Account KEY as "Runtime Password".

...

Introduced in 1.0.0

...

Defines the Workspace for Flow Run execution. Task authors can use directly the Workspace ID by copy pasting it from Prefect UI, enter the name of the Workspace or use the Dynamic Choice functionality to list the available Workspaces names that are applicable under the specific Account.

...

Introduced in 1.0.0

...

Defines the Deployment of Flow. Task authors can use directly the Deployment ID by copy pasting it from Prefect UI, enter the name of the Deployment or use the Dynamic Choice functionality to list the available Deployments.

...

Introduced in 1.0.0

...

Flow Run Name

...

The name of the flow run. Defaults to a random slug if not specified.

...

Introduced in 1.0.0

...

Additional Optional Parameters

...

Used to show/hide additional optional parameters for the Flow Run.

...

Introduced in 1.0.0

...

Parameters (JSON)

...

This is a JSON structure that provides additional optional parameters that can be passed. A default value is provided so users can easily edit the required parameters if required, and it is not intended to be used as-is. The default value provides the following elements.

parameters: it is an object that represents the parameters of the Flow Run. As an object it can contain JSON elements of any type.

context: it is an object that represents the context of the Flow Run. As an object it can contain JSON elements of any type.

job_variables: it is an object that represents the job variables of the Flow Run. As an object it can contain JSON elements of any type.

tags: it is a list of strings that represents a list of tags associated with this Flow Run.

Available if “Additional Optional Parameters” is checked.

...

Introduced in 1.0.0

...

Wait for Success or Failure

...

If selected, the task will continue running until Job reaches the "COMPLETED" or "FAILED" state. "CRASHED", "CANCELLED" are also considered "FAILED" states.

...

Introduced in 1.0.0

...

Polling Interval (sec)

...

The polling interval in seconds for the Flow Run State check.

Defaults to 60 seconds.

Required when Wait for Success or Failure is checked.

...

Introduced in 1.0.0

...

Max Number of Polls

...

Maximum number of polls. Can be used to control the approximate expected duration of the Flow Run (in relation also to Polling Interval (sec)).

If left empty the UAC Task will poll indefinitely checking whether the Flow Run is completed or resulted in failure. If the Maximum Number of Polls is reached the exit code of the task will be 40.

Available if Wait for Success or Failure is checked.

...

Introduced in 1.0.0

...

Extension Output Options

...

User can decide the content of Extension Output using the following options.

“--None--”.
“Include latest Flow Run information”. In this case the latest Flow Run information retrieved from Prefect is available on the Extension output.

...

Introduced in 1.0.0

Output Fields

...

Flow Run ID

...

The Flow Run ID provided by Prefect.

...

Flow Run Name

...

The Flow Run Name. If input field Flow Run Name is not provided, then a random slug is generated by Prefect.

...

Flow Run State

...

The latest Flow Run execution state retrieved by Prefect.

...

Cancelation and Rerun

In case of cancellation, the Flow Run is not canceled on Prefect. In case of Re-Run, the Flow Run will be re-executed from scratch.

...

Exit Codes

Universal Task allows command execution on Windows and on Linux. If the command requires a file, users can optionally include a local file or create a file on the Agent, allowing the Controller to serve as the source for the file.

Key Features

Feature

Description

Run Command

Execute a Windows or Linux command as if it were run from a user's default shell. Full command lines are supported, and commands can either be located on the system's PATH or executed via full file paths, as is typical in a command-line environment.

In the Optional Additional File field, a file can be used either as a parameter in the command or as a script to be executed with an interpreter.

Task Output

STDERR and STDOUT are captured in near real-time during command execution, which is essential for monitoring long-running tasks.
If the command outputs JSON to STDOUT, it is included in the EXTENSION_OUTPUT in JSON format, ensuring standardized information flow to subsequent tasks in the workflow.

Anchor
Requirements
Requirements
Requirements

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

Area

Details

Python Version

Requires Python of version 3.7 or 3.11. Tested with the Universal Agent bundled Python distribution.

Universal Agent

Both Windows and Linux agents are supported:

Universal Agent for Windows x64 Version >= 7.4.0.0
Universal Agent for Linux Version >= 7.4.0.0

Universal Controller

Universal Controller Version >= 7.4.0.0

Anchor
Supported Actions
Supported Actions
Supported Actions

Action: Run Command

Users can execute a single command by specifying the command and its parameters. Full command lines are also supported. The command can be executed if it is available in the PATH environment variable; otherwise, the full path to the command must be provided.

Task authors may optionally include an additional file on the agent, which can be used either as part of the command parameters or as a script to be executed via the command line, using the interpreter of their choice. The contents of this file are stored as a Univeral Controller Data Script. This feature is particularly useful when the required files are not present on the agent’s filesystem, allowing the Controller to serve as the source for these files. The additional file can be accessed using the UE_CMD_ADDFILE environment variable. This environment variable is set internally and can be used within the command line. When running scripts on Windows, the Script name needs to include the file extension. For example, a batch file should be named <name>.bat, and a PowerShell script should be named <name>.ps1.

Configuration examples

This extension enables a wide range of shell functionalities, including command stacking, conditional execution, and output redirection. Additionally, users can directly execute scripts provided inside of the Optional Additional File field, by specifying an interpreter in the command and referencing the provided script through the UE_CMD_ADDFILE environmental variable. Below are some configuration examples:

Info

Task authors should consider the following best practices:

Although the Runtime Directory field is optional, it is strongly recommended to configure it. This provides clarity about the directory from which the command or script is executed.
Thoroughly test your commands before running them in production to avoid any unintended behavior.
Although not always necessary, it is recommended to quote the environmental variable UE_CMD_ADDFILE when attempting to reference it, as there is a chance for the path to it to contain spaces.

OS

Task Configuration

Scenario/Description

Linux

Image Added

Scenario: Execution of an ls command.

Task instance success or failure depends on the exit code of the command being executed. If the command is executed with exit code = 0, the task instance completes with Success status. Otherwise, the task instance status is Failed with exit code = 1.

This example shows the execution of an ls command, including outputs for both success and failure cases.

Code Block

language	js
title	Extension Output when File exists
linenumbers	true
collapse	true

{
	"exit_code": 0,
	"status_description": "Task executed successfully",
	"invocation": {
		"extension": "ue-cmd",
		"version": "1.0.0",
		"fields": { ... }
	},
	"result": {
		"metadata": {
			"runtime_directory": "/tmp",
			"command": "ls existing_file.txt",
			"exit_code": 0
		},
		"command_json_output": "existing_file.txt"
	}
}

Code Block

language	js
title	Extension Output when File does not exists
linenumbers	true
collapse	true

{
	"exit_code": 1,
	"status_description": "Execution returned exit code other than 0",
	"invocation": {
		"extension": "ue-cmd",
		"version": "1.0.0",
		"fields": { ... }
	},
	"result": {
		"metadata": {
			"runtime_directory": "/tmp",
			"command": "ls non_existent.txt",
			"exit_code": 2
		},
		"command_json_output": null
	}
}

Linux

Image Added

Scenario: Command execution that produces a valid JSON result.

This example shows a command that produces JSON output on STDOUT. In such a case, the output is also visible in the task instance EXTENSION output.

Code Block

title	Extension Output containing JSON object
linenumbers	true
collapse	true

{
	"exit_code": 0,
	"status_description": "Task executed successfully",
	"invocation": {
		"extension": "ue-cmd",
		"version": "1.0.0",
		"fields": {
			"action": "Run Command",
			"command": "echo '{\"name\": \"John\", \"age\": 30, \"city\": \"Athens\"}'",
			"additional_file": null
		}
	},
	"result": {
		"metadata": {
			"runtime_directory": "/tmp",
			"command": "echo '{\"name\": \"John\", \"age\": 30, \"city\": \"Athens\"}'",
			"exit_code": 0
		},
		"command_json_output": {
			"name": "John",
			"age": 30,
			"city": "Athens"
		}
	}
}

Linux

Image Added

Scenario: Execution of a shell script stored in the Controller.

The example shows execution of script.sh. Environment variable ${UE_CMD_ADDFILE} points to the script full path referenced from Optional Additional File field.

Note: In this example, the reference to the environmental variable UE_CMD_ADDFILE is surrounded by quotes. This was done because the path to this variable contains spaces, so it must be quoted in order for the shell to resolve it correctly.

Linux

Image Added

Scenario: Conditional execution of commands.

This example shows a scenario that depends on the result of grep. If there is a pattern match, a success message is displayed; otherwise, an error message is printed to indicate the pattern wasn't found.

Linux

Image Added

Scenario: Command Stacking.

This example shows multiple commands being executed:

execute a shell script provided in the Optional Additional File field
pause for 2 seconds
print a message indicating that execution has completed.

Linux

Image Added

Scenario: Redirection of output.

In this example, the contents of the current directory are listed in long format using ls -l, and then redirected to the output.log file. Afterwards, the contents are displayed through the cat command.

Windows

Image Added

Scenario: PowerShell script execution.

The example shows execution of a PowerShell script provided by the Optional Additional File field referenced through the UE_CMD_ADDFILE environment variable.

Info
PowerShell can execute scripts when related execution policy is granted. For more information, refer to the official Microsoft website.

Info
PowerShell Scripts need to be saved with a .ps1 extension.

Windows

Image Added

Scenario: Execution of a batch file.

The example shows execution of a batch file provided by the Optional Additional File field referenced through the UE_CMD_ADDFILE environment variable.

Info
Batch Scripts need to be saved with a .bat extension.

Action Output

Output Type

Description

Example

EXTENSION

The extension output follows the standard Extension Output format, providing:

exit_code, status, status_description: General info regarding the task execution.
invocation.fields: The task configuration used for this task execution.
result.metadata:
- runtime_directory: The directory on the Agent Host just before the execution of the command or script
- command: The resulting command line
- exit_code: The command line exit code
result.command_json_output: The JSON result if the STDOUT of the executed command is either a JSON object or a JSON primitive.

Code Block

language	js
title	Extension output for a simple command line execution
linenumbers	true
collapse	true

{
	"exit_code": 0,
	"status_description": "Task executed successfully.",
	"invocation": {
		"extension": "ue-cmd",
		"version": "1.0.0",
		"fields": {...}
	},
	"result": {
		"metadata": {
			"runtime_directory": "/home/user/dir",
			"command": "cat ${UE_CMD_ADDFILE}",
			"exit_code": 0
		},
		"command_json_output": null
	}
}

Code Block

language	js
title	Extension output in case the STDOUT of the executed command is in JSON format
linenumbers	true
collapse	true

{
	"exit_code": 0,
	"status_description": "Task executed successfully",
	"invocation": {
		"extension": "ue-cmd",
		"version": "1.0.0",
		"fields": {...}
	},
	"result": {
		"metadata": {
			"runtime_directory": "/tmp",
			"command": "echo '{\"name\": \"John\", \"age\": 30, \"city\": \"Athens\"}'",
			"exit_code": 0
		},
		"command_json_output": {
			"name": "John",
			"age": 30,
			"city": "Athens"
		}
	}
}

Code Block

language	js
title	Extension output in case of failure.
linenumbers	true
collapse	true

{
	"exit_code": 1,
	"status_description": "Execution returned exit code other than 0",
	"invocation": {
		"extension": "ue-cmd",
		"version": "1.0.0",
		"fields": {...}
	},
	"result": {
	"metadata": {
		"runtime_directory": "/home/user/dir",
		"command": "cat ${UE_CMD_ADDFILE}",
		"exit_code": 1
	},
	"command_json_output": null
	}
}

STDOUT

The STDOUT of the executed command also appears on the STDOUT of the Universal Task.

STDERR

Provides messages from the task instance itself, and from the STDERR or the executed command for informational & debugging purposes. Messages produced by the executed command are prefixed with [[CMD]]

Anchor
Input Fields
Input Fields
Input Fields

Field	Type	Description	Version Information
Action	Choice	The action performed upon the task execution. Available options: Run Command	Introduced in 1.0.0
Optional Additional File	Script	An optional field to include a file used either as a parameter in the command or as a script to be executed with an interpreter. This file can be referenced in the command line using the UE_CMD_ADDFILE environment variable. This field is particularly useful when the required files are not present on the agent’s filesystem, allowing the Controller to serve as the source for these files.	Introduced in 1.0.0
Command	Large Text	The Command Line to be executed. It should be provided as a single line. Any additional lines will be ignored. Environment variable UC_CMD_ADDFILE can be used here to reference the additional file provided. Required when Action is “Run Command”	Introduced in 1.0.0
Runtime Directory	Text	The Runtime Directory just before the execution of the command. While the Runtime Directory field is not mandatory, it is highly recommended to be configured. This ensures clarity about the directory from which the command is executed	Introduced in 1.0.0

Anchor
Exit Codes
Exit Codes
Exit Codes

In case Wait for Success or Failure input field is checked it means that the Flow Run ended up in a Success State.

In case Wait for Success or Failure input field is not checked it means that the Flow Run has been successfully triggered

Exit Code	Status	Status Description	Meaning
0	Success	“Task executed successfully. “

Successful Execution.

If the executed command succeeds, it returns an exit code of 0. The task will reflect this success by also returning exit code = 0.
1	Failure

“Execution

““Execution Failed: <<Error Description>>”

Failed Execution.

In case Wait for Success or Failure input field is checked it means that the Flow Run ended up in a Failed State.

This error code also acts as a generic error code. Raised when error not falling into the other error scenarios

This indicates that the executed command failed, or the task itself failed for some other reason.
20	Failure	“Data Validation Error: <<Error

Description>>“

Description>> “

Input fields validation

error.40Failure

“Polling Timeout: maximum polling timeout reached.“

The Flow Run is executed out of the normal duration boundaries.

STDOUT and STDERR

STDOUT is empty, while STDERR provides additional information to the user.

...

error.

Anchor
STDOUT and STDERR
STDOUT and STDERR
STDOUT and STDERR

STDOUT of the Task Instance includes the STDOUT of the executed command.
STDERR of the Task Instance provides log messages of the task, as well as the STDERR messages from the executed command. The messages from the executed command are prefixed with [[CMD]]. STDERR is for user information purposes. It is not advised to be used for machine processing (like workflow logic).

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

Anchor
How To
How To
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. Anchorintegration_modificationsintegration_modifications

Integration Modifications 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",

...

- - "Icon" should not be changed.
- Universal Template Details Section
  - "Template Type", "Agent Type", "Send Extension Variables",

...

- - "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

...

- Fields Restriction Section
  The setup of the template does not impose any restrictions

...

- , however with respect to "Exit Code Processing Fields" section.

...

- 1. Success/Failure exit codes need to be respected.

...

- 1. 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

...

- 1. success or failure of a task.

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

Anchor
Document References
Document References
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.

Anchor

...

Changelog

...

Changelog

...

Changelog

ue-

...

cmd-1.0.0 (2024-

...

10-

...

31)

Initial Release supporting Flow Run executions on Prefect Cloud.

Version	Old Version 1	New Version Current
Changes made by	Aristotelis Sdrolias	Alec Berger
Saved on	Oct 11, 2024	Nov 05, 2024

Content Comparison

Versions Compared

Key

AnchorDisclaimerDisclaimerDisclaimer

Overview

Key Features

Version Information

AnchorVersion InformationVersion InformationVersion Information

AnchorOverviewOverviewOverview

Supported Actions

Action: Prefect Cloud - Launch Flow Run

Configuration examples

Action Output

Input Fields

Output Fields

Cancelation and Rerun

Exit Codes

Key Features

AnchorRequirementsRequirementsRequirements

AnchorSupported ActionsSupported ActionsSupported Actions

Action: Run Command

Configuration examples

Action Output

AnchorInput FieldsInput FieldsInput Fields

AnchorExit CodesExit CodesExit Codes

STDOUT and STDERR

AnchorSTDOUT and STDERRSTDOUT and STDERRSTDOUT and STDERR

AnchorHow ToHow ToHow To

Import Universal Template

Configure Universal Task

Integration Modifications Modifications

AnchorDocument ReferencesDocument ReferencesDocument References

Anchor

Changelog

Changelog

Changelog

ue-

cmd-1.0.0 (2024-

10-

31)

Anchor
Disclaimer
Disclaimer
Disclaimer

Anchor
Version Information
Version Information
Version Information

Anchor
Overview
Overview
Overview

Anchor
Requirements
Requirements
Requirements

Anchor
Supported Actions
Supported Actions
Supported Actions

Anchor
Input Fields
Input Fields
Input Fields

Anchor
Exit Codes
Exit Codes
Exit Codes

Anchor
STDOUT and STDERR
STDOUT and STDERR
STDOUT and STDERR

Anchor
How To
How To
How To

Anchor
Document References
Document References
Document References