Introducing the all-new TIBCO Community site!

For current users, please click "Sign In" to reset your password and access the enhanced features. If you're a first-time visitor, we extend a warm welcome—click "Sign Up" to become a part of the TIBCO Community!

If you're seeking alternative community sites, explore ibi, Jaspersoft, and Spotfire.

Jump to content
  • What's New in TIBCO EBX® 6.1.2


    Michael Ratovo

    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

    Org Chart: The step by step mode

    New view mode available on the Org chart

    A new view mode is now available on the Org Chart focusing on one level : The step by step mode.
    The step by step mode introduces a new way of navigating on the org chart by displaying only one level at a time (a parent and its direct children).
    Users can go up and down on the hierarchy by using the dedicated buttons.
    A breadcrumb is also available to show the different levels crossed by the user.
    Users can still open directly the records by right clicking on the node they want to see in detail.
    User-added image
     

    Org Chart: Additional Features

    Breadcrumb and number of children

    New graphical elements are available with the Step by step mode on the org chart.
    The breadcrumb is filled and updated every time users go up and down on the tree showing the path used from the starting node.
    Users can click on any level of the breadcrumb to automatically display the related parent and its direct children. This feature allows users to quickly navigate on the graph.
    On each node, we now display the number of children available (if any). It simplifies the navigation since users know directly on which node to click to expand a new level.
    User-added image
     

    Org Chart: Default view

    When creating a new configuration, users can now select the default view to use to display the Org chart (standard or step by step)

    When creating a new graph configuration, it is now possible to select the default view applied:
      - Standard
      - Step by step
    This default view will be used when launching the graph. Then users can switch to the other view when needed.
    User-added image
    The change of the default view is only possible on the administration. We will remove this limitation in a future release.
     

    Org Chart: Switch view

    It is now possible to switch from Standard mode to Step by step mode (and vice versa) anytime while navigating on the graph

    With the addition of the new Step by Step view mode on the org chart, users now have the ability to switch from one view mode to the other whenever they want.
    From the standard mode, users can right click on a node and select the menu “Switch to Step by step mode”. Then the Step by Step view is applied with the selected node, its parent and all the children at the same levels.
    From the Step by step mode, users can right click on a node and select the menu “Switch to Standard mode”. Then the standard mode view is applied and the selected node becomes the root node of the graph.
    User-added image
     

    Org Chart: Card tooltip

    The card tooltip is now displayed on the Org Chart

    Previously, there were no tooltip when hovering a node on the Org Chart.
    Now, when hovering a node on the Org Chart, a card tooltip is now displayed. It allows you to see more details about the node and see the full fields values displayed (it is truncated on the node if the text is too long).
    User-added image
    More elements will be added on the card tooltip in a future release.
     

    Search

    Hierarchical view: Quick search option

    New option on search on hierarchical views

    On previous EBX versions, the quick search on hierarchies was searching on all columns of the table. This was sometimes causing performance issues due to the number of columns.
    Now, we changed the default behavior of the quick search, in the context of a hierarchical view, to search only on the labels of the nodes instead of searching on all columns.
    We also added a new parameter in the quick search toolbar to activate the search on all columns as on previous EBX versions if needed.
    This change makes the default search on hierarchies more natural and provides better performances during the search.
    User-added image

    Permissions

    Access rules description in permissions screen

    Programmatic access rules information available on the UI

    Previously, using the UI, it was not possible to know if access rules were set on a node or a service.
    Now, in the new permission screen (introduced in EBX 6.1.1) the dynamic access rules and their descriptions are displayed along with the related node or service.
    User-added image
     

    Data Integration and Development APIs

    Specify scope for exporting related data

    Select related table and decide to include snapshot on Export

    Previously, all related tables on all dataspaces/snapshots were exported.
    Now, users can decide which related tables are exported and exclude data from snapshots.
    User-added image
    This feature is available on the UI and API (for template only).
     

    Handle permission for services

    Apply permission setting on Dataset for DINT services

    Previously, permission configuration on dataset was partially applied when using import/export/transfer services.
    Now, all permission definitions are fully used by Data Exchange services.
    User-added image
     

    Custom transformation function documentation

    Name, Description and Data type are available for input/output of custom transformation functions

    Previously, on API, user cannot set Name, Description and Data type.
    Now, Names, Descriptions and Data type are predefined and read-only, helping the user to know how the input/output fields should be used for Custom transformation function.
    On API, user also can set fixed number of input/output.
    User-added image
     

    Matching & Merging

    Operators: a new tool for data comparison

    An easier way to check whether the Match or No Match result for a specific field is based on the real values or based on the null values

    Previously, only a hardcoded value check was supported, so that custom solutions needed to be implemented to support this scenario.
    Now:
      - The Predicate comparison function has been deprecated
      - Four operators are currently supported : Equals, Either null, Both null, Both not null
      - List of supported data types has been enriched with 'date', 'time', 'dateTime', 'decimal', 'text', 'string', 'integer', 'boolean', 'email'.
    User-added image
     

    Replication of the Business object matching metadata

    Replication configuration is now available for the Record Metadata tables of the Business object metadata datasets

    Previously it was only possible to perform the SQL export of these tables.
    This replication enables external solutions or SQL requests to get the matching results directly from the database.
    User-added image
     

    User Experience Enhancements

    Simplified configuration and a better understanding of the matching results

    More details are provided on the matching results.
    User-added image
    The display order of fields in merge policies was updated so that Auto create new golden options are now at the top. This is more intuitive as Mode value can impact the availability of other options.
    User-added image
     

    New JAVA APIs

    Additional Java APIs are provided to interact with the Matching engine

      - Java API to accept/reject Suspect, remove Matches
      - Add the operators into the Data comparison node (replacement for "Criteria")
    This API works for both Matching with relationships and Business objects.
     

    Digital Asset Management

    Drag and drop assets to folders

    It is now possible to easily add the selected assets to a folder thanks to the drag and drop feature

    Previously it was only possible to move them thanks to 'Move to' service.
      - Select one or more digital assets and drag them to the folder of your choice.
      - A notification pop-up is sent once the action is completed.
      - The ‘Undo’ service is available via the pop-up notification.
    User-added image
     

    Better control of the URL expiration time

    You can now specify the expiration time limit for asset URLs

    Previously the URL expired once the session was finished.
    Now:
      - The expiration time limit for asset URLs can be specified in the ebx.properties file by changing the value of ebx.addon.dama.rest.token.timeout.
      - This property defaults to a value of 1800 seconds (30 minutes).
      - The useAddonToken parameter was removed from all REST endpoints.
     

    New JAVA API

    Some Java APIs have been provided in addition to the feature delivered in the previous version

      - Java API to change the size of assets for downloading.
     

    Performances

    Performance improvements

    Performances improvements have been done on various parts of EBX®

    • Recursive hierarchies: On recursive hierarchies and recursive hierarchies containing a filter, the algorithm has been optimized. The result is that performances have been greatly improved and the display of such hierarchies is significantly faster than on previous EBX 6 versions.
    • Quick search on hierarchies: With this evolution the search is now by default performed only on the fields labels of the nodes of the hierarchy which make the search quicker.
    • Change state on Matching operations: This key operation driven by the matching engine to handle the states of the records has been improved.

    Miscellaneous

    Logs configuration

    Configure your logs using Apache Log4j™ 2

    On previous EBX® versions, an older version was provided, with limited configuration capabilities.
    Now, you can fully embrace the options provided by Apache Log4j™ 2.
    You can for example:
      - Use any log4j2 appenders (Kafka is now an option)
      - Centralize your log configuration for all the web application
      - Delete old log files based on a defined retention period
      - And more!
    Note: In terms of configuration, the ebx.properties file can still be used. It is also possible to use a combination of Apache Log4j™ 2 and the ebx.properties main configuration file.
     

    Kubernetes platform support

    Official support of OpenShift!

    EBX® Container Edition is now compatible with Red Hat® OpenShift®
    User-added image

     

     


    User Feedback

    Recommended Comments

    There are no comments to display.



    Create an account or sign in to comment

    You need to be a member in order to leave a comment

    Create an account

    Sign up for a new account in our community. It's easy!

    Register a new account

    Sign in

    Already have an account? Sign in here.

    Sign In Now

×
×
  • Create New...