Teneo Developers

Teneo Studio

Version Flag

Teneo 6.1 brings Version Flags to the world of Teneo, this feature allows users to set a specific version of a document (Language Object, Flow, Entity, Global item, etc.) to stable, but keep developing the same document (i.e. creating newer versions) and if needed, publish the stable document together with all other stable documents without worrying about the latest improvement performed.

Auto-test and Try Out have undergone changes - as well as the Publish area of a solution - to allow for testing and publishing either the stable solution containing all the documents flagged as stable, or to test and publish the latest version of a solution with all improvements performed after marking a specific version of the documents as stable.

This feature supports parallel long and short running development of solutions, being able to select specific versions of the documents as stable and use those when publishing the solution while working on new implementations which might not yet be ready to go live. The feature also allows for developers to fix bugs in stable versions of a document and re-publish the stable solution without worrying about any other - newer - implementations in other parts of the solution.

Set Stable version

With the new Version Flag feature, it is now possible to set a specific version of a document as stable. A document can have just one stable version at the time or not have it.
There are several ways to set a document version as stable (same applies to unset):

  • From the Solution Explorer, it is possible to select one or more documents and then click on the Set button Set stable
  • From the History of a document when selecting a revision Set stable history
  • In the top ribbon of an object, when opening in Read-only mode and Edit mode (only if no changes are done) Set stable read and edit mode

It is also possible from the Solution Log to set an entire revision as stable or unset all.

Setting an entire revision in the Solution Log as stable means that the version existing at that revision of all documents are going to be set as stable. Clicking on the Unset all button means that no stable version of any documents exist (it is not necessary to select a specific revision to unset all).

Set stable solution log

Stable version icon

A document with a stable version is displayed with one of the two following icons:

Stable version icons

The yellow icon indicates that the stable version is the latest version of the document, while the grey icon indicates that the stable version is a former version of the document (i.e. changes have been saved after setting the stable version).

No icon displayed means that the document does not yet have a stable version.

Edit stable version of a document

To edit a stable version of a document, if the stable version is the latest version of the document is done by simply editing the document in its current version; but when the stable version is a former version of the document this version of the document first needs to be restored and then changes can be applied and saved.

Deletion and Recycle Bin

Deleting a document with a stable version will not remove it automatically from the stable solution - thus deletes that are part of ongoing maintenance will not accidentally affect the stable version of the solution; In order to remove the document from the stable version of the solution, it needs to have its stable state manually unset in the Recycle Bin / Document History or a later Revision of the solution be set to stable.

Required Stable documents

To consider a solution stable and be able to test it in Auto-Test and Try Out or Publish a stable version, the below documents mandatorily require having a stable version:

  • Solution Properties
  • Intent Trigger Ordering
  • Prompt Trigger Ordering
  • Global Listener Ordering
  • Solution Libraries

If one or more of the above documents are missing a stable version, then a solution cannot be considered stable and cannot be used. Trying to test/publish a stable solution missing a stable version in any of the above documents will lead to error messages being displayed, e.g. in Try Out as in the below image captures.

When at least all the mandatory documents have a stable version, it is possible to use Auto-test, Try Out and Publish on a stable solution.


The Auto-test now allows to select which type of documents to test.


All Auto-tests of stable versions of the solution's documents are flagged with a "Tested using stable versions" text.

Auto-test stable version

Try Out

In both the simple and advanced Try Outs, it is possible to select which documents to use: Latest or Stable document versions.

TryoutWhen using the stable version and wanting to test performed changes, the Try Out is not reloaded automatically, but the user will need to do this manually.

When using the latest version of the documents, Try Out works as in former Teneo Studio versions.


When publishing a solution, it is possible to select which documents needs to be published: Latest or Stable.


Once the solution is published, the status includes if the live solution was published from a stable version or not. Publish Stable

Publishing a stable solution on top of a latest solution will always result in a full publish and vice versa.


Once a solution is published, in the logs it is possible to see if the generated sessions are related to a stable solution or not.

The session property solutionStatus contains the relevant information.


Read more in the User Guide

Other improvements and fixes

  • Lines are again wrapped in the condition editor to ensure clear visibility of conditions (of Condition Match Requirements, Listener Data Actions, Language Objects, Global and Flow Listeners, as well as Scripts).
  • An issue with an error message not being displayed on top in Teneo Studio after disconnecting a VPN connection while a results dialogue, i.e. a successful publish dialogue, was open, has been fixed to ensure the error message is correctly displayed in front of other open windows and dialogues.