How to Export Tasks and Connections

Introduction

This article describes how to export global configurations (creates a .CONNECTION file) and tasks with their associated task data (creates a .TKS file).

What Can Be Exported?

Note: User accounts, tasks in the recycle bin, and Agent configurations (Microsoft SQL Server Trigger The Microsoft SQL Server Trigger tool uses the Microsoft® SQL Server™ trigger functionality to create a trigger on a table of a specified SQL data source. When a specified data modification is attempted, such as an attempt to add or delete a table row, the trigger then causes a task to run. Agent, Email Trigger (SMTP) The Email Trigger (SMTP) tool triggers a task to run based on the contents of incoming or outgoing mail sent via an SMTP mail server. Agent, and Workflow Job Trigger The Workflow Job Trigger tool triggers a task to run when responses from Workflow Jobs match criteria specified in one or a number of filters. Agent) are not included in the tasks or connection files.

Objects Included in the .TKS File

You can export a mix of the following to a .TKS file:

►

Task folders and contents

Sub-folders are automatically included when the parent folder is selected. If sub-folders are not required, you can clear the selection before exporting.

►

Tasks and associated properties

Associated task data is included when a task is exported, that is, task variables Variables are created and used extensively throughout and can either have fixed values or values that are dynamically populated when a task is run. Task variables are only available for the specific task they are created for. Users with Task Administrator rights can create task variables., task formulas, task functions, memory definitions Memory definitions specify the data, generated by a task at run-time, to be memorised. You can save memorised data in an internal Repository, in an ODBC or OLEDB data source, or in an OLEDB data source via a stored procedure., and repositories Repositories are used by the Internal Memory feature to store memorised data in BPA Platform's proprietary database format. as well as the task process itself.

►

Repositories

Note that repositories can be separately exported through the Repository interface (see How to Export Tasks and Connections). This method creates an .XML or .CSV file instead.

►

Global formulas

►

Global functions

►

Global variables

Objects Included in a .CONNECTION File

You can export the following to a .CONNECTION file:

►

Any global connection or configuration created in your BPA Platform instance

Note: When exporting the global configuration for the Call Task The Call Task tool is used to trigger an external task to run. Using variables, BPA Platform data can be passed between the two tasks at run-time, if required. tool, any users created specifically for this tool are not included in the export. These must be recreated manually in the new BPA Platform instance before importing the .CONNECTION file.

Exporting Tasks and Task Data

You use the Export interface to export tasks and task data:

Click the image to view full size.

Exporting a Specific Task

If exporting a specific task or task folder, do the following:

Right-click the required task or task folder and select Export.
Go to the Tasks tab.
If the tasks make use of global variables Variables are created and used extensively throughout and can either have fixed values or values that are dynamically populated when a task is run. Global variables are available for all tasks in this BPA Platform installation. Once created, global variables can be used by any task., formulas, or functions, expand those nodes and select the required objects.
Click (Export) to create the .TKS file in your preferred location.

Exporting All Tasks

If exporting all or a selection of existing tasks and task data, do the following:

From the Tasks toolbar, click (Export).
Go to the Tasks tab.
Select the required objects to export.
Use (Select All) to select all objects.
Click (Export) to create the .TKS file in your preferred location.

Why Can't I Select a Specific Task?

You may find that you are unable to select a specific task in the Export interface:

Export - Unable to select task

This is because that task is currently being edited, either in the same BPA Platform instance where the export is happening or in a remote client instance. Ensure all tasks are closed before exporting; note that tasks that are active (running) have no impact on the export.

Exporting Global Configurations

Unlike when exporting a task, you do not need to be in the Tools section of the resources tree when exporting global configurations.

From the Tasks toolbar, click (Export).
In the Export interface, go to the Connections tab.
Click the image to view full size.
Select those connections you want to export.
Use either (Select All) or Connections to select all existing global connections.
Click (Export) to create the .CONNECTIONS file in your preferred location.