All release notes

Version 1.9.11

Released: January 2023

New features

Instructions were added to the documentation that describe how to prevent library conflicts when deploying on WebLogic. See the Preventing library conflicts on WebLogic heading in the index.html file that is located in the following folder in the 4.5.16 Add-on Bundle: documentation > igov_<xxx>.

Changes in Functionality

This release contains changes in functionality.

Changes to third-party libraries

This release contains no changes to third-party libraries.

Closed issues

This release contains no closed issues.

Known issues

This release contains no known issues.

Version 1.9.10

Released: December 2022

New features

This release contains no new features.

Changes in Functionality

This release contains changes in functionality.

Changes to third-party libraries

The Apache Batik library was updated to version 1.16.

Closed issues

This release contains no closed issues.

Known issues

This release contains no known issues.

Version 1.9.9

Released: October 2022

New features

This release contains no new features.

Changes in Functionality

This release contains changes in functionality.

Changes to third-party libraries

The following third-party libraries were updated:

• The Apache Batik library was updated to version 1.15.

• The Xalan library was removed.

Closed issues

[IGOV-1128] A vulnerability needs to be fixed.

Known issues

This release contains no known issues.

Version 1.9.8

Released: August 2022

New features

This release contains no new features.

Changes in Functionality

This release contains no functionality changes.

Changes to third-party libraries

The following third-party libraries were updated:

• The Apache FontBox library was updated to version 2.0.26.

• The Apache POI library was updated to version 5.2.2.

• The jQuery UI library was updated to version 1.13.2.

Closed issues

This release contains no closed issues.

Known issues

This release contains no known issues.

Version 1.9.7

Released: March 2022

New features

This release contains no new features.

Changes in Functionality

This release contains no functionality changes.

Changes to third-party libraries

The following third-party libraries were updated:

• The Apache FontBox library was updated to version 2.0.25.

• The JQuery library was updated to version 3.6.0.

• The jQuery UI library was updated to version 1.13.1.

Closed issues

This release contains no closed issues.

Known issues

This release contains no known issues.

Version 1.9.6

Released: December 2021

New features

This release contains no new features.

Changes in Functionality

This release contains no functionality changes.

Changes to third-party libraries

The jQuery UI library was updated to version 1.13.0.

Closed issues

This release contains the following closed issues:

• [IGOV-1100] Validate field inputs.

• [IGOV-1102] Validate data repository inputs.

Known issues

This release contains no known issues.

Version 1.9.5

Released: August 2021

New features

This release contains no new features.

Changes in Functionality

This release contains no functionality changes.

Changes to third-party libraries

This release contains the following third-party updates:

• Apache Commons Compress to version 1.21.

Closed issues

This release contains no closed issues.

Known issues

This release contains no known issues.

Version 1.9.4

Released: May 2021

Product updates

This release contains the following updates:

• The Apache Batik library was upgraded to version 1.14.

• The Apache FontBox library was upgraded to version 2.0.23.

• The Apahce Commons IO library was upgraded to version 2.8.0.

Version 1.9.3

Released: January 2021

Product updates

The Apache Common Codec library was upgraded to version 1.13.

Release Note 1.9.2

Release Date: September 18, 2020

Product update

• The add-on has been updated to support the OpenJDK8 and OpenJDK11 libraries.

• Libraries were updated to fix some potential issues.

Release Note 1.9.1

Release Date: June 23, 2020

Product update

The jQuery library was updated to version 3.4.0 and the log4j version 1.12.7 and dom4j version 1.6.1 libraries were removed.

Bug fixes

[IGOV-1070] An add-on description in French is not translated.

Release Note 1.9.0

Release Date: June 20, 2019

New features and updates

This release contains the following new features and updates:

• The add-on's services have been adapted and are now fully compatible with TIBCO EBX® 5.9.0 and later.

• When viewing a RACI matrix in the Party tab, the display orientation of the parties can be toggled. The parties can be displayed horizontally in the top row, or vertically in the first column. The following image highlights this feature:

  

• A RACI matrix can now be exported to an Excel file. The following image shows an example of an exported file:

  

Release Note 1.8.1

Release Date: March 25, 2019

New features

Support has been added to take into account the new version of the TIBCO EBX™ Information Search Add-on 2.4.0.

Release Note 1.8.0

Release Date: October 26, 2018

Adaptation

This release of the EBX® Information Governance Add-on has been partially adapted to the EBX® 5.9.0 GA release. The add-on's built-in services will be available in a future release. You can still manually create administered items. However, the item description metadata from the DMA cannot be synchronized. This functionality will be restored once adaptation efforts are complete.

Release Note 1.7.3

Release Date: May 2, 2018

New features

• Support has been added to take into account the new version of the TIBCO EBX™ Digital Asset Manager Add-on.

Release Note 1.7.2

Release Date: March 16, 2018

New features

• Support has been added to take into account the new version of the TIBCO EBX™ Information Search Add-on.

Release Note 1.7.1

Release Date: September 29, 2017

New features

• Support has been added to take into account the new version of TIBCO EBX™ Information Search Add-on 2.0.0.

Release Note 1.7.0

Release Date: April 18, 2017

New features

Export PDF

Property and Object Class Administered Items can be exported to a PDF file.

Bug fixes

• [25494] Unauthorized access to resources is possible.

Warnings

• Customers are strongly advised to upgrade to the latest version which patches the security issue.

Release Note 1.6.0

Release Date: December 16, 2016

New features

Business Glossary updates

• The Icon bar has been added to serve as a quick-reference for information regarding the selected Administered Item.

• You can now restrict user access to data models.

• You are now able to see information about the data model selected in the Browse tab.

• It is now possible to specify which icons represent Item quality information in the Business Glossary. You can set icons for 'Approval', 'Deployment', and 'Quality'.

Synchronize metadata

• The 'Synchronize metadata' service has been added to synchronize manually created Items with their data model. The 'Refresh Administered Items' service no longer synchronizes them.

RACI inheritance

• Properties can now automatically inherit parties and roles from parent Object Classes in the RACI view.

Data model declaration

• The 'Data model' field has been added to the 'Data model' table. You are now able to select a published data model to use as the basis for Administered Item management.

Export to relational service

• This service has been removed from the 'Data model' table. The export dataspace and dataset remain for now, but they will be removed in a future release.

Data quality integration

• You can now configure dashboards (titles) for the Association Item.

Tag link improvement

• Tag links can be easily added using a record's new 'Insert' button.

Repository hierarchies

• You can now assign icons to represent different types of Administered Items when viewing the 'Item' table as a hierarchy.

• The 'Party hierarchy' table has been added to represent the parent/child relationship between parties.

Table for extended attribute

• The new 'Restricted to data model' field has been added to restrict the Items from a data model that can access this table.

• The new 'Automatic display' field has been added to specify whether or not this table automatically displays when users open the related Item.

API

• New APIs have been added that allow you to run the 'Data model' table services.

Release Note 1.5.4

Release Date: October 28, 2016

New features

Dynamic info-tip and labels

• You are now able to hide the universal name on the info-tip using the 'Hide universal name' field.

• The linked rules name and description can be displayed on the info-tip using the 'Display rule information' property.

• The 'Maximum number of rules' property can be used to activate or deactivate the rules and configure how many rules to display.

Repository hierarchies

• The 'View misaligned meta-data' hierarchy view has been replaced with the tabular view.

• The 'Data repository' has been added to the top hierarchy level in all the hierarchy views of the 'Item' table.

Excel import/export

The 'Logical name' field has been added to the exported Excel file when using Light mode.

Property names and UI labels

• The 'Object Class' field in the 'Is association' group has been renamed to 'Linked Object Class'.

• You can now edit the records in the 'ISO type' table.

Release Note 1.5.3

Release Date: August 4, 2016

New features

'Physical' tab Administered Items

The 'Physical' tab has been added to 'Item' table and displays item fields related to the data model.

Release Note 1.5.2

Release Date: June 10, 2016

Bug fixes

• [20874] An Excel file cannot be imported if it contains a blank cell.

Release Note 1.5.1

Release Date: May 19, 2016

New features

Light mode in the 'Export in Excel' service

• When a file is exported using 'Light mode', it can be imported using the 'Import from Excel' service.

Import from Excel spreadsheet

• Rather than creating Administered Items manually, you can import them from an Excel file.

Bug fixes

• [20280] Wrong results in the exported Excel file when running 'Export in Excel' service from the occurrence page.

• [20291] The preview button is missing when Extended attribute value is a URL.

Release Note 1.5.0

Release Date: April 13, 2016

New features

Administered Item creation and history

• You can now manually create an Administered Item using the API.

• While manually creating an Administered Item, its type 'Data reference' property allows you to select the node's path in the logical data model. Previously, you had to type in the full path, which could prove difficult in large data models. Note that if you've already run the 'Create Administered Items' service on a data model, the option to automatically select a node path-while manually creating an item in that model-will not be available.

• The 'Universal name' field is now required and must be added to any Administered Item created manually.

• If an association is created manually, its related 'Object Class', 'Minimum occurrence' and 'Maximum occurrence' properties can be added manually.

• A history of Administered Item modifications is stored in the 'History' table. This behavior is turned on/off in the 'User preference' table. A 'Stack size' property is also available to define, which determines whether the number of stored history records follows a first-in/first-out approach and how many records get stored before the process of overwriting begins.

Graph view integration

• Administrators are able to specify whether users can see the 'Graph' and 'Meta Graph' tabs by adjusting configurations in the 'User preference' table.

RACI style view

• A RACI style matrix including images is displayed when viewing parties, roles and types. This behavior is implemented when viewing an item in the repository and when viewing an item in the Business Glossary.

Business Glossary updates

• The Business Glossary is now using an AJAX component that improves loading time and allows the glossary to use the documentation pane.

• How tab labels and attributes are displayed has been overhauled and gives users more fine-grained control over Business Glossary look and feel.

• A new 'List view' was added to the 'Query panel' that allows you to browse Object Classes and Properties in the selected data model.

• When an Administered Item is linked in an email, the recipient can open it directly in the Business Glossary.

Emailed Items

• Links to Administered Items now open directly in the Business glossary making all of the item's information readily available.

Repository hierarchies

• A new data model structure was created for the 'Classification' group.

Property names, values and UI labels

• The default value of the 'Search tab view by default' property is now 'No'.

• The default value of the 'De-duplication is active' property is now 'No'.

• 'Additional data' is now 'Additional attribute' and 'Extended data' to 'Extended attribute'.

• The 'Context' labels no longer contain the [ON] prefix when displayed via the 'Item' table.

• The 'Confidentiality' labels no longer contain the [ON] prefix when displayed via the 'Item' table.

• The [ON] prefix has been removed from the 'State' and 'Operation' table labels.

Release Note 1.4.4

Release Date: February 26, 2016

Adaptation

Adaptation of the UI to the new EBX® 5.7.0 ergonomics and layouts.

Release Note 1.4.3

Release Date: February 4, 2016

Adaptation

Adaptation of the UI to the new EBX® 5.7.0 ergonomics and layouts.

Release Note 1.4.2

Release Date: January 18, 2016

Bug fixes

• [18677] An error message displays when a user selects December as the input date.

Release Note 1.4.1

Release Date: July 23, 2015

Metadata creation

• When you create metadata manually from the data hierarchy view, the basic attributes are now fed by default depending on your position in the hierarchy: 'Data model', 'ISO type' or 'Logical data type'.

• Two new services allow you to create metadata from the data hierarchy's data model level: 'Create an Object Class' and 'Create a Property'.

Data repository extension

You can now declare new attributes based on any EBX® table-even tables not under EBX® Information Governance Add-on (IGov) control-while maintaining the safeguards ensured by IGov. This is accomplished through an extension of the IGov data model by referring to a table and a field using the 'Meaning' and 'Value' properties, respectively. For example, you might have a 'Product' Object Class under IGov control and want to add a new 'Law name' attribute from a data model not under IGov control. To achieve this you would declare the 'Law' table and 'name' field to extend 'Product' attributes. Then, when defining 'Product' metadata, you can choose the appropriate 'Law name'.

Data hierarchy display

The 'Data model unset' item is now hidden from the data hierarchy view.

Release Note 1.4.0

Release Date: June 10, 2015

Metadata creation

• You can now create metadata, or 'Administered Items' manually. In the previous add-on version, ' Administered Items' were created using an introspective lookup in the data model. After manual creation, you can link metadata to a data model element, such as a table or field. It does not matter whether metadata was created automatically, or manually; alignment between an 'Administered Item' and its related data model(s) is fully enforced.

• By allowing manual creation of metadata, business users can enter definitions and descriptions to anticipate new data design. These definitions and descriptions represent data business requirements.

Metadata deletion

You can now delete metadata in a logical mode. A 'purge' service performs physical deletion of logically deleted metadata.

Business glossary UI customization

• Information displayed in the 'Business glossary UI' can be configured as follows: 'Always displayed', 'Display if defined' and 'Always hidden'. This feature affords you complete control over the entirety of the 'Business glossary UI' based on user-profiles and end-user expectation.

• You can now configure a link from metadata to the actual data value. For instance, when displaying metadata for 'Product', a link allows opens the 'Product' table to get the actual data value. The data displayed depends on the users permission level.

• The fuzzy search panel is now extended with filters applied to the data type. For instance, this allows you to look for metadata applied to the 'Table' type only, ignoring metadata applied to other concepts such as 'Field', 'Group of fields', etc.

User comments management

Comments can be posted on all metadata and shared with users that have subscribed as recipients.

Definition and description

The definition and description context management now relies on a direct sortable data structure (arrow up/down) that replaces the 'Apply' button.

Export to Excel spreadsheet

The export process into an Excel spreadsheet has been improved. Now the spreadsheet is based on a multi-folders data structure that makes the exported data value clearer.

Data quality integration

You can integrate data quality information when displaying metadata. This information is delivered as dashboards (tiles) stemming from the TIBCO EBX™ Insight Add-on. For instance, when displaying the definition and description of the 'Client' metadata, a 'Quality' tab is available and contains the results of the 'Client' table's existing quality indicators.

Release Note 1.3.1

Release Date: April 9, 2015

TIBCO EBX™ Graph View Add-on 1.1.0

Support has been added to take into account the new version of TIBCO EBX™ Graph View Add-on 1.1.0.

Release Note 1.3.0

Release Date: January 26, 2015

Web Business glossary UI

Metadata can now be accessed through a web application outside the EBX® user interface. Authorized users can easily browse the Business glossary or search for information and/or metadata contained in an EBX® Information Governance Add-on repository. This is accomplished using an interface that provides access to data much in the same way as traditional web-based front-end application.

Management of relationships between Object Class items

The EBX® association modeling concept is now used to document relationships between Object Class items. This modeling concept allows the repository to provide meaningful documentation of the relationships regardless of the underlying join tables. The ability to directly document foreign key fields and join tables is still possible.

New metadata and display

Several metadata have been added to enrich the description of Administered items such as: 'Application', 'Confidentiality', 'Maintenance rules', 'Identifying properties', 'Rules', etc.

Release Note 1.2.1

Release Date: October 10, 2014

New feature

• It is now possible to add any bespoke data to complement with pre-defined meta-data. A group of information 'Additional data' is then available in the main definition part of every Administered item.

Release Note 1.2.0

Release Date: September 12, 2014

Dynamic management of table and field labels

The EBX® Information Governance Add-on API lets you customize table and field labels using the governance repository content. For instance, a table labeled 'Empl' in the data model, can display the labels 'Employee' or 'Staff' depending on the context associated with a user's profile. This is accomplished by means of an automatic lookup in the governance repository.

Trigger extension on the metadata

It is now possible to configure a trigger extension (Java class) on the table 'Administered item'. The Java class is then triggered during the Administered item modification and creation processes. This trigger extension can perform any type of actions: workflow execution, rules execution, data transfer, etc.

Graphical view of the metadata

The TIBCO EBX™ Graph View Add-on can be used to get graphical views of the metadata. When this add-on is installed, two tabs appear to get the graph views applied to the 'Data model' under governance, and the EBX® Information Governance Add-on repository by itself.

New metadata and display

• The metadata 'Is field' is enriched with its data type declared in the associated data model. In case the metadata 'Is field' is a foreign key, then the link to the associated Administered item is provided.

• The metadata 'Is property' is enriched with all the associated 'Data elements' using it. For instance the 'Age' property can be used in many tables with different data types such as: Empoyee.age[18..70], Company.age[1..200], etc.

• The metadata 'Is table' is enriched with the links to its associated Object Classes when there are one or many relationships with this table (foreign keys).

• New metadata 'Logical label' is now available on the Administered Items' main tab to display the naming from the logical data model.

• It is now possible to hide any Administered item by using the properties 'Is hidden' and 'View by only'. It allows you to hide metadata such as technical data, and filter the metadata by user-profile.

• A user preference configuration allows you to decide if the 'Is hidden' and 'View by only' properties are active or not. The UI tab 'Also defined in' can be hidden.

• The data models can now be grouped by 'Data repository' to get a better alignment with the Enterprise Data Architecture patterns.

Export the governance repository

• The governance repository can be exported into a flat relational table. From this table, the metadata can be exported in XML format or as an Excel spreadsheet. The metadata can then be queried using a third-party tool.

• The governance repository can be exported into a normalized relational table. From this table the metadata can be handled from data hierarchy views in EBX® and queried using a third-party tool.

Tag links

The resolved tag link label now includes the universal name of the linked item.

Release Note 1.1.0

Release Date: April 1, 2014

User interface improvements

• The definition and glossary text now use an HTML editor that allows rich rendering (fonts, bold, italic, color, size, hyperlinks, images, etc.).

• This text can integrate tag links to refer to any information in the governance repository. For instance, the text 'Refer to the item ai3392' is automatically transformed into 'Refer to the item 3392', where the hyperlink is computed using the key word "ai". A list of ready-to-use key words is available to link to any information in the governance repository.

Query administered items

A new UI is now available to query the administered items based on criteria and dates.

Java API

• New API allows using the descriptions and glossary as documentation panes on the tables and fields known to EBX®.

  This API relies on a configuration to display the correct description and glossary depending on the user context. For instance, a different description for the table 'Product' can be displayed for the sales department and for manufacturing.

Migration procedure

The migration of an existing EBX® Information Governance Add-on repository from GA 1.0.1 to GA 1.1.0 requires executing the service 'Validate data with tag links'. This service automatically completes the 'Identifier' fields used as references in the tag links. It exists as a service at the dataspace level to migrate the repository.

Release Note 1.0.1

Release Date: January 22, 2014

Universal name management

The 'Universal name' of composite Administered Item (Data Element Concept and Value Domain) is now based on the universal name of the related Administered Items. It is possible to overload this name and to reset it with the related Administered Items' names.

Smart UI

The size of the definition block is increased.

In the context naming definition of Administered Item, if the context is '[ON] DMA', the definition is automatically calculated and is not user-modifiable.

Release Note 1.0.0

Release Date: November 25, 2013

EBX® Information Governance Add-on provides a "governance repository" to manage the metadata applied to any assets known to EBX® (tables, fields, groups of fields, data types, workflows, rule). These assets can be master data that is under the control of the MDM system or any data managed by other applications.

The repository relies on the standard ISO-IEC 11179 (Information technology - Metadata registries MDR) that defines a robust data structure for collecting and sharing the knowledge applied to any data. It also provides a standard vocabulary to define the key concepts that a metadata repository must apply. This means that the knowledge collected in the "governance repository" is independent of the tool.

Since the governance repository is built using EBX®, it benefits from the MDM features to govern the metadata as real master data.

Business naming control

When a new element is entered into the repository, the add-on builds its 'default name' automatically. This name is based on the underlying data model loaded into EBX®. This means that the default name is related to the logical layer of the data management. This default name is inherited by another field known as the 'universal name'. This name can be changed by the administrator of the repository. This 'universal name' is related to the semantic layer of the data management. This two-level naming approach ensures a clear relation between the logical and the semantic levels of the data.

De-duplication of identical knowledge

A de-duplication process is executed when new information is entered into the repository. It allows checking if elements are duplicated. In this case, a shared definition of the related metadata can be defined.

Synchronization between the semantic and the data logical layers

At any time, the relations between the logical layer (data models, workflow, rules) and the semantic layer (governance repository) is synchronized. All properties existing at the level of the logical data model are reused to provide a first level of the documentation automatically.

Operations

• Create all Administrated Items.

• Delete all Administered Items.

• Refresh all Administered Items.

• Validate all Administered Items.

• Delete Administered Items recursively.

• Delete Administered Items with no data reference recursively.

Extended information management

• 'Party management' to connect any type of party to an Administered Item. Any party can be configured to play any type of role.

• 'Classification management'. Any type of classification scheme can be used to arrange the Administered Items by taxonomy.

• 'Relation management'. Any type of relationship between the Administered Items. The 'Contains' relationship is automatically created between the Administrated Item that already have a structural relationship defined in the logical data model (e.g. fields belonging to a table).