What's New in TIBCO EBX® 6.1.3

Latest version available for download on eDelivery

TIBCO EBX^® product documentation

Back to the What's New in EBX^® 6.1 page

Back to the What's New in EBX^® landing page

  Table of Contents

• Data visualization
• Workflow
• Permissions
• Data Modeling
• Staging
• Data Integration and Development APIs
• Matching & Merging
• Digital Asset Management
• Performances
• Miscellaneous
• Important information for current users before upgrading

Data visualization

Org Chart: Card tooltip

Additional fields can be displayed on the card tooltip

Previously, we could display only two fields on the card tooltip.

Now, the tooltip can display up to 5 fields. It allows you to see more details about the node and increase the amount of information visible directly on the graph. The card tooltip is available in standard mode and step by step mode.

Org Chart: Show more/Show less

Step by step mode: Improved user experience on nodes with many children

When having a lot of children to display on the Org Chart in step by step mode, it?s not often necessary to display all nodes at once.

To improve the user experience and the navigation on the Org Chart we now initially display a limited number of children nodes. The user can then display more nodes by clicking on the ?Show more? button, or less nodes by clicking on the ?Show less? button.

Org Chart: Additional Features

Default view configuration and number of children

Previous limitations have been removed on this new version.

The previous limitation about the change of the default view only possible on the administration has been removed. Now, a dedicated section on the Edit Graph display service is available on the Org Chart to select the default view applied to the graph.

The number of children nodes is now available on the standard mode of the Org Chart. It was previously available only on the step by step mode.

Workflow

API Publish and Unpublish Workflows

Automate the management of your Workflows

Previously it was not possible to automate the publication of Workflow models.

Now some Java APIs are available to manage your Workflow publications.

Permissions

Services permissions on tables

Permissions on services can be defined for each table separately

Previously, services permissions could only be configured at dataset level, i.e. for all tables of this dataset.

Now, it is possible to define specific services permissions for each table.

Permissions on hierarchies actions

Extended ability to define permissions on hierarchies actions

Previously, permissions on hierarchies actions were limited to Move service and Open link record service.

Now, it is possible to define permissions for the following services:

• Associate (attach a node to another one)
• Detach
• Move
• Open link record

It can be configured at Dataset level and at Table level.

These permissions can also be configured programmatically.

Scripted permissions enhancements

Additional information available for scripted permission rules

It is now possible to define scripted record permissions based on:

• the current date and time using datetimeNow(), dateNow() and timeNow() functions
• the workflow input variables when permissions are evaluated during a workflow execution

Data Modeling

Case sensitivity of uniqueness constraints

More flexibility on uniqueness constraints behavior configuration

Previously, uniqueness constraints (ability to define that a field or a set of fields should be unique on a table) were case sensitive.

Now, it is possible to define in the data model what should be the behavior (case sensitive or case insensitive). By default, it will remain case sensitive.

Staging

Views and Roles

Staging now supports all views and roles (additional fields and roles inclusion)

Previously, it was only possible to add the Published views on the staging and the role was limited to its name.

Now, all views are available on the staging widget including non-published views. The published views are located under ?View publication? and the non-published views under ?Views?.

The staging module now manages the full role table (name, documentation and email) and the role inclusion.

Data Integration and Development APIs

Data Integration global permission configuration

Global permission is available for administrator to set restriction for specific user/role

Previously, it was not possible on the UI to restrict business user's access to certain functions of DINT.

Now, administrator can set specific permissions on specific services on Data integration.

Apply options from the main table for related tables when exporting

Option settings for related tables will follow settings for the main table when exporting related tables

Previously, when exporting related data, the default format was always applied for related table(s), regardless of the selected options.

Now, Export label options and options affecting data format which are set on the main table are also applied for exported related table.

It applies to services on UI and API.

Data transfer from one record to many records

Split data to one record to many records based on a single field or on many fields

Previously, DINT only allowed to split a single source field to multiple target fields and vice versa via transformation functions.

Now, the user can:

• Split the value of a single field to multiple records.
• Split the values of a multivalued field to multiple records.
• Split the values of a combination of fields to many records.

RESTful Services

New categories and operations for Business Objects, pagination improvement

Business Objects:

• New operation categories have been introduced to specify that the operation is on a Business Object (data-bo and data-compact-bo). It gives you the ability to:
  • Get the content of a Business Object (select operation)
  • Delete a Business Object
• It also support OpenAPI operations

Other:

• Pagination improvement: Selector pagination was enriched with three new links for first, previous, and last page navigation
• Dataset operations: Retrieve associated metadata, such as information about it (creator for example) or the hierarchical structure in case of dataset inheritance

Java APIs

Additions to the public Java API

• Publish / Unpublish one or multiple Workflow model(s) thanks to the new WorkflowPublisher interface
• New API to build URIs for Business Objects (in CategoryURIBuilder)
• Dependencies to dataset fields: It is now possible to define, in a constraint on table, a dependency to a dataset field (field not under a table). In the context of the incremental validation, this means that any updates performed on the dataset field will imply a full revalidation of the constraint.

Matching & Merging

Ability to register the lists of synonyms and stop words from the UI

A more user friendly way to register the lists of synonyms and stop words in the Search extension

In the past only technical users were able to register those lists.

Now:

• 2 additional sections added to the DMA search extensions
• The lists can be added manually or via standard csv or xml import. They can also be exported
• For the synonyms the main word aims to prevent the user from creation of multiple lists for the same items.
• All the synonyms from the group are considered as matches to each other
• Once added the lists will be automatically taken into account by the indexing

Special characters are preserved when using distance algorithms

More accurate score is returned for the strings containing special characters

In the past the special characters (e.g., %$&*(), etc.) was converted into spaces.

Now:

• This behavior is applied for JaroWinkler and Levenshtein distance algorithms
• Score 1.0 is returned when 2 values are the same
• Multiple white spaces are also kept to compare and will not be replaced by the single white space

Fk alignment logs enhancement

More accurate logs to assist the debug process

The number of lines has been reduced and clear structure and error messages have been added.

Clear error messages have been added to cover various permissions violations at the field node of the table.

Also, the error messages are written in the logs in case of create/update of the related record permission violation.

Miscellaneous

Various enhancements for the survivorship, metadata dataset content and for the API

• The survivor record selection in case there are no or multiple records satisfying the survivorship conditions will now follow a clear rule: it is the lowest PK record that will become golden.
• The outdated matching selection will be cleansed from the metadata dataset when executing the 'Purge old matching' service.
• It is now possible get more accurate number of Suspect relationships while querying the Matching Result table. Starting from now, when a Suspect is accepted by the user, the Suspect relationship between the accepted record and any other records from the Matches section will be removed from the Matching result table.
• The API to get the whole list of the records in the group and the list of the suspects targeting to the group has been optimized to avoid the potential performance issues : several processes have been grouped into a single SQL query.

Digital Asset Management

Display the attached images in the tile view

The image assets attached to EBX records can be now integrated into the tile view

Previously, the user had to input a URL of every image to be displayed.

It is now possible to select the media type field corresponding to the desired attachment to be displayed in the tile view.

For the media type field to be visible in the view configuration, the maximum authorized number of attachments has to be related to 1 in the data model assistant (following the EBX behavior).

Pagination in the Drive view

Customize the display and avoid performance issues thanks to the pagination feature

In the past in was not possible to set the number of assets to display per page. 50 assets were displayed by default while the part was loading.

Now:

• Navigation buttons "Go to the beginning", "Previous", "Next", "Go to the end" have been added to the Drive view.
• The assets are loaded and displayed based on selected pagination similar to EBX tabular view.
• 'Select all in view' and 'Select all in page' options have been added

Performances

Matching Performance improvements

Performance has been improved for the following services

Merging phase : FK alignment and snapshots removal

1. FK alignment performance has been improved for both Table matching and Business object contexts. The calculation time has been reduced to below 50%.
2. Snapshots (being the root cause of the performance issues) are no longer generated during the merging phase since they are now replaced by the transaction difference API.

Index integrity check

Reduce the instance starting time

The Index integrity check is the operation that checks that the indexes are not corrupted (aligned with the underlying data). If the indexes are not valid, then a rebuild operation is done.

Previously, the integrity check was done at boot time. For large volume of data, the global check could take an important time.

Now, EBX embraces a ?lazy approach?, meaning that the index check is done when data is accessed the first time, greatly reducing an instance starting time.

Dataset inheritance and validation

Define how the validation should be done on child datasets

In the ebx.properties file, you can now define how the validation in such context should behave (FULL or DIFF):

• DIFF is more efficient when you have a small volume of changes in child datasets
• FULL is more efficient when you have a lot of changes in child datasets

Miscellaneous

Container edition

More content and features on the installer to build different images

Legacy addons:

It is now possible to build an image containing legacy addons (EBX5 Addons migrated to EBX6)

Multiple architecture support:

When you are building an image, it is now possible to create an image containing a different architecture than the one that you are currently using. For example, from a MAC M1 using an ARM 64 architecture, you can build an AMD64 image.

Important information for current users before upgrading

Authentication

Introduction of the new ebx-authentication servlet

Custom directory implementation:

If you are currently using a custom directory implementation, an update in your configuration will be required, to take into account this new servlet:

• Enabling cookies and crosscontext for ebx.war and ebx-authentication.war
• Updating your redirect URI from /ebx to /ebx-authentication

Different users in different tabs:

As cookies are now used, a user will not be able to login with 2 different accounts in different tabs. But the  Incognito mode or the use of a second browser will be supported.

Supported environments

Update on the supported components

Supported databases:

PostgreSQL 11 is no longer supported.

The minimum supported version of PostgreSQL is now 12.

Supported Java environment:

JRE 17 and 21 LTS are now supported.

Support was removed for JRE 11, except for WebLogic 14c where JRE 11 currently remains supported