How to import solutions

There are two ways to import solutions into Teneo: as a new solution or import into an existing solution.

Import as a new solution

Importing a solution as a new solution results in a new, isolated solution that is a copy of the imported solution. It has no dependency on other solutions. This is the safest way to import solutions. To import a solution as a new solution, proceed as follows:

  1. Open Teneo and go to the solutions' overview (if you have a solution open, you need to close it to go there).
  2. Drag the solution you want to import into the solutions list.
  3. In the window that appears, click 'OK' (if you want you can change the name and description).

The solution will be imported. This may take a while. You will be notified when the import is ready.

In most cases the solution you imported will make use of a Teneo Language Resource (TLR). To assign it, proceed as follows:

  1. Open the solution
  2. Go to Resources, and click on 'Lexical' to handle Lexical Resources.
  3. Click Assign Lexical Resource in the upper right corner, and select the appropriate 'Teneo Lexical Resources' in the drop-down.

Import into Teneo Dialogue Resources

Many of the prebuilt solutions work best when they are imported into a solution which is based on Teneo Dialogue Resources. There are two things we need to do: first create a new empty solution based on Teneo Dialogue Resources and then to import another solution into this solution.

This is how you go about to create a new solution based on Teneo Dialogue Resources. (A more detailed illustration of this process can be found here)

  1. Open Teneo and go to the 'Solutions' overview.
  2. Add a new solution using the green button, to the left, select English as the language and to the right, click 'create from Template' and select 'Teneo Dialogue Resources English' in the drop-down.
  3. Once created, open the solution.
  4. Got to Resources and click on 'Lexical' to handle Lexical Resources.
  5. Click 'Assign Lexical Resource' in the upper right corner and select 'Teneo Lexical Resources English' in the drop-down.
  6. Close the solution.

Now it's time to import the new solution into this existing solution:

  1. Go to Teneo's solutions overview.
  2. Select the solution that you have created in the previous step.
  3. In the top right corner, choose 'Edit'.
  4. In the window that appears, on the right (Solution Content) choose 'Import additional content from file'.
  5. Click 'Browse...' to find the pre-built solution that you previously downloaded from the Prebuilt solutions page that you want to import.
  6. Click 'Open' and then click 'OK' to start he import.

That's it you are now ready to use the prebuilt solution together with the advantages of the Teneo Dialogue Resources.

Import into an existing solution (merging solutions)

Importing into an existing solution will add all assets (flows, language objects, variables, global scripts etc) of the imported solution to your existing solution. These are the steps involved to import into an existing solution:

  1. Open Teneo and go to the solutions' overview (if you have a solution open, you need to close it to go there).
  2. Select the solution that you wish to import another solution into.
  3. In the top right corner, choose 'Edit'.
  4. In the window that appears, on the right (Solution Content) choose 'Import additional content from file'.
  5. Click 'Browse...' to find the solution you want to import and click 'Open'.
  6. Click 'OK' to start the import.

The solution will be imported. This may take a while. You will be notified when the import is ready.

Merging conflicts

When importing a solution into an existing solution, merging conflicts can occur. For example, the existing (or host) solution may have assets with the same name, like folders or variables. It's possible that assets in the host solution are overwritten by the assets in the imported solution. Since merging solutions cannot be undone, it is very important to verify that no conflicts will arise before you import a solution into an existing solution. If you don't know what is exactly included in the solution that you are about to import, you may want to first import the solution as a new solution so you can safely check global scripts, global variables and other elements.

Assets that can be overwritten when merging:

  • Global scripts
    If the imported solution contains non-empty global scripts, they will overwrite the ones in the host solution. Empty global scripts in the imported solution are ignored.
  • Global variables
    If a global variable in the imported solution has an identical name as one in the host solution, the global variable of the imported solution will overwrite the one in the host solution, even if the value is empty.
  • Metadata
    Metadata fields in the imported solution with duplicate names will overwrite those of the host solution. This is the case even if the value in the imported solution is the default value.
  • Confidence Threshold
    The confidence threshold of the imported solution overwrites the threshold set in the host solution. (Confidence threshold is found in Solution Properties.)

Assets that will be retained when merging but may require attention after importing:

  • Language objects
    Language objects from the imported solution with identical names to those in the host solution (no matter in which folder they are stored) will have the suffix _1 added to their name. Note, however, that language conditions will not be updated. If a language condition in the imported solution contains a reference to a language object or entity that has been renamed after the import, it will then refer to the language object or entity in the host solution. The original language objects in the host solution should be reviewed and updated with the appropriate values. The duplicate <language object>_1 objects should then be removed.
  • Entities
    Entities from the imported solution with identical names to those in the host solution (no matter in which folder they are stored) will have the suffix _1 added to their name. Note, however, that entities will not be updated. If an entity in the imported solution contains a reference to a language object or entity that has been renamed after the import, it will then refer to the language object or entity in the host solution. The original entities in the host solution should be reviewed and updated with the appropriate values. The duplicate <entity>_1 objects should then be removed.
  • Order groups
    If both solutions contain order groups with the same name, the triggers in the imported solution will be added to the same group in the host solution. Also the order of the same-named groups is defined by the imported solution, as is the choice for default order group. In general, it is best to make sure that the imported solution and the host solution don't contain identical order group names. That way it is easier to tune the ordering after the import. After completing your import be sure to review the choice of default order group as well as the relative ordering of all the groups.
  • Class Intents
    Class intents with the same name will be imported with the suffix 1.
  • Folders
    Folders with the same name and the same level will be imported with the suffix 1.
  • Flows
    Flows will be retained as is in their folder. As noted above, folders with duplicate names will be added with a suffix, so even flows with identical names in identical folders will be retained.
  • Global Listeners
    Global listeners with the same name will be imported and have the suffix 1 added to their names.
  • Global contexts
    Global contexts with the same name will be imported and have the suffix 1 added to their names.
  • Integrations
    Integrations with the same name will be imported and have the suffix 1 added to their names.
  • Files in the Resource file manager
    All files from both solutions will be retained in the result solution. Those with identical names will not be overwritten, but the imported resource files will be added to the end of the list of the existing files. You should manually remove duplicate files.

Prebuilt solutions

The prebuilt solutions are designed in a way that minimizes conflicts when merging. However, it is advised to verify that no merging conflicts will occur before you start. On the information page for each prebuilt solution you will find a table of all components (flows, global variables etc) that are included in the solution. This allows you to assess if merging the solution with your own solution can do harm.

Was this page helpful?