How to import solutions

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 return back it to the overview).
2. Select the 'Create' icon at the bottom right corner to create a solution.
3. Click on 'Import Solution', and select the solution file (alternatively, drag the solution you want to import into the solutions list).
4. If you want to, change the name and description, then click 'Create'.

The solution will be imported. This may take a while. But you will be able to open the solution once the importing is finished.

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. Click on the 'Info' button located at the ribbon bar.
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 'Save'.

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 the 'Create' icon at the bottom right corner to create a solution.
2. Select a solution language for your first bot. This will be the mother tongue of your bot. For this example, we will use English.
3. Under 'Solution Content', choose 'Create from Template' and select the latest version of your language, ('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 'Next' and continue by giving your solution a fitting name like, My first solution
   .
5. Finally, click on 'create' to create your first solution. 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. Click on the 'Info' button located at the ribbon bar.
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 'Save'.

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.

When assets have the same ID in the original and imported solution, most asset types* will be overwritten in the original solution by the value from the imported solution. This applies to the following assets:

• Global listeners
• Global scripts
• Global variables
• Global contexts
• Integrations
• File resources
• Classes
• Flows
• Language objects
• Entities
• Metadata
• Emotion
• Confidence Threshold

*If the Order groups from both solutions have the same ID, they are merged, not overwritten.

If the assets have different IDs but the same name, they will be retained in most cases*. However, they may require attention after importing; for the following assets, the document from the imported solution is added to the list of already existing documents in the original solution, and "_1" is appended to the name of the document to make it unique within the solution:

• Global listeners
• Global scripts
• Global variables
• Global contexts
• Integrations
• File resources
• Classes
• Flows (note that these only need to be unique within a folder)
• Language objects
• Entities
• Order groups

*Metadata and Emotion will not be retained in this case; if Metadata or Emotions in both solutions have different IDs but the same name, they will be overwritten.

If both the name and ID for assets in each solution are different, the new asset from the imported solution are simply added to the original solution. For Order groups, these are added to the top of the Trigger ordering, and the default Order group will be the one from the imported solution.

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.