Teneo Studio Web
Work on improving Teneo Studio Web is continued, and Teneo Studio Web 7.2 includes alignment of terminology (Studio Web/Desktop alignment) and improving the display of texts in, for example, documents' lists, tooltips and the Add Match dropdown menu in Flows. The tooltip in documents' lists now display the complete values for name and description fields when a value is too long to fit in the actual list.
Moreover, Studio Web 7.2 includes keyboard shortcuts for the modal views (e.g., the pop-up window when adding a new document) where Escape allows to close the modal (i.e., cancel the creation) and Enter confirms and creates the document; the button visible when creating new Variables and File Resources has been aligned with with the button available for other documents and is renamed from Save to Create.
Improvements are done for Script Ordering and Listener Ordering to remove logged errors in the browser console and also, in the lock message for Script Ordering and Listener Ordering, an issue with the Retry button has been fixed to ensure correct behavior when clicked.
On top of this, the following features are now available in Teneo Studio Web:
- Solution Import/Export
- Add Content (to existing solution)
Furthermore, the following Flow usability improvements are included in the 7.2 release :
- TLML and Script editors in Flow nodes are now expandable
- Collapse/Expand functionality available for the Flow overview, Flow Variables and Flow Listeners.
All of these are described further in the following sub-sections.
Import, export and Add content
Developers can now import and export solutions directly in Teneo Studio Web including adding (more) content to an existing solution. The Import/Export and Add Content buttons are accessible in the following places:
- Solution list: Export Solution and Add Content are available in the right-side of the solution on hover over
- The Create button to create a new solution now contains two options: one to Import Solution and one to Create New Solution. The Import Solution option creates a new solution with the imported solution
- Solution dashboard: the top ribbon now includes an Info button which allows to edit the solution name and description as well as the options to Export Solution and Add Content; when updating a solution's name, the Save button becomes available in the top ribbon after closing the Edit document info box.
In the Solutions list, while an import is in progress, the solution is listed at the top of the list; when the import is finished the solution is again moved to where it belongs in the list (depending on any filters applied, but by default alphabetically sorted).
When adding content from the Solution dashboard, the import is done after pressing Save and while the content is added a spinner is displayed where the Save button was. Once finished, the Document saved successfully! message is displayed and the developer can keep working in the solution.
Note that Export is only visible for users with export permissions.
Drag and drop
On top of the above, developers can also:
- Drag and drop a .solution file onto the Solution list to start the creation of a new solution with the selected file
- Drag and drop a .solution file onto the Solution dashboard to add content to the solution.
Developers can with Teneo 7.2 work on a solution's intent classifier directly in Teneo Studio Web. Access is provided via the Classes tile on the Solution dashboard, and - as for other document types - the tile provides activity information for the past four weeks as well as links to the last modified and the last created classes. The list of classes is accessed by clicking the right-pointing arrow and new classes can be added with the create button (+).
The Classes' list provides an overview of the classes in the solution and the developer can filter on the list by using the text filter in the top ribbon or by clicking any of the headers of the list. Adding a new class is done by clicking the Create button in the lower, left corner of the view.
Opening a class is as simple as clicking it, and once opened, the developer can add training data either by clicking Add Training Data at the top of the window or at the bottom (below any existing training data examples).
The training data can be searched by letters/text in the Search Training Data field, and when changes are performed, the Save button becomes available in the top ribbon.
The developer will also find the new Info button in the top ribbon allowing to rename the class or provide a description; also see Info and About buttons.
Collapse Flow Overview, Variables and Listeners
The Flow Overview, Flow Variables and Flow Listeners have been reworked and are now independent of each other which allows to collapse / expand any of the three as needed while working in the Flow; the work includes an update of the displayed icons for Flow Variables and Flow Listeners to align them with the icons used for the Global Variables and Global Listeners.
Finally, the icons in the Flow graph referencing to other document types (i.e. variables or listeners, as visualized in the above image) are aligned with the document icons displayed on the Solution dashboard.
Expandable code editors
Enhancements are performed to the handling of active nodes in the Flow to ensure better usability, and the developer can now expand the code editors in Flow nodes (TLML Syntax and Scripts) as well as the ones in Flow Variables and Listeners by simply clicking on the expand icon in the bottom, right side of the editor providing developers with a better overview of existing code pieces as well as a bigger workspace for creating and maintaining scripts and TLML syntaxes.
On the Flow graph, when zooming out the names of the nodes are now displayed in order to facilitate the recognition of the different elements in the Flow; if no node name is provided by the developer the type of Flow node is printed in the view, for example, "Match requirements" and "After Match" as seen in the below image.
Zooming in and out on the Flow graph is now available in Safari.
A few improvements are included in Teneo 7.2 to provide better support to multiple users on the same solution, including the solution name automatically being updated in all open views for all users when one user has updated the solution name. And, when looking at a document in read-only mode, the user is now prompt when changes are performed by another user and encouraged to either reload the view to include the latest updates or to cancel and leave the read-only view of the now outdated document.
Finally - to align the behavior with Teneo Studio Desktop - error handling is implemented for situations where one user tries to delete a solution which is currently in use by another user in order to avoid deleting solutions in use.
Info and About buttons
On the Solution dashboard and with any document open, a new Info button is available in the top ribbon allowing developers to either view the name and description of the solution/document or to update either of these properties with new relevant details.
Note that a document’s name can still be edited inline in the top ribbon and that improvements are performed to ensure that users do not leave the name of a document empty (i.e., if the user clicks otherwhere the previous value will return) and any suffix, e.g., .ENTITY, is automatically added when the user stops writing.
An About button has been implemented in Teneo Studio Web in the upper, right corner both before and after logging in to Teneo Studio, giving access to information related to the currently logged in user and the server version.
Teneo Studio Desktop
Log Data Source
A big focus point for the Teneo 7.2 release has been on expanding the Log Data Source in Teneo Studio with the data management functionalities previously available in the Log Data Manager. The functionalities new to Teneo Studio cover:
- Overview (of Sessions)
- Saved Results
Hereby, Teneo Studio includes even more functionalities at the tip of the fingers of the solution developers, allowing to easily synchronize log data or update augmenters without the need to open a different frontend. Note that the Import function has been moved to Teneo Manager.
The Log Data overview, available both before and after opening a solution and now also in the backstage of the Log Data Source window, is enhanced and besides the number of sessions for a particular Log Data Source now also includes the number of sessions available in the Log Archive and, if applicable errors when the two numbers (counts of sessions in the Log Data Source and in the Log Archive) do not match.
In the Log Data Source window, the graph is available in the backstage of the window in the Overview tab which also includes the Configuration of the Log Data Source.
Read more in the Log Data Source pages
The Synchronize tab provides the developer with the option to synchronize the Log Data Source with the associated Log Archive, cancel the process and Clear the Log Data Source.
Read more in the Log Data Source pages
The Augmenters tab provides an overview of existing adorners and aggregators (if any), and management options are available at the right-side of each of the listed augmenters. The Add buttons allows to create new adorners and aggregators and, last but not least, the Pending Actions box allows to apply updates and pending actions.
Adding or editing an adorner/aggregator opens a separate window, where the user can either view the details of an existing adorner/aggregator or add the details for a new adorner/aggregator; as in the old Log Data Manager frontend, the following fields are available:
- Name of the adorner/aggregator
- Solution Revision
- Date Range
- TQL command / Groovy script (depending if the adorner/aggregator is of type TQL or Groovy)
- Keys (generated on clicking Preview or Save for TQL adorners/aggregators; added manually for Groovy adorners/aggregators)
Read more in the Log Data Source pages
Validation checking Key has Type
Please note that when saving or previewing aggregators, a new validation has been introduced checking that the key has a type. This validation didn't exist on previous Teneo versions so it could happen that an aggregator key without type already exists on the LDS ; if that is the case and the user wants to edit the aggregator, the user needs to add the type to the key to be able to save it.
The Saved Results tab allows to view and manage any saved Log Data query results, and the available buttons provide options to View, Export (CSV and JSON formats), Upload and Delete the data.
Read more in the Log Data Source pages
Depending on the assigned access roles in Teneo Manager for a given Log Data Source and user, the Log Data Source window will display an "Access Denied" message in the backstage tabs for which permissions are not granted to the current user while buttons may be greyed out in the Home window and the user will not be able to access these functionalities (unless the user obtains the right access roles). Of course, if the user has other access roles assigned, the functionalities related to the assigned roles are still accessible.
Collapsible Flow Overview
The Flow Overview visible in previous Teneo versions in the upper, left area of the Flow editor has been moved into the left-side panel allowing developers to open it when needed or hide it while focused on work in other parts of the Flow window; this change brings a better visualization of the Flow graph, especially when containing many triggers and nodes as it allows for more space to display the graph.
The experienced Teneo user will notice that the dialogue when deleting documents in Teneo Studio Desktop has changed a little and now includes a check box to select Do not check usage for cases where the user wants to delete documents without checking first if the document(s) is referenced somewhere in the solution.
The rest of the dialogue continues as previously when deleting with usage check, letting the user select which documents to delete even when they are in use in the solution.
Other fixes and improvements included in Teneo 7.2 covers:
- The Search button is no longer visible for Metadata with Session and Transaction scope since they are not linked to any searchable properties in Studio, i.e., search results of these were always empty in previous Teneo versions.
- All Studio windows (others than the main window) now maintain their correct naming after, for example, a solution renaming action.
- To ensure stability of Teneo Studio, the option to minimize secondary modal windows, such as a Flow Listeners (in the backstage of a Flow), has been removed.
- In Localization setups, in a local solution when performing a search selecting All solutions, it is again possible to open and view Flows from other solutions.
- Updates related to nested folders are performed to the exported solution XML file.
- The keyboard shortcut Ctrl+r (allows to restore previous version of a document when viewed) is reviewed to ensure correct behavior.
- Input Parameters, in Tryout, are reviewed to ensure correct handling of these based on casing (upper/lower case) and to not allow duplicated parameter names; for example, Tryout will accept PARAM1, param1 and PAraM1 as different parameter names since the casing is different while PARAM2 and PARAM2 will raise a warning as the name is duplicated (i.e. identical in wording and case). Also note that parameter names are always required and the field cannot be left empty.