Task Export and Import

Export a task. Share the task with other account holders so they can import it.

Task Export

Follow these steps to export a task.

1. From the Build menu, click Tasks to open the tasks card deck.

2. Right click the three dots ... in the top right corner of the task card.

   

3. To export the task, select Export. To create a template from the task, select Publish.

4. Check the inventory of elements in the task.

   Itinerary Section	Description
   Overview	Shows the number of canvases, nodes, and node types in the task.
   Nodes	Shows the types of nodes in the task and the number of times they are used.
   Content	Shows the types of content items in the task and the number of times they are used.
   Advanced Content	Shows specialized content used by the task, such as authentication profiles.

   

5. If elements of the inventory have an associated Configure link, click those links to verify configuration settings.

   Following are some examples of elements with configuration links.

   Element	Configuration
   Secure Variable	Use to indicate whether to export the secure variable value. By default, the value is not exported.
   Authentication Profile	Use to indicate whether to export sensitive credentials like the key file and password. By default, the sensitive credentials are not exported.
   Datastore	Use to indicate whether to export the datastore values. By default, the datastore values are not exported.

Task Import

Follow these steps to import a task.

1. From the Build menu, select Tasks.

2. Click the create button in the top right corner.

   

3. Click Import Task.

   

4. Fill in the Task Properties.

5. Specify how to import content items associated with the task.

   Component	Description
   Suffix for newly created content items	Type the suffix to apply to imported content items with name conflicts. If this field is left blank, the first six characters of the task name are used as a suffix. A content item is renamed from the original task if a content item with the same name already exists in the account.
   Datastores	You can request that the task use a datastore already existing in the account if the datastore name is the same as that for the original task. Otherwise, a new datastore is created. You can request that the task use the original datastore values if known. Otherwise, the initial values for the datastore are the existing values in an existing datastore or empty values in a new datastore.
   Secure variables	Secure variables store credentials in a fully encrypted manner. You can request that the task use a variable already existing in the account if the variable name is the same as that for the original task. Otherwise, a new variable is created. You can request that the task use the original secure value if known. Otherwise, the initial value for the variable is blank, and you must assign a value to the variable once import is complete.
   Redirect currently linked tasks	This section is relevant if the newly imported task is replacing a task. Select the task this task is replacing. The import process updates other tasks in the Studio account to link to this task (the task you are importing) in place of the selected task. For example, task A links to task B through a link task node. Task C is being imported to replace task B. Select task B so on import the link task node in task A links to task C in place of task B.
   Link task nodes	In a call flow, the link task node routes the call to another task within the account. Studio lists each link task node in the task you are importing. For each link task node, select a task in this account to link to. If no task is selected, the link task node is converted to a comment node.
   Authentication profiles	Authentication profiles store credentials for use in an integration node. If you leave this field blank, a new authentication profile is created in the account. The profile values are recreated from the original task. If the authentication profile is missing sensitive credentials, those fields are left blank, and the integration node displays a status error against the profile until you add new credentials. You can assign to the integration node an authentication profile that already exists instead of creating a new authentication profile. The list of authentication profiles is ordered so those most similar to that used in the original task are listed first. Note: This icon in the user interface indicates the authentication profile is missing sensitive credentials.