Release 33
- 1 Description
- 2 ✨ New Features
- 2.1 🚨 [Custom Workspace] Replace "Default Action" for collections with "Default Analysis"
- 2.2 🚨 [Custom Workspace] Rename "Automation Manager" to "Workspace Manager"
- 2.3 🚨 [Custom Workspace] Move Annotation Actions to Toolbar
- 2.4 [Custom Workspace] Allow to use original transaction id to download export artifacts
- 2.5 [Custom Workspace] Page Segmentation Boxes are trainable
- 2.6 [Custom Workspace] Move Chosen Category to Categorization Node
- 2.7 [Custom Workspace] Make Analysis panel Collapsible
- 2.8 [Custom Workspace] Page Segmentation Step has Annotation Actions
- 3 🛠 Technical Improvements
- 3.1 [Custom Workspace] The Categorization Test is not failing anymore
- 3.2 [Custom Workspace] Category evaluation used to fail due to insufficient training samples.
- 3.3 [Custom Workspace] Table Step + Step Effects leads to unexpected behavior when the Form Recognizer is used
- 3.4 [Custom Workspace] Actions were not triggering the elements view refresh
- 3.5 [Custom Workspace] Generate Annotations from Document was not working if the global model was other than trainable
- 3.6 [Custom Workspace] Changing Analysis Version only changed the Analysis content after Refresh
Description
Current release 33
🎉 Welcome to Acodis Platform 33! 🎉
Our latest release introduces powerful new features and improvements that bring greater control and efficiency to your workflows as well as an all together better experience. Let’s dive into what’s new and exciting in Version 33!
✨ New Features
With version 33 of the Acodis Platform our journey to improve users' experience continues. We fixed bugs and added small features aimed at making life easier when working with our product, features that were developed based on our users' feedback.
🚨 [Custom Workspace] Replace "Default Action" for collections with "Default Analysis"
From version 33 on, the “Default Action” has been changed to “Default Analysis”. The goal was to replace the generic “Default Action” for collections with the (pretty much exclusively used) “Default Analysis” concept, which allows to configure the behavior more in line with the actual use. In addition to replacing the “Default Action” concept with a “Default Analysis”, the users also have the ability to specify which version of a specific analysis they want used by default, as well as the ability to configure the collection to automatically run that analysis upon import of new documents.
🚨 [Custom Workspace] Rename "Automation Manager" to "Workspace Manager"
The “Automation Manager” is now a “Workspace Manager”. The change in name was done to better reflect the area of influence this role has. Apart from the name, nothing else has been changed in regards to this role.
🚨 [Custom Workspace] Move Annotation Actions to Toolbar
This change brings all annotation actions under a single menu to improve the ease of use. Therefore, from version 33 onwards:
all actions are in the dropdown of the actions button,
To the left of the user icon, there is a status flag showing checked if all pages for the selected step are verified (Page Classification and Noise Page step already have that),
The status flag will show a status when hovered: “All pages are verified” or “Not all pages are verified”
All right-click options from the selected step as per table below are available in addition at the end of the dropdown:
Selected Steps | Right-click option to be removed | Name of the option in the Annotation dropdown in the toolbar if the step is selected |
---|---|---|
Noise |
|
|
Enumerations |
|
|
Table |
|
|
Figure, Caption, Structure |
|
|
OCR |
|
|
Page Segmentation |
|
|
[Custom Workspace] Allow to use original transaction id to download export artifacts
With the introduction of branching in the workflows, a new behavior was introduced in the API calls that made downloading export artifacts more confusing. We addressed this issue in this release and we are happy to let you know that you can download the export artifacts as you would expect, by calling the API endpoint with the original transaction id.
[Custom Workspace] Page Segmentation Boxes are trainable
As of version 33 the model backing the step can be trained and evaluated like any other of the models. By correcting and verifying the page segmentation annotations, like you do with any other trainable step, you are helping the new model that you will create to be even better than before, adapting it to your needs.
[Custom Workspace] Move Chosen Category to Categorization Node
To improve experience on small screens we moved the chosen category into its own node. From now on you will see the result of the categorization process in a Categorization Node. This is also the place where you can review the predicted category and approve it or change it if needed.
[Custom Workspace] Make Analysis panel Collapsible
To further improve experience on small screens we made the analysis panel collapsible. This way you will get more real-estate to display the document you are working on, making it easier to spot potential issues or handle annotations.
[Custom Workspace] Page Segmentation Step has Annotation Actions
To clean up potential text-building issues inside the remaining text element after having split parts of it as an “effect” (=action) of an “Element” step, users are now able to configure text effects for the remainder - analogous to the text effects that can be applied to the newly formed element.
The Text-Effects UI is extended as follows:
🛠 Technical Improvements
[Custom Workspace] The Categorization Test is not failing anymore
In the previous version if you would create a categorization resource, create a model, go to the testing screen and upload a document, the predicted category would not show up.
This behavior is now fixed and the categorization test works as expected.
[Custom Workspace] Category evaluation used to fail due to insufficient training samples.
There were cases where the evaluation of a model would fail. The latest case we detected and fixed is the case where there is insufficient data in the training set. With version 33 the evaluation knows how to handle this case as well.
[Custom Workspace] Table Step + Step Effects leads to unexpected behavior when the Form Recognizer is used
When the Form Recognizer is used to OCR a document, the Table step produces improperly aggregated text when step effects are applied. This behavior has been fixed with this release.
[Custom Workspace] Actions were not triggering the elements view refresh
Prior to this release some of the actions executed on some steps would be applied but the view would not refresh to show the result, thus leaving the user under the impression the action was not triggered.
This behavior is now fixed and users can enjoy a better experience.
[Custom Workspace] Generate Annotations from Document was not working if the global model was other than trainable
If you used the values of “None” or “Pretrained” for the Shared Model of some steps you might have noticed that running “Generate annotations from document“ was not generating any annotations.
This issue was fixed and you can now reliably generate the annotations.
[Custom Workspace] Changing Analysis Version only changed the Analysis content after Refresh
If you were working with an analysis that had more than one version, changing the version from the drop-down menu would not lead to the display of the analysis' steps until the page was manually refreshed.
With version 33 the issue has been fixed, and the proper steps are displayed when changing the analysis version without needing to refresh the page.