News | Teneo Developers

Teneo 6 highlights

April 9th at 3:19pm

This release comes full of powerful changes that will differentiate Teneo further in the areas of team collaboration, solution maintainability, development productivity and enterprise strength.

The changes in this update will help project managers, developers, and other team members, know exactly what changes have been made, by whom, and when they took place, allowing for the restoration to previous versions if needed.

Here are some highlights of what this release brings:

Through the introduction of Match Requirements (that define the technology-specific requirements for when a trigger/transition matches) and Data Actions (that define atomic actions to take after the match has occurred), Teneo can now achieve fully-hybrid input matching and processing by combining these directly in the UI.

This is a step forward towards a more visual and choice-based development approach and is a feature that reduces the cognitive workload by removing concepts that are hard to explain. Even more important, it ensures greater efficiency and productivity of the solution development process.

It also makes it easier to develop, maintain, and enhance hybrid matching, allowing for swapping, enhancing, and changing match requirements and tech choices without affecting the flow design.

Teneo 6.0 brings users closer to a more guided approach, where the system suggests the next steps to follow, without limiting savvy users to follow their own path. Processes such as ‘building a flow’ have been revisited to support better task/responsibility separation and to allow flow sketching directly in Studio, without requiring a technical implementation.

These have been achieved due to the introduction of “TODO” prompts - these remind the user about what remains to get done for the flow to work. This allows the developer to create a flow skeleton as part of a separate scoping exercise without risking changing the functionality of the running solution. If a trigger is still TODO, it will not affect the rest of the solution.

Further changes alongside this work have given classes a dedicated area for management - separate from triggers - as well as the possibility to run cross-validation to determine the performance of classes within a solution.

Version support has been extended now to include every document within the solution - including Scripts, Integrations, Listeners, etc. - and an overall “ Solution Log ” has been included showing every change to every document within a given solution.

A Recycle Bin has been added to allow the retrieval of deleted documents. Combined with performance improvements, this allowed us to remove the 10-version limit on individual documents ensuring that edits can be safely made with the full support of the platform and knowing that there is the option to roll back if something goes wrong.

To aid debugging a solution, Try Out 1 has been given a new slimmed-down view in the main solution with an Advanced view, showing more detail and visual processing path for simpler and deeper debugging.

All code editors (TLML, TQL and Groovy) have been improved with better syntax support and some editing improvements around tabbing. Text fields have been improved with a spell checker that is aware of the language of the solution being edited.

Our Localization feature has been reworked to allow more control over which documents are included in branching from a master solution. This allows a fully working, testable, publishable Master solution and requires much less upfront thought required when using branching. Any solution can be branched, with no restrictions on how the Master solution is built. Dialogue Resources have also been rebuilt with this feature in mind to allow local solutions to be created from TDRs.

Date & Time support is now native to the Input Processing chain in the platform for Chinese, Danish, Dutch, English, French, German, Italian, Japanese, Norwegian, Portuguese, Spanish, and Swedish - with changes to the IPs and supporting objects in the lexical resources.

We have added 48 new languages , bringing the total supported language count of Teneo to 86. This ensures that Teneo remains ahead of the game in real-world language coverage.

With regards to Documentation , we have reworked and restructured it, so it is readily available and centralized on your own Teneo environment and Teneo Developers.

Authentication has been extended to support an external Identity Provider (IdP) via the industry-standard SAML 2 protocol, allowing clients to manage authentication via an external system whilst configuring the permissions authenticated users still within Teneo Manager. This lets Teneo support any kind of required authentication required (multi-factor, biometrics, single sign-on, password expiries.)

Lastly, major changes have been made in the Tech Stack for this release with a shift to Java 11 (to better support containerization - as well as gain from the other improvements over Java 8). Upgrades to the scripting language in solutions will now use Groovy 3 and all packages are now released as Red Hat as well as the previous Debian flavor.

Teneo 6.0 is available for new users that sign-up through Teneo Developers and for existing users upon request for an upgrade.

For more details, you can see our full list of detailed changes in the documentation

1 post - 1 participant

NEW FEATURES

JAVASCRIPT API

IMPROVEMENTS AND FIXES