TVC 2021.4.0 Release Information

NSX search field supports conditional fields with which additional fields can be added to searchform based on the value selected on the dependent search field. For example, it might be desired to load part related attributes when type selected in Part and for the classification field, additional classification attributes needs to be loaded. However, conditional fields are loaded only after a search is performed. With this release, it is now possible to load conditional fields searchform without performing a search. This feature is applicable only for fields having conditional fields defined. This feature can be enabled by configuring the below setting in the search config.

Read the Search Configurations chapter for more configuration details. Also read Conditional Fields for more details on Conditional Fields.

When the search is performed against index based search engine like Exalead, search results are returned in terms of total hits and hits displayed on the page. Total hit count can now be seen on the top search result in Structure Browser. This can be useful for the user to get an idea of how many records search criteria match.

Following string resource key can be used to customize the message. The first argument is page count and the second argument is the total count. Please go through Locallization (i18n) to know about how a resource file can be configured.

NSX datefield now has a new datepicker which provides more features and better user experience.

The users can still use the old datepicker by configuring "useOldDatePicker" setting at column level.

For more details see here Date Picker

The New Search Experience (NSX) in TVC allows user to find objects of interest by configuring the search within a page. The NSX comes with side panel for search and the results are displayed in a flat table. The NSX supports search providers - Enovia, Exalead or other data source.

When the NSX form gets loaded, the fields can be pre-populated with default values.

However, it might be needed that these default values are not pre-selected but can be set with a single click. As an example, for a person field, the default value can be context user and the user may want to set it on click of an icon instead of prefilling it.

This can be achieved by using the below settings :

The icon and its tooltip are configurable. The tooltip also supports localization.

<Settings> <Setting name="populateDefaultValueIcon" value="hand point left outline" /> <Setting name="populateDefaultValueIconTooltip" value="tvc.tooltip.owner.default" /> </Settings>

When the user enters a large value in the search limit input box, it takes more time to get the result and the application becomes non-responsive. To handle this situation, we have introduced a configurable setting upperSearchLimitValue to set the upper search limit. In case if the user tries to input a larger number than the defined upperSearchLimitValue the search does not get initialized and system throws an error message.

Validations are in place for search limit to ensure that it is non-empty, non-negative, numeric value and between 1 and upperSearchLimitValue.

We are now adding feature which allows to load selective TVC and Helium Dashboards in TVC Widget. To avail the feature, you would need to use tvc.3ddashboard.classic.dashboard.directories and tvc.3ddashboard.helium.dashboard.directories properties in tvc.properties file. Value of these properties are comma separated directory names which are present in TVC Path of dashboard configuration.

E.g. there are some TVC Dashboard configurations present in WEB-INF/tvc/mcadoptimizer-ups/classic/dashboard/ directory. Resolved path or TVC Path for one of the configuration would be tvc:dashboard:mcadoptimizer-ups:classic/UPSContextProduct.xml. If we want to see dashboard configurations from this directory, we can choose a directory name or pattern which can be identified in the path. e.g. mcadoptimizer-ups or mcadoptimizer-ups:classic. The property accepts multiple directory names in comma separated fashion. So if there is another set of Dashboard configurations, another unique directory name can be identified and added to the property. Please see example as below.

Please note that we have two different properties for Classic Dashboard and Helium Dashboard. It is in order to differentiate two types of Dashboard configurations. If a directory name pattern happens to be common in Classic and Helium Dashboards path, the configuration will show up in configuration list of both Classic and Helium Dashboard widget type.

In case the properties are not configured, below values are considered by default.

If TVX, Launchpad and Hex are not installed on the system, you won’t be able to find any configuration for Classic Dashboard widget type until the property is configured correctly to show custom configurations.

Previously when user used to select a Config from preferences which required context object to load in TVC Widget like (AddAffectedItem, AddDocument, AddExisting, etc..) or in HETrueWidget like (PartPage, ProjectPage, etc..), once the widget was loaded user needed to drag and drop a context object to load. Once the widget was loaded, if user switches to new Config which requires context, the widget used to use the same context which was set in earlier case, even though user does not want to load the previous context.

For example, if user has selected AddDocument Config initially and initialized it with a Document object. Later the user switches to EBOMByType Config, the widget would still show previously selected Document object.

Now we have provided the ability to the user to retain the previously set context object to load in new Config or not. If user does not want to load the previous context object, user can uncheck the check box Persist Context Object in preferences and save the preferences. By default Persist Context Object is checked.

Previously user could configure tvcWidget to load Table(Structure), Table(Flat), Classic Dashboard etc. But user was not able to configure tvcWidget to load menuBasedTabPage configurations. Now a new widget type Tab Page is added. User can use this widget type to load existing menuBasedTabPage configurations into the 3DDashboard widget.

A new widget type Search Based Table is introduced to support search based table. A search based table has two components a left search panel and a search result table on right. With widget type Search user can select pageconfig and searchconfig to load the searchbasedtable.

More Apps support is added to context menu. Using More Apps command in context menu it would be possible to open an object in desired app available in compass.

More Apps functionality in OOTB Widget

More Apps functionality in TVC Widget.

More Apps command in context menu can be made available through inbuilt OpenWith menu.

As we know, the users can launch various Helium Configurations such as Helium Page, Helium Dashboard, Helium Table and Form Widgets etc. in TVC Widget. These Configurations support helium-files actions. These actions support file related operations.

It was not possible for users to use TVC File Manager in these configurations. In this release, we are now supporting these file actions through TVC File Manager as well. This feature is controlled by tvc.3ddashboard.settings.useNativeFileManager property in tvc.properties file. The default value is true. If the users do not intend to use TVC File Manager for Helium Configurations in TVC Widget, please set value of this property to false.

In the Structure Browser, there is a built-in search function. This function can be re-used in many different use cases.

The search function contains functionality to define search forms, render the search form, perform the query and display the search result. When launching the search functionality in the structure-browser, we usually use Search Configuration. Please go through Search Configuration to know more about Search Configuration in Structure Browser.

Namefield is one of the most important fields in Search Configuration which determines search result. It denotes the name pattern of the objects which user want to see in search result. This field has been case sensitive by default while searching for results. It is now possible to configure this field to be case insensitive by setting tvc.structurebrowser.search.namepattern.caseinsensitive to true in tvc.properties file. Please note that default value of this property is false.

TVC Category Top Panel can be enabled and used to show category tree menu instead of OOTB tree/category menu. On enabling TVC Category Top Panel, category menu is rendered using TVC tabs. It is also possible to show a different category top panel for the specific type. Earlier, forward and back buttons were available on TVC Category Top Panel only for content pages. Now forward and back buttons are also functional on TVC Category Top Panel in popup mode for Enovia versions 2019x or higher.

File Manager web extension is published on Microsoft Edge store. Earlier, Microsoft Edge was using extension from Google Chrome web store. This extension can also be side loaded into Microsoft Edge browser. Alternatively, TVC File Manager extension can be added by opening Microsoft Edge and navigating to the below URL:

https://microsoftedge.microsoft.com/addons/detail/technia-file-manager-inte/dekbfpbkniankbfephkhpdolhlpmbfog

As per the existing design, the file actions column shows actions that can be performed. So, for a locked file unlock action is shown and for unlocked file lock action is shown. However, this can be confusing to some users as they expect to see the state of the file.

Now it is possible to reverse icons on Action columns so that it shows the state of the file/object i.e. lock icon when a file is already locked and unlock icon when a file is already unlocked.

This can be done using below setting.

See this chapter for more information.