Node Information During Workflow Import/Export | Vantage Analyst - Handling Node Information - Teradata Analytic Apps - Vantage Analyst

Vantage Analyst User Guide

Product
Teradata Analytic Apps
Vantage Analyst
Release Number
1.4.1
Published
May 2022
Language
English (United States)
Last Update
2022-05-09
dita:mapPath
ufz1626905554941.ditamap
dita:ditavalPath
wsp1565965728073.ditaval
dita:id
B035-3805
Product Category
Teradata Applications

When you import or export workflows, some nodes do not include the underlying information.

History and Schedule Information

Workflow Run History and Schedule settings are not included when importing or exporting workflows.

You must create a new schedule for each exported or imported workflow or customer list.

Connection Information

For security reasons, when you import or export workflows, the specific login information for database, API, and SFTP connections is not included in the export.

Although the system will create the basic connection information (if it does not already exist), you must edit the necessary connections to add the specific login details.

Action Taken When Workflow with Identical Name is Imported

When you import workflow objects with an identical name, the import skips those objects (workflow name, connection name, variables). For example:
  • A sub-workflow in a parent workflow has an identical name to one already in the system. The sub-workflow is not imported; the parent workflow is imported using the existing sub-workflow.
  • An SQL node in a workflow has an identical database connection name to one already in the system. The database connection is not imported; the workflow is imported using the existing database connection name for the SQL node.