What's New in TIBCO EBX® 6.1.1

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

Search
Permissions
Data visualization
Staging
Integration and Development APIs
Matching & Merging enhancements
Digital Asset Management
Data reporting
Performances

Previously in EBX6, it was not possible to define complex searches involving multiple attributes.
Now, it is possible to use a combination of multiple attributes with logical operators (AND, OR, NOT).
The definition of this search is done in a graphical way, which simplifies the configuration.

Search on association

Search on associated objects label

Previously, it was possible to select associated objects as a search criteria.
Now, it is possible to search on the associated objects labels as well. This gives the ability to perform such request: Who are the customers whose addresses label contain “Paris”?

This feature is available on the UI (Quick search and Advanced search), in the Java API and through data services (REST calls and SOAP operations).

Exclude fields for Quick Search

Better control on Quick Search performances

Previously, the search was performed on every field of a table when Quick Search was used.
Now, it is possible to define in a precise way the scope of this feature. It provides administrator a better control on this operation, and allows to tune the performances, especially in the context of large data models.
It is still possible to use the Advanced Search on these fields.

Permissions

New dataset permission setup screen

Configure and check all dataset permissions in a single screen

Previously, as permissions were defined per profile, it was difficult to have an overview of all the defined permissions for a dataset.
Now, a new feature is available to edit and display the permissions, in one single screen.
It simplifies the management of the permissions for administrators.
It is also simpler to check that what has been configured matches what was defined in the conception phase.

Access to the history of a table having scripted permissions enabled

Define who has access to history when scripted permissions are defined

As a current limitation, scripted permissions rules cannot be applied in the context of a table history and for security reason the access to this history has been disabled when these rules are defined.
Now, it is possible to define which profiles have access to the history when such rules are set up.
These profiles can be selected when editing the permission rule.

Data visualization

Org Chart : Edit graph display service

Create new org chart configuration graphically

Previously, it was not possible to create an Org chart using the Edit graph display service directly from the data. The configuration was only available on the administration.
Now, directly on your table, after selecting at least one record, it is possible to create and edit the Org chart configuration graphically.
Options are available on the left pane :

Link the node with a DAMA field
Add more fields on the node to be displayed on the graph

This feature is available on the UI (Display data using configuration) on creation and also on the graph by clicking on the corresponding icon.

Org Chart : Mini Map

Display of the mini map on the Org Chart to facilitate the navigation on the graph

Previously, the mini map was only displayed on standard graphs.
Now, the mini map is available on the Org Chart. It helps visualizing the full graph and facilitates the navigation inside it.
Users can drag the mouse on the mini map directly or click on a particular zone to directly access this area on the graph.

This feature is available on the UI (Display data using configuration).

Org Chart : Multiple records selection

Provides the ability to select several records to generate the Org Chart

Previously, the Org chart was only available for a single record selection.
Now, it is possible to select multiple records to generate the Org chart.
The graph will contain all the selected nodes and will automatically compute the hierarchy until the lowest common parent node (if exists). If no common ancestor is found, nodes display individually on the graph.

This feature is available on the UI (Display data using configuration).

Hierarchy dimension selector improvement

UI improvements on the dimension selector while creating a new hierarchical view

Previously, it was difficult to clearly identify which dimension was the foreign key and which one was the group by hierarchy.
Now, the dimension selector has been enhanced to provide a clear view of the type of field :

The foreign key field is now clearly identified with the target table on the right.
The group by hierarchy field has now a dedicated icon and the target table on the right has been removed.

This feature is available on the UI on the creation wizard of a hierarchical view.

Staging

New EBX components added in staging

Manage more and more EBX components into the staging : Workflow models, Scheduled tasks and Global permissions

Previously, the staging feature did not manage important EBX components like workflow models.
Now, workflow models, scheduled tasks, and global permissions are available as part of the staging archive.
Staging now allows the migration of a full EBX data domain from one environment to another with all user flows and technical tasks.

This feature is available on the UI (Staging on the administration) and through data services (REST calls).

Automatic import on startup

Automatically import staging archives on server startup

Previously, the staging import could only be done manually or using REST services.
Now, a new property has been added on ebx.properties file allowing to trigger imports of staging archives on server startup. Configuration and options can be set using instructions.json file.
Available options are:

forceUpdateOnIdenticalComponent : forces the update of a component even if it is the same on the repository.
importDomainDefinition : imports the domain definition in the staging domain configurations

Digital assets migration via Staging

Users can seamlessly migrate all digital assets, including their versions, tags, and reference data, from one environment to another

Previously, the staging scope was covering only Drive and DAC configurations.
The migrated assets have all the supported functions available just like the original assets.
Users can export and import physical files using the REST API.

Match and Merge configurations migration via Staging

Match and Merge configurations export is now covered by the Staging feature, allowing users to seamlessly export and import them within the EBX UI

This eliminates the previous limitation of overriding all configurations in the target environment.
Distinct policies can be directly imported into the target environment, allowing the use of matching configuration without additional updates.
The export includes matching configuration with all related elements such as matching and merge policies, main information and replications.

Data Integration and Development APIs

New import format: .xlsm files

XLSM files import on table and dataset levels

Previously, only .xls and .xlsx Excel files were possible to import, .xlsm files import was not supported.
Now, in addition to .xls and .xlsx, EBX supports .xlsm files.

This feature is available on the UI and the Java API.

More statistics

Display 'Update' and 'Skipped' statistics on import/transfer result screens

Previously, on result screen of import or transfer service, only statistics for “insert”, “delete" and “invalid" records were displayed.
Now, the number of “updated” and “skipped” records is available for import and transfer services.

This feature is available on both UI and log file.

Ability for admin to set 'Default option values'

Support to set “Default option values" for import, export and transfer services

Previously, it was not possible to define default values for options displayed in the services configuration screens.
Now, an administrator can set the default option values for import, export, and transfer services.

New built-in transformation function

Ability to split a single value into multiple values

When a field contains multiple values, it is now possible to define how these values should be split thanks to a separator and then be mapped to a multi-valued field in EBX.

Documentation on transformation function

Name and description are available for input/output of transformation functions

Now, Names and Descriptions are predefined and read-only, helping the user to know how the input/output fields should be used.

Business Object introspection API

Manipulate Business Objects in your Java code

Ability to get the definition of a Business Object through the use of the Java Public API.

Matching & Merging enhancements

More flexibility for the Inline matching workflow task configuration

It is now possible to customize the matching policy that will be used for the Inline Matching Workflow task

In the past the Default matching policy was the only option available for the users.
A new parameter named "Matching policy" is displayed in "Inline matching" service configuration screen to select and alternative policy.
If an alternative policy is not selected, the default matching policy will be applied.

Search before create service enhancements

The Search before create service no longer needs to be enabled by an administrator. Additionally, when running the service, the matching policy is selectable

In the past the Default matching policy was the only option available for the users.
The chosen matching policy will determine which fields are available to search and the criteria used to locate potential matches.
The Search before create service is still available from the matching policy configuration, however it is marked as deprecated.

Simplified access to Validate groups service

The Validate groups service is crucial to obtain the list of groups that require data steward review. It is now always available from the actions menu

Previously it was necessary to execute it from the Consolidated view.
The Consolidated view has been deprecated. It is still available to access, but it is planned to be removed in a future release.

Miscellaneous

Various enhancements are implemented for a better user experience

A prefix has been added to the snapshots generated by MAME to simplify distinguishing them from other types of snapshots.
The deletion of replication is synchronized with the deletion of the respective matching configuration.
Comparison node default values updates :
- The default value for Comparison function is now All fields match.
- For the Full text, Fuzzy, and Hybrid fuzzy algorithms, the Minimum score now defaults to a value of 100.

Digital Asset Management

Resize the asset when downloading

The resolution of the downloaded asset can be reduced or increased to fit the destination requirements

Previously the assets could be downloaded with the original resolution only.

The resizing option is available for images and videos
The assets are grouped to easily find the resizable ones
Several standard resolutions are available in addition to the original one
A custom resolution is also available

New Download options for a DAM Administrator

Export the digital assets from multiple Drives directly from the Digital asset table

Previously, the Download or Export options were not available in this screen.
The user can filter and select the assets from the Digital asset table and Export them to a zip file.
In case the digital assets come from multiple Drives, they will be sorted by Drive in the exported Zip file.

Better experience when using external storage

Several features aiming to reduce the gap between the internal and external storages have been provided

Users now have the ability to define both the maximum and minimum resolution for assets stored at the external storage platforms like Amazon S3, Azure Blob, Sharepoint, and more.
Furthermore, they can opt for a synchronization mode that enhances performance, offering increased control over the asset management process.

Additional API

Java and REST API to get the image asset’s width and height

You can effortlessly extract crucial information about an image asset, such as its width and height.
This combination enables you to efficiently analyze and utilize the image asset in a wide range of applications.

Data reporting

Delete dashboard

Remove a Dashboard

The dashboard owner(s) are now able to delete a dashboard.
When a dashboard is deleted, all data related to its configuration are also removed.
The delete icon is available only for the owner(s).

Performances

Quicker access to Workflow tables

Workflow tables contents are displayed faster

Optimizations have been implemented in order to display Workflow tables with high volume more quickly.
These optimizations impact these tables: Inbox, Publications, Active workflows, Work items, Completed workflows, and all Administration views of Execution of workflows.

Dataset inheritance

Better performances when dataset inheritance is used

Optimizations have been implemented in order to provide better performances when dataset inheritance is used, on different aspects:

Access to the data
Dataset Validation
Search of information

Matching Performances improvements

Performance has been improved for the following services:

Pre-processing optimization: Pre-processing now optimizes the number of comparisons by prioritizing complete records with equal token counts in fields.
Merged records modification process: This enhancement aims to improve the delta load matching process.
Business dataset validation process: For dataset with matching configured, it will help to retrieve the list of errors and warnings for the business data faster by excluding the matching-related metadata.