Feature Details

Enhancement in URL pattern mechanism for execution of specific functions in OMN web client

For the following Editors/Function OMN supports now to work with ID AND Plugin configuration name (in later versions this will be Extended for other functions)

Example:

Current URL patterns looks like (using ID):

httрs://obj-storage.d.omn5.com/omn/home/AssetView/16437?objectId=37490&objectName=0002%20-%20Kopie%20-%20Kopie.jpg&objectPath=%2Fimages%2F0002%20-%20Kopie%20-%20Kopie.jpg&objectRncId=15091&title=ewAiAGwAbwBjAGEAdABpAG8AbgAiADoAIgBBAHMAcwBlAHQAVgBpAGUAdwAiACwAIgBpAHQAZQBtAE4AYQBtAGUAIgA6ACIAMAAwADAAMgAgAC0AIABLAG8AcABpAGUAIAAtACAASwBvAHAAaQBlAC4AagBwAGcAIgB9AA%253D%253D&editMode=true

New URL pattern (using configuration identifier):

httрs://obj-storage.d.omn5.com/omn/home/AssetView/F.AssetView.ACC?objectId=37490…​

Improved localization in info box when checking-in an asset

The "fkMetaTagGuid" which is an alias for TID of an assets is now configurable

Improvement, that project links will be maintained when linked asset is moved on the DAM filesystem

Possibility to view the annotations of an asset in Single Object View directly (also for new introduce types), so that the user knows if work on the asset is done

Possibility to see reference type name and full asset name in SingleObject filmstrip (in context of PIM2) at a glance so that the user can easily get useful details about images related to a product

LightTable supports now localization for Attribute object type

Optimization in localization in ShoppingCart module

Improvement for localization of keyword Editing function on FSNavigation

Improvement for localization of turn version into variation function

Invalid PIM asset links are shown at the end of the list in 'Linked assets and PIM items' accordion on Management page

Small change that invalid PIM asset links (links to objects which are no longer exists) are shown in the end of the list

PIM ClassificationView Localization Assetview

Asset related View in PIM2 classification client can now be localized via Config Client

Possibility to change values of the ancestor product directly in the FSDetail

Possibility to add new values to date attributes is configured in FS Detail for Type PIM2

Possibility to add new values to a number and date attributes of PIM2 in FSDetail if Option is configured

Improvement for validation when add new real Attribute value

Improvement by new validation for a entered date value in case that creating new values is allowed and entered value is wrong, so that the admin knows that the Input has to be adjusted

Function "Unlink entity from product" is now using a new Icon

Function "Unlink entity from product" is now localisable*

Adjustments in Create PEO function to build PEO names on base of configurated name patterns for items which are created together with selected product when assigning them to projects

Support for using Special characters for certain attribute types on Channel Object Entity

Support on following types:

Usage of Special characters on following types is not allowed and supported:

Possibility to open the shown content on the Flatplan tile within the annotation tool independent from pattern configuration

Possibility to use/see/access the shown content on the Flatplan tile within in annotation Tools

Possibility to see the related nested row for new created PEO in ProjectProductView expanded automatically in hierarchy mode

Small Improvement in deletion modal so that the default name of PEOs fits in the modal window (the width of the modal equals 500 px)

Enhancement of userbased Settings for ProjectProduct Center view so that the last selected content view in the central Panel is stored in userbased Settings

Enhanced operators for filtering in string column in ProjectProductView, so that the user has more Options for filtering values

Former implementation only covered following Operators:

Performance improvement when to work faster with large data in ProjectProductView

New dirty check modal in case if the user applied a sorting on a specific quick filter level and did not persist it via save function, so user can decide if the applied order of items should be persisted or not, when switch to another quick filter Level

Possibility to mark an annotation as resolved, so that the user don’t need to see them anymore and so that the user can filter for only open TODos

Possibility to manage and edit custom annotation Attributes from different types for different Annotation types so that the user can manage additional information for annotations like putting Weblink to a rectangle

Possibility to see on comment view (right view) what type of annotation is shown in the list by a specific icon representing its annotation type

Possibility to see labels of annotation attributes in both themes (dark / light mode)

Display of Annotation type as Icon in Annotation Widget

Possibility to see created annotations from type text editing in every place where annotation info is available, so that the user is aware of all made Annotations (AnnotationRepository, ProjectAnnotationView, Annotationwidget)

Possibility to see the new resolved state in the PDF Annotation Export in order to see which annotations are done and which are not

Possibility to download PDF containing a preview with PDF-compliant Annotations for new Annotation type text pointer so that the user have a clear representation of made annotations and can manage them in PDF too

Annotation colors will be supported in the annotation PDF export to have the same colors in PDF-Export as specified in the annotation tool

Different Annotation Tool colors (personal colors) in PDF-Document

New information About resolved state in Annotation Repository, so that the user can see and filter for annotations that are resolved, in work or open

New extra column for resolved state inside the Annotation widget, so that the user can see and filter for annotations that are resolved, in work or open

Improvement with new Tooltip to be informed about previously prepared translations for terms and sentences so that available matches can be reused and ease translation process

Introduction of a new column for glossary name in the glossary table in MDT and Terminology plugin, so that the user knows from which glossary the translation term is

Possibility to see a column for type like terms and sentences, so that the user understands, which entry belongs to what

Possibility to have additional, configurable glossary overview in the Terminology Plugin, so that the user can view and manage glossary related information and execute camunda workflow functions on glossaries

New Content switcher in Terminology plugin, so that the user can switch between Terminology and Glossary overview (which is based on FSTable configuration possibilities)

Possibility to execute functions on selected glossary items from Terminology Glossary Overview, so that the user can delete, edit or create glossaries or execute workflow functions (Camunda Workflow) on selected glossaries like export to an external service or system like DeepL Glossary

Possibility to export the table data from Terminology, so that the user can reuse the translated terms/expressions' base in further work

Possibility to start a configured Camunda Workflow on a Glossary item as configured in OMN Terminology Plugin

Introduction of new object type glossary with the possibility to configure glossary specific workflow-related attributes and the possibility to execute Camunda Workflows on glossary items on base of WorkflowConfig function Plugin

Change that preview of a DAM asset is shown on its related workflow for expression preview

Possibility to see a configured custom icon for workflow transitions so that the meaning of transition execution is clearer to the user

Possibility to set an optional translation Parameter for the Translation language, independent of the target language of the attribute to be translated e.g., English, which specific language is used for the translation by AI-Translate e.g. Use British English

Possibility to translate text with DeepL AI Translation Workflow and usage of a glossary for DeepL translations for better term translation

New Camunda workflow-based Glossary Export to DeepL for exporting Terms of a selected OMN Glossary (created in OMN Terminology Plugin) to DeepL Glossary

New Camunda workflow-based Glossary Workflow for deleting an already exported OMN Glossary (created in OMN Terminology Plugin) from DeepL Glossary repository

AI Tagging allows now to send a low Quality preview to Google Custom Vision Service

Saved Elastic Searches are now supported with Web2Print Preparing and Docedit module

27]

Stored Searches in Preparing Images boxes are sorted alphabetically to find stored searches more easier

Improvement that prevents usage of 'Image' tab from being used until the request is processed in Preparing module

New Information when a text in CKEditor is displayed in a different font because the original font is not installed on the System

Web2Print CK Editor now supports to work with bullet Points

DocEdit shows Textbox Content (with latest changes) for master box done in Preparing on the canvas of DocEdit when Opening

New tree component for Navigation in new ConfigClient Area to provide intuitive and good organized navigation in the left panel of the ConfigClient

Possibility to navigate into the main structure elements in new config Client by new sidebar items

Introduction of searchable Dropdowns for value selection in new HTML5 Configclient

Improvement of Breadcrumb component to show icon in the path’s segments and additional functions (for information and help) in the right part

Possibility to configure toolbar functions for a specific Plugin

Possibility to jump to the documentation in the correct version and language directly from Configclient

Possibility to manage basic settings for an OMN mandator in the new HTML5 Configclient, so that the common settings are set for all pages of the frontend client (e.g. dates Display)

Introduce new server-side method to find reference configuration by mandator identifier

Configuration for Login specific settings in new HTML5 Configclient, so that the configurator can influence the registration process and license agreement and add the use of terms on the login screen

Possibility to configure GDPR page in the new Configuration Section, so that UI users are aware of the Agreements

Possibility to configure the Terms of Use on the Login Screen, so the Administrator can add license Agreement

Possibility for configuration of languages used in application, so that the configurator can define what languages are available in the frontend Client

Possibility to create a new plugin instance, so that the user can add my configurations

Possibility to create a new plugin instance, so the administrator can add another version of a plugin to the UI and add certain configuration(s) in it

Possibility to delete one or several plugin instances of a certain plugin

List of plugins is sorted now in deletion plugin dialog

Possibility to create attributes from different types, so that the can use them in different contexts in my OMN System

Possibility to have created attributes selected and in the viewport after creation, so creation is obvious, and the user can do further actions with Attributes

Possibility to configure attributes from the type glossary so that those attributes can be used in the context of the terminology plugin (especially for glossary overview)

Possibility to create a new attribute from type glossary, so that the user can use it in table for glossary overview for example

Possibility to edit attributes from the type glossary so that the user can use those changed attributes in the context of the terminology plugin (especially for glossary overview)

Possibility to delete an attribute from type glossary in new HTML5 Config Client

Possibility to localize content Plugin names for the Terminology table (View) so that the admin can adapt them in the corresponding name

Possibility to see icons for each attribute type in navigation bar of create attribute modal, so that the user have the same visual indicators as in table behind the modal

Possibility to have localization for Annotation custom Attributes so that these attributes can be displayed on any language

Possibility to configure attributes from the type annotations, so the administrator can use those attributes in the context of the Annotation tool

Possibility to create a new attribute from type annotation, so that it can be used as a custom attribute in the annotation tool

Possibility to edit attributes from the type of annotation so that the user can use those changed attributes in the context of the AnnotationTool

Possibility to delete an attribute from type annotation

The reference management configuration introduce with OMN version 5.10 is now available at a new place in config Client under Data/Datasettings/Referencemanagement

Functionality to enable and configure terminology plugin in the Config UI, so that the Administrator add additional views and functions to Terminology Plugin

Introduction of a new own object type glossary as a new entity in Online Media Net to set up data, views, and functions with it

Improvement by new Validation for Default name when the name is too long

]

Possibility to define default name and column in content view configuration of terminology plugin, so that the admin can see those in the UI

Possibility to configure specific import and export parameters for terminology plugin, so the admin can decide for example Format

Possibility to assign an FSTable for terminology plugin to display certain information and functions about a glossary like a overview of all glossaries available in OMN

Server Extension to extend the Terminology Plugin by additional Content Views with its own configured functions

Possibility to manage so called glossary custom attributes for new OMN Entity glossary

Possibility to have localization for attributes in Terminology, so that these attributes can be displayed on any language

Improvement of dropdown usage in new HTML5 Config Client by having ability to resize and search

Possibility to select existing configured views (like tables or detail views) for the terminology page plugin in view configuration table, so that this views can be used in a Plugin configuration

Possibility to remove a view from view configuration table in terminology plugin, so the view is not shown in the UI anymore

Possibility to add a new view in the view configuration of terminology plugin, so this view will be shown in the UI*

Possibility to assign / create an FSTable for terminology plugin to display certain information in a table

New API method is introduced to avoid that Glossary update attribute clears all existing attributes values

API endpoint to upload Asset via API by chunks

New API endpoint to upload version by chunks

Currently chunks are written to storage and assembled to target file when upload is finished

By new improvement chunks can be appended directly

New API endpoint to move an existing OMN Keyword to an other Keyword via API

New API endpoint to move an existing OMN Asset to an another RNC or Directory via API

New API endpoint to copy an existing OMN Directory to an other RNC or Directory via API

New API endpoint to copy an existing OMN Asset to an another RNC or Directory via API

New API endpoint to move an existing OMN Directory to another Directory via API

New API endpoint to unlock an asset if this one is locked by another user via checkout process

New API endpoint to access the Asset History (changes from the History function)

API endpoint Retrieve Asset Versions returns now creation and lastUsage date

Each creatd Plugin instance with new config client contains additional fields

Change in RestAPI Retrieve Asset Versions to return creation and lastUsage date

New API endpoint to set/update custom attributes in OMN Glossary

New API endpoint to retrieve the existing OMN Glossary structure and ist related elements (Terms and Sentences)

New ConfigClient API following for:

New Config API endpoint to fetch and save information about configured content views and related functions for a plugin configuration

New Config REST API endpoint to manage attributes for glossary (CRUD operations)

Get an information about configured content views for Terminology UI plugin

Extension of ConfigAPI for Management of mandator Settings by the following params:

The following ConfigAPI endpoints now support to work with localized values

Create new attribute

Get attribute

Delete attribute

Update attribute

Get all attributes

Config API endpoints to manage attributes for Annotation by CRUD operations

New config API endpoint get list of available languages for mandator

Possibility to view, create edit and remove glossary functions in function pool only once per instance, because they are not related to plugin instance of terminology Plugin

Ability to delete multiple plugin instances via Config API*

ConfigClient API extension to get full information about a plugin instance

Loading improvement in order to open mandator settings page without long waiting times