Latest version available for download on eDelivery
TIBCO EBX® product documentation
Back to the What's New in EBX® landing page
This page describes the new features and improvements brought by EBX® 6.1.0.
Additional content available on:
Table of Contents
- Side Bar & Social MDM
- Data visualization
- Data modeling
- Integration and Development APIs
- Matching & Merging enhancements
- Digital Asset Management
Additional information on elements and social features access
A new bar at the right side of the EBX® window has been added to easily provide contextual information with one click.
At table level it gives information about the displayed table.
At record level it gives information about the current record.
It also gives access to the social features related to this record (aka Team Up).
Brand new social features for enriched collaborationThere was previously no way in EBX® for users to provide feedback on table records (about quality, points for attention, issues, etc), nor to classify records (tags).
- The 'Team Up' features aim to improve the collaboration and engagement of the EBX® users.
- It reuses the new (right) side bar concept.
- It allows users to interact about data records by commenting, rating and assigning tags to those records.
- Some metadata can be reused along with EBX® searching (e.g Tags) and sorting features (e.g Ratings).
New visual display modePreviously, there were only three display modes to view records in EBX® (i.e. simple table views, hierarchies and graphs). Moreover, if customers wanted to leverage images from the record?s data, they needed to develop specific code in order to render images in such views.
Now, there is a new display mode called Tile View:
Group By hierarchiesIn previous versions, grouping data having common values was limited to some data types and to a single field on the selected table.
Now, the dimension in a Group By hierarchy can be defined using columns located in the same table. Allowed column data types are foreign keys or the following enumerable types: String, Integer, Enumeration, and Boolean.
A group by hierarchy also provides flexibility when setting the order for dimension levels.
For example, a Product table might include the following columns: Brand, Segment, Type, and Packaging.
Use these columns in any order to show products by: Segment --> Type --> Packaging, or Brand --> Segment --> Type --> Packaging.
Skipped level hierarchiesIn previous versions, except for recursive hierarchies, it was not possible to have unbalanced/ragged hierarchies (i.e. hierarchies including members where their parent skips one level).
Now, it is possible to create a skipped-level hierarchy, where nodes not having parents can be attached to grandparents.
TimelineIn previous versions, for tables having a date field, it was difficult to display records in a hierarchy whose nodes would be derived version of the date (e.g. Quarter, Month, etc).
Considering a project table with a deadline(date) field.
We could generate a hierarchy ?Project by Category by Date? but sometimes the requirement is to display not by date but by another time dimension (By year, by Quarter, by Month).
Now, for any date field, it is possible to build a configurable time-based hierarchy dimension (using century, year, quarter, month node types).
Introducing the Org ChartA new graph type is now available inside DMDV : the Org Chart which can display any organizational data such as HR, Companies, Legal entities, or any hierarchical data.
All current features of the current graph are also available on the Org chart (Navigation, Export, Zoo-in/Zoom-out,Expand/Collapse nodes).
Configuration is done on the same tables as the current graph.
New parameters have been added dedicated to the org chart.
Fields to be displayed on the nodes are configurable.
New nodes customization out of the box:
View node details directly from the graph (right click on the node and select open record).
Export PDF, SVG and PNG.
Display selected data - Team Up360° view of your Team Up data using DMDV.
Team up data available on each records to be displayed :
Display selected data
Display data model : Show/Hide linksAbility to hide & show all the links of the graph with one single click using the dedicated display button added on the top banner.
Display data model : Breadcrumb update after saveIn EBX® 6.0.10 we added an evolution on the data model save feature. However the breadcrumb was not updated after saving a graph. This limitation has been resolved in EBX® 6.1.0.
New global propertiesTwo new properties are now available in the configuration inside the ?Global Properties and Options? group to limit the number of records to display when expanding nodes:
Metadata information usable in queriesPreviously, it was cumbersome to manage a record metadata such as its creation date.
Now, some metadata information is available directly in the record structure as the data model now automatically embeds metadata nodes. Hence this information can be accessed using queries (XPath with Java API or REST calls, or SQL).
The available nodes are:
Also when activating Team Up, the comments, the ratings and the tags are included in the queryable metadata information.
Simpler access to tables for SQL requests and Data Services operationsPreviously, it was only possible to refer to tables by using their paths which could lead to some difficulties (typing errors, long paths, path changes that need to be replicated in multiple locations, ?).
Entity names allow to refer to tables in SQL requests and Data Service operations using unique names instead of their paths.
These names are easily configurable using a mapping table in the Data model configuration.
They can be retrieved using the Java API.
By default, an entity name, based on the last step of the table path, is now automatically set for tables when no name is explicitly defined in the data model.
If duplicated entity names are present, an error is raised during data model compilation time in order to manually define unique entity names.
Generalization of advanced search strategies selectionPreviously, Information Search add-on needed to be deployed to select advanced search strategies to be applied on String fields.
Now, these strategies can be selected and configured in the data model.
The available strategies are:
Broaden search to AssociationsPreviously, search was limited to the selected table content.
Now it is possible to select a table association and search on the records labels of this association.
This feature is available on the UI (Advanced search), in the Java API and through data services (REST calls and SOAP operations).
Search on tags, comments and ratingsTeam Up information is now available as criterion search.
Hence it is easy to retrieve
Searchable records metadata informationPreviously, it was not possible on the UI to filter records using their metadata information.
Now, as metadata elements are automatically added to records structure, these elements can be used as search criterion.
It now becomes easy to get the list of records created by a specific user or to see the list of records updated this month.
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).
Improved UX and records metadata supportPreviously, it was needed to scroll down the list of fields to select the type of permissions to apply for each field, which was not convenient when displaying more than 10 lines.
Now the available types of permissions are located on the top of the fields list.
Record metadata access rights management is available in this screen as well.
Out-of-the-box configuration migrationPreviously, there was no native feature to migrate configurations/artefacts between EBX® environments (e.g. from development to testing environment).
Customers were mainly performing manual tasks or relying on specific code to ensure such environment staging (data, models, workflows, import/export configurations, etc..).
Now EBX® offers a native staging feature.
Migration is configured per each domain managed in EBX® (e.g. Products, Employees, Third Parties, etc).
Data Exchange add-on (DINT) ready for stagingElements available in the staging:
Visualization add-on (DMDV) ready for stagingVisualization elements available in the staging:
Insight add-on (DPRA) ready for stagingAllow migration of all dashboards.
Additional scripts to manage dataPreviously, custom development had to be integrated within specific script tasks to execute some actions on the data.
Now, a set of new scripts have been added to perform the following actions:
Layout orientation customizationPreviously, steps and links needed to be manually moved to display them in columns.
Now, a new option allows to apply a vertical layout to the current diagram.
Arrange the links as you wishPreviously, when having many steps displayed it was not easy to clearly distinguish links which were automatically positioned whenever a step was moved.
Now, movable link connectors can be easily placed anywhere around the steps boxes allowing to completely customize the layout of the steps and links.
Be warned when unsaved changes are donePreviously, when changes were performed on the layout and the user added a new step or updated an existing one without saving the layout first, then when going back to the diagram, the displayed layout did not reflect the previous unsaved changes.
Now, a pop-up is displayed to warn the user about unsaved changes when he clicks on the link to add a new step or when he clicks on a step to edit its content.
A single activation instance for multiple tablesPreviously, to enable a workflow launcher on multiple tables, it was necessary to create as many activation instances as target tables.
Now, it is possible to select multiple tables within an activation configuration form.
An additional way to launch a workflowPreviously, workflows could be launched from a tabular view using the Action menu or from a record form.
Now, it is possible to launch a workflow directly from a table row custom toolbar.
REST Toolkit APIsOpenAPI extension of the ?api? category to generate document for REST Toolkit resource.
Built-in RESTful services
Built-in SOAP operations
Data Exchange (DINT) enables the simulation of CSV/EXCEL importAllows users to use the current configuration and mapping settings to simulate a data import.
The simulation results can include different levels (error, warning, and information) of non-blocking, blocking submission, blocking operator.
Ability to view errors directly (limited to 100 rows) or to download an error file to analyze errors.
Uses the result information to make any needed changes before performing the actual import.
Is available for import on both table and data set levels.
Data Exchange (DINT) templates allowing data filteringPreviously, the only way to export filtered data was to use table views.
Now, data export templates can be defined embedding custom data filters.
Hence, for example, these filters can be used by custom workflow script tasks using the appropriate Template ID.
Data Exchange (DINT) supports SQL connection to MS SQL Server using Windows authenticationDatabase can be accessed using Windows authentication by username and password
New development libraries ebx-api.jar and ebx-resource-api.jarCompilation and build operations must now use these libraries instead of ebx.jar library whose Java types are now visible. These development libraries ensure the reliability of EBX® custom modules by guaranteeing exclusive use of public API.
At runtime, they should not be deployed while ebx.jar remains required.
Blocking access to not fully initialized repositoryNew API to block access attempts to a partially initialized repository until it is able to handle data services (SOAP, REST Built-in, REST Toolkit) and UI.
Information on custom viewsNew API to get information on views such as:
It?s now possible to execute Business Object (BO) matching once BO is committedPreviously, only Manual matching option was available for BO.
BO Matching trigger can be paused, so that the deduplication is not executed during the BO import.
Once the batch import is finished, newly created BOs can be matched thanks to the new ?After submission? setting.
It?s now possible to execute the Evaluate matching from the EBX tabular view and from Manage group screen of the BOPreviously, this service has been supported only for the table matching.
The Evaluate matching service is reflecting the Matching fields coming from the related objects (for example Phone and Email fields in the below screenshot).
The service is working in a same way as for the table matching : 2 objects should be selected to simulate the output.
Related tables included in the golden record processingPreviously, it was not possible to create golden records in the related tables.
?Manual Merge? screen allows a Data Steward to review the related tables and to select the values to include into a golden record.
A compact preview screen lists all the changes occurred in different parts of the Business Object.
Easily follow all the sub-steps of the related table manual mergingIn previous versions the navigation between related tables steps was not explicit.
A new vertical step bar has been provided to improve the UX of BO manual merge (based on customers feedback).
More space is available to display the data.
Tooltips are available when hovering the step bar.
Leveraged UX for the Data Stewardship for table matchingPreviously, Manage Group screen had limitations related to the screen separation into Match and suspect sections (for example impossible to compare a Match record with a Suspect).
The UI has been reorganized based on customers feedback.
It is possible to perform the actions on Suspect and Match records.
It is possible to customize the attributes order thanks to the new custom view feature.
More details on the Pre-processing phase outputThe pre-processing used to be a black box, but it is no longer the case.
Thanks to the explicit guidance the user can check and adjust the pre-processing parameters (Matching fields, weight, search strategies?).
In case 2 records have been filtered at the pre-processing step, the user can see why it has happened.
Users can have several sets of parameters for Hybrid fuzzy algorithmBefore 6.1 version only default values were available, hence the users were not able to adjust parameters to better meet the business requirements.
Now, the configurable parameters (Synonym, Levenstein-1, Levenstein-2) are available at the decision tree node level.
The customized settings are saved and can be reused.
More flexibility to manage the merged records update flowPreviously the records were put out of the group when a matching field was updated.
Three options are currently available:
Additional Java APIs have been provided
New way to organize the assets in the DrivePreviously, all the assets were organized at the same level, hence it was not possible to keep the same structure as the external file management systems.
Built-in Drive UI has been improved by allowing users to create folders and to move the assets between folders.
When visualizing the external Drive via EBX UI, the original assets organization can be kept.
Out-of-the-box connectorsPreviously, it required a lot of coding to connect to third party file management applications.
Now, two additional built-in connectors to the most popular systems Microsoft SharePoint and Google Drive are available for the selection.
Consequenlty, the user can use EBX® DAMA Drive view as an interface to view the files in Microsoft SharePoint and Google Drive.
More specific search capability and improved navigationPreviously, it was not possible to perform advanced search in Drive view.
Currently it becomes possible thanks to the advanced mode.
It is also possible to easier navigate among drives thanks to the new Drive search feature.