There are three ways to import solutions into Teneo: as a new solution, by importing into Teneo Dialogue Resources, or by importing into an existing solution.

Import as a new solution

Importing 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 carry out imports. To do this, proceed as follows:

1. Open Teneo and go to the solutions' overview (if you have a solution open, you will need to close it to see the overview).
2. Click on 'Import/Export' in the menu, followed by 'Import Solution', and select the solution file (alternatively, drag the solution you want to import into the solutions list).
3. In the window that appears, click 'Next'.
4. If you want to, change the name and description, then click 'OK'.

The solution will be imported. This may take a while. You will be notified when the import is ready, at which point you can click on 'Open Solution' to open it.

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 when importing into an existing solution:

1. Open Teneo and go to the relevant solution you want to merge with.
2. Navigate to the solution backstage and click on 'Import/Export'.
3. Click on 'Add Content' followed by the solution you want to merge.
4. Feel free to add a comment (this is recommended when performing big actions as it will be shown in the solution history), and select 'Continue'.

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

Import into Teneo Dialogue Resources

Many of the prebuilt solutions work best when they are imported into a solution based on the Teneo Dialogue Resources template. To achieve this, there are two things we need to do: create a new empty solution based on Teneo Dialogue Resources and then import another solution into this solution.

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

1. Select 'Solutions' in the menu.
2. Click the 'New' button in the upper right corner. This opens a dialog box.
3. Set the language to English. This will be the mother tongue of your bot. Under 'Solution Content', choose 'Create from Template' and select the latest version of 'Teneo Dialogue Resources English' from the list. This will boost your bot with lots of pre-built flows. The bot will then, right out of the box, understand and respond to greetings, meta-requests (like 'Can you repeat that?'), feedback (like 'Great!' or 'You are funny') and conversational small talk.
4. Click on 'Next' and fill in a name for your solution.
5. Click 'OK'. It may take a couple of minutes for your solution to be created. You will be notified when it’s done.

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

1. Open Teneo and go to the relevant solution you want to merge with.
2. Navigate to the solution backstage and click on 'Import/Export'.
3. Click on 'Add Content' followed up with the solution you want to merge.
4. Feel free to add a comment (this is recommended when performing big actions as it will be shown in the solution history), and select 'Continue'

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

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 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 information on components that are included in the solution. This allows you to assess whether merging the solution with your own solution could do any harm.