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

Vantage Analyst with Machine Learning Engine User Guide

Product
Teradata Analytic Apps
Vantage Analyst
Release Number
1.1
Published
December 2019
Language
English (United States)
Last Update
2020-08-06
dita:mapPath
ezh1551894635141.ditamap
dita:ditavalPath
wsp1565965728073.ditaval

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

Node Type Action

Rule

You must create a new rule and assign it to the node.

API or SFTP You must create a new API or SFTP data integration and assign it to the relevant node.
Nodes that include database, API, or SFTP connection information API and SFTP connections are not included when importing or exporting.

For security reasons, database connections include only the connection name and description when importing or exporting.

When importing a workflow, you must create or edit the necessary connections (if they do not already exist).

Workflow Run History and Schedule settings are not included. You must create a new schedule for each exported or imported workflow.

Action Taken When Workflow with Identical Name is Imported

When you import workflow objects with an identical name, the import will skip 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 will not be imported; the parent workflow will be 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 will not be imported; the workflow will be imported using the existing database connection name for the SQL node.