Skip to main content
inorigo® Platform
Released  

22.4.9

Highlights

  • Restore Previous Application History in Application Builder
  • Application Builder: Version Management
  • Preserve Column Width in Knowledge set Builder
  • View Office files in inorigo using a Web Browser extension

Application Builder Enhancements

Restore Previous Application History in Application Builder

We’ve added a new selection in the Edit menu in Application Builder. Users can now revert an application to a specific previous saved version.  
This feature provides greater flexibility in managing application versions. Note that only the latest saved version will appear in the workbench.

To revert an application open the Edit menu in application builder and select the menu option “Rollback application version”, and then select the desired version by clicking on the desired timestamp and the OK button.

Application Builder: Version Management


This feature simplifies replacing an application in production with a new copy. Users can through this functionality build a version 2 of an application, and then go into the original and replace its content with the version 2, thus keeping the ID and the URL of the application.

Example: A user has designed a new version of the “Resources” application named “Resources 2” and wants to replace the “Resources” application with the “Resources 2”.

The user opens the “Resources” application and selects the menu option “Replace application…”, and then selects the "Resources 2" application and the OK button.

Improved Filter Handling in Application Builder

When designing an application based on a knowledge set, filters are automatically added to some filter boxes derived from the knowledge set.
However, these added filters sometimes don’t match the filters set in the Knowledge Set Builder.

When building an application based off of a knowledge set, a filter is today added to some filter boxes that are pulled out from the knowledge set (p0). The added filter is often not equal to the filter set in knowledge set builder - for example if an or statement is built with multiple definitions in Knowledge set builder, the application adds only one of the definitions to the filter, which causes additional filtering on top of the knowledge set. This is confusing and makes defining filters in Knowledge set builder moot.

Solution: Application Builder does not add any filter to filter boxes that are pulled out from knowledge sets.


KnowledgeSet Builder Enhancements 

Preserve Column Width in Knowledge set Builder

In Knowledge Set Builder, a new menu item allows users to reset column widths in the result table. Initially, columns are sized to fit the heading. If the grid width permits, they expand evenly. Column widths are remembered even when you manually resize them. So, if you hide and then bring them back, they will regain their width. However, columns are not updated when running a query. In the past, they used to be updated, which caused them to lose their width and flicker. To address this, a menu item has been added in the result table menu in Knowledge set Builder. This menu allows users to reset the column widths. Throughout the session, all column widths are remembered. Additionally, the width memory feature also works for Aggregation tables in Applications. This improvement enhances the user experience when hiding and showing grouped columns via the box menu.

Data Type Mismatch Handling

An Automatic check has been added when a Knowledge Set is opened in Knowledge Set Builder, the check ensures that column types match underlying Data set/knowledge set.
If any issues are found a series of dialogs will be presented.

The check looks for columns where the source DS column can't be found (column removed automatically).
The check looks for columns where the source Knowledge Set column can't be found (column removed automatically).
The check looks for columns where the source attribute can't be found (only presented as warning).
The check looks for columns where the data type does not match the source (data type adjusted automatically).
The check looks for columns where "transient" does not match the source (column adjusted automatically).


Application Runtime

View Office files in inorigo using a Web Browser extension

A new feature is introduced to show Office files in an inorigo application if an Office extension is installed on the user's Web Browser.

Sample of Office documents and in the bottom right a sample if there is no office extention.

If the web browser lacks an Office extension a message will appear explaining why the file cannot be previewed.

In the examples above we have used the “Office Editing for Docs, Sheets & Slides” extension found on the

https://chromewebstore.google.com/free of charge. Note that there are other extensions available.


Other improvements

Statistics Services

We’ve introduced new services with enhanced statistics for server logging.

Maintenance and Performance Related Issues

As part of our commitment to best practices, we continue to address maintenance-related issues to ensure better performance and stability, by upgrading 3rd party components.


 

Bug Fixes

  • SMTP connector fails when a failover round-robin member is offline.
  • Unable to remove user credentials in connection editor.
  • Large error is displayed on the workbench when the session is lost.
  • Create instances from a definitions box.
  • Names are not consistent.
  • Knowledge Graph doesn't work.
  • Data Source limited SQL statement field.
  • Auth dll files get deleted by WAR plugin.
  • Connection Graph sort is no good.
  • Change to transient attribute not reflected in KS .
  • Knowledge Set Builder will include abstract attributes.
  • Service API - dependencies/edges.
  • Sometimes Workbench Recent cards or Index list does not display.
  • Knowledge and Connection Graph fails when attribute value contain quotes.
  • Filter box item context menu contains options that shouldn't be enabled.
  • mssql-jdbc_auth-12.6.1.x64 is created in tomcat root folder.
  • Select all appear twice in definition filter box menu.
  • Search for user in instance with more then1000 accounts is very slow.
  • Not possible to refer to hidden components with action expression functions.
  • Service API Runtime command enable cease to work.
  • Sys Mgmnt Third Party reporting multiple versions of same artefact.