TVC 2022.2.0 Release Information

1. 3DDASHBOARD

1.1. TVC Collaboration Widgets

Collaboration can be configured as True Widgets through the widget preferences in the administrator’s dashboard. The True Widgets follows the 3DDASHBOARD development concepts and runs directly inside the 3DDASHBOARD widget iframe.

The following widget URLs can be used to configure myspace and panel as a widget in 3DDASHBOARD.

Myspace : <server-url>/webapps/tvc/collaboration/tvcCollaborationMyspaceWidget.html

Figure 1. TVC Collaboration Myspace in 3DDASHBOARD.

Panel : <server-url>/webapps/tvc/collaboration/tvcCollaborationPanelWidget.html

Figure 2. TVC Collaboration Panel in 3DDASHBOARD.

1.2. Including custom resources in HETrueWidget/TVCWidget.

Previously when the user wanted to add any custom resources (JS and CSS) files in HETrueWidget/TVCWidget, the user has to modify the source HTML file of the existing widget. This forces user to create a new widget using the updated source HTML file or need to drag-drop the same widget to fetch/cache the newly added custom resources and do all the configuration once again.

To avoid such scenarios this new feature gives the ability to include custom resources (JS and CSS) files in HETrueWidget/TVCWidget without updating the source HTML file of the existing widget.

The custom folder needs to be specified in tvc.properties file.

tvc.3ddashboard.heTrueWidget.custom.resources = /webapps/HETrueWidget/helium/custom/launchpad
tvc.3ddashboard.tvcWidget.custom.resources = /webapps/tvc/custom

1.3. 6WTag and Search in the current tab support for JSON based widget.

JSON-based widgets or predefined widgets are, where the admin can predefine the configuration needed by the widget in the JSON file. This can be used to create the widgets directly. No need to select config after adding a widget to the dashboard.

Previously there was no support to use 6WTags in JSON-based widgets. From this release, we have extended the support for 6Wtags integration to JSON-based widget.

1.4. Widget Preferences Internationalisation.

Widget preferences are used by TVCWidget and HeTrueWidgets to save / load various configurations, like config to load, drag and drop support, etc. For widget preferences, internationalisation is now supported. To enable internationalisation, the admin must place a translation file in the webapps/tvc/asset/nls folder with the format TVC_3DDTranslation_lang.json.

Sample file for German language. TVC_3DDTranslation_de.json

{
    "Title": "Titel",
    "Search And Drop": "Suchen und ablegen",
    "Search Droppable": "Droppable suchen",
    "Widget Type": "Widget-Typ",
    "Persist Context Object": "Persistenz-Kontextobjekt",
    "Subscribe OOTB": "Abonnieren Sie OOTB",
    "Table Link Publish": "Tabellenlink veröffentlichen",
    "Config": "Konfig",
    "Search Config": "Konfig suchen",
    "Type To Drop": "Geben Sie zum Ablegen ein",
    "Please select a Type To Drop": "Bitte wählen Sie einen zu löschenden Typ aus",
    "Please select a Config": "Bitte wählen Sie eine Konfig",
    "Widget List": "Widget-Liste",
    "Select 6W Category": "Wählen Sie die 6W-Kategorie",
    "Subscriptions": "Abonnements",
    "Type not allowed": "Typ nicht erlaubt",
    "Drop Zone": "Abwurfgebiet"
}

Figure 3. Widget Preferences in English

Figure 4. Widget Preferences in German

2. Workflow

2.1. Workflow Chart Column in 3DDASHBOARD.

In the case of 3DDASHBOARD, if a table page is configured along with workflow chart column in a tvc widget then Collaboration panel widget need to be configured and added into dashboard to open a respective workflow on clicking the workflow chart icon.

Refer 3DDASHBOARD Widgets to add the collaboration panel App and widget.

Figure 5. Workflow chart behavior in 3DDASHBOARD.

2.2. Person absence and delegation Information for Multiple Application Servers.

In Collaboration, person information is cached in a java object to avoid the multiple DB hits. During the update of person absence and delegation information from My Profile page, cache updating is taken care of.

But in some of the use cases where information is updated through different forms / in the case of multiple application servers / by any other means, the person’s information cache is not synchronized and because of this, task delegation does not work properly.

The following system property could be used to disable the cache for the task delegation use case.

Property

Description

Default

tvc.collaboration.person.delegation.cache

to use java object cache to fetch the person delegation information

true

This property will not impact any other caching. It would be helpful for multiple App server environments where the java object cache is not synchronized.

3. New Search Experience

3.1. Search result behaviour on No Result Found.

We have introduced a new setting noResultShowsEmptyTable which will help to customize the search result behaviour. If noResultShowsEmptyTable value is set to true then in case of no search result, the search result section will show an empty table else No Result Found message will be displayed. It will be useful for users to use table features like create even when there is no search result.

default value for noResultShowsEmptyTable is set to false. |

<Settings>
    <Setting name="noResultShowsEmptyTable" value="true" />
</Settings>

3.2. Introduction of time zone offset for exalead search.

Exalead server stores the values in UTC. When a user searches the data on exalead, search criteria entered is in the local timezone which might not be the UTC and can give the wrong result. To overcome this situation, we have introduced the new setting timeZoneOffset where the admin can leverage this setting and configure the zone offset difference between the local time zone and UTC.

For example, IST has offset of UTC+05.30 then the timeZoneOffset value should be set to -5.30.

<Settings>
    <Setting name="timeZoneOffset" value="-5.30" />
</Settings>