Add Content
Teneo Studio provides the possibility to merge import one solution into another making it possible to easily add content (such as Flows, Language Objects, Variables, Global Scripts, etc.) from a previously exported solution to a new or simply different solution. Please note that different documents behave slightly different when performing this type of import in Teneo Studio; read more.
Teneo Studio only supports import of files in the .solution file format.
- Teneo Studio Desktop
- Teneo Studio Web
To add content to a solution follow the below steps:
- With the solution open, go to the backstage of Teneo Studio (Solution tab > Import/Export)
- Click Add Content
- Browse to the location of the solution file, select it and click Open
- Optionally, enter a comment and lastly, click Continue
The import of the solution file starts, click Run in background to keep working on other tasks meanwhile; Teneo Studio notifies the user when the import has finished.
In Teneo Studio Web it is possible to add content to an existing solution in two places: the Solutions list and the Solution dashboard, both options are outlined below:
Add Content from the Solutions list
- With Teneo Studio open on the Solutions list, hover over the solution to which content should be added
- In the left side of the view, click Add Content
- In the file browser, browse to the location of the .solution file, select it and click Open
- Back in Teneo Studio Web, optionally enter a comment and click Save
The solution import starts and the "Document saved successfully!" is displayed when finished.
Add Content from the Solution dashboard
- With the solution open on the Solution dashboard, in the top ribbon, click Info
- Select Add Content
- In the file browser, browse to the location of the .solution file, select it and click Open
- Back in Teneo Studio Web, optionally enter a comment and click Save
Alternatively, simply drag and drop a solution file onto the Solution dashboard to initiate the process to add content.
The solution import starts and the "Document saved successfully!" is displayed when finished.
Document behavior
The below table captures the defined behavior for different types of documents when performing an Add Content / merge-import of one solution into another; the behavior is defined based on the Ids and names of documents in both the solution to import and the original solution. In the below table, the "imported solution" refers to the solution selected in the "Add content" window, while the "original solution" refers to the currently open solution into which the imported solution will be merged.
When an import has finished, users are encouraged to review and adjust the order of Global Scripts, Global Listeners and Order groups
| Document type | Different Ids, different names | Different Ids, same name | Same Id | Others |
|---|---|---|---|---|
| Solution Properties (name, language, location, quality control, confidence threshold, description, notes) | In any case, Solution Properties of the original solution persist (i.e., the values are not overwritten). | |||
| Global Listener, Global Script | The document from the imported solution is added at the end of the list of any already existing documents in the original solution. | The document from the imported solution is added to the list of already existing documents in the original solution, "_1" is appended to the name of the document to make it unique within the solution | Values are overwritten in the original solution by values from the imported solution | Global Listeners/Scripts from the imported solution are added at the end of the Listener/Script ordering, below any existing documents. |
| Global Variable, Global Context, Integration, File Recourse, Class *, Flow, Language Object, Entity | The imported document is added to the list of documents in the original solution | The imported document is added to the list of documents in the original solution, "_1" is appended to the name of the imported document to make it unique within the solution. (Flow names only have to be unique within the same folder) | Values are overwritten in the original solution by values from the imported solution | |
| Order group | The imported order group(s) are added to the top of the Trigger ordering | The imported order group is added to the list of order groups in the solution, "_1" is appended to the name of the imported group to make it unique within the solution | Order groups are merged when they share the Id in both the original and the imported solutions | All Order groups from the imported solution are added to the top of the Trigger Ordering. The default Order group will be the one from the imported solution |
| Metadata, Emotion | The imported document is added to the list of documents in the original solution | Values are overwritten in the original solution by values from the imported solution | Values are overwritten in the original solution by values from the imported solution |
* Note that the assigned Intent Classifier model is not exported and therefore imported solutions always use Learn.