Release Notes | Release 2.2.3
Overview
Welcome to Semarchy Convergence for MDM!
This document provides the latest information about this Semarchy Convergence Release, including new features and bug fixes.
Contents
- Release Notes | Release 2.2.3
- Overview
- Contents
- New Features in Version 2.2
- Redesigned Master Data Governance Experience
- Clarity
- Efficiency
- Comfort
- Interactive and Safe Data Authoring
- Interactive Data Augmentation and Validation
- Pro-active Duplicates and Unique Keys Detection
- Concurrent Change Detection
- Design-Time Enhancements
- Workflow Design Productivity
- Filters on Child Records
- Export/Import Models Everywhere
- New Plug-in: Text Normalization and Transliteration
- Other Changes
- Design-Time
- Administration
- Deployment
- New Features in Version 2.1
- Overview
- Detailed Features
- Entity Matching Behavior
- Automated ID Generation
- Error Processing Workflows
- Improved Experience for Data Authoring and Stewardship
- Quick Records Check out
- Workflow Data Validation
- Improved Data Import/Export in Excel and CSV
- Retention Policies and Scheduled Purges
- New Features in Version 2.0
- Major Features
- Support for High-Availability Deployment
- Display Components
- Row-Level Security
- Model Variables
- Model Documentation
- Client API
- Other Changes
- Administration
- Deployment
- Integration
- Change Log
- Version 2.0.1.
- Version 2.0.2
- Version 2.0.3
- Version 2.0.4
- Version 2.0.5
- Version 2.0.6
- Version 2.1.0
- Version 2.1.1
- Version 2.2.0
- Known Issues
- New Features
- Bug Fixes
- Version 2.2.1
- New Features
- Bug Fixes
- Version 2.2.2
- Known Issues
- Bug Fixes
- Version 2.2.3
- Known Issues
- New Features
- Bug Fixes
New Features in Version 2.2
Semarchy Convergence for MDM 2.2 brings master data governance to the next level by introducing a redesigned user experience with enhanced interactivity.
Redesigned Master Data Governance Experience
Convergence for MDM introduces a redesigned interface for business users and data stewards exercising master data governance.
This user interface is separated from the design-time workbench and provides simplified and powerful access to the master data. It has been enhanced in the following areas:
Clarity
- An updated Home page with shortcuts to workflows
- A simplified layout showing only relevant content and options
- Simplified forms and editors
- An issue detection report showing all data issues (data validations, duplicates, concurrent changes ) in a single place, with the capability to export the issue report.
Efficiency
- A reorganized navigation panel
- Quick Search to find any piece of data at any time
- Consistently reorganized actions
- Direct activity actions to claim, un-claim, or complete a task in a single step
- Direct duplicate management actions (merge, split, etc.) from the data lists and tree view
- Direct data editing actions from the data lists and tree view
Comfort
- URLs to directly access applications and data editions
- Support for multiple browser tabs
- An elegant theme with an improved icon set
With no additional design-time effort, this new simple, fast and elegant interface is available from your Convergence for MDM instance on the /data path.
Interactive and Safe Data Authoring
Convergence for MDM 2.2 adds new benefits for users authoring data in the hub: data entry is made simpler, faster and safer.
Interactive Data Augmentation and Validation
With this feature, developers can define enrichers and validations triggered on workflow tasks and transitions. Resulting workflows deliver more interactivity to the business users and data stewards authoring master data in the hub:
- Enrichers are triggered from data entry forms, automatically augmenting input fields or filling in computed fields. At the same time, validations pro-actively notify users of possible data issues. All this happens interactively while the user enters keystrokes or moves from field to field.
- When the user completes a workflow task, enrichers and validations are automatically triggered to enforce data quality policies. Issues detected are reported as simple warning messages or may be configured to block the user from completing the task.
Developers can configure enrichers and validations from the Properties view for tasks and transitions in the Workflow diagram for data entry workflows.
Pro-active Duplicates and Unique Keys Detection
ID Matching entities, frequently used for data authoring patterns, now support duplicate and unique key violation detection within workflows:
- Developers can define matchers on ID Matching entities. Such matchers detect duplicates for a record while it is created.
- Unique Keys defined in the model on ID Matching entities are also checked in data entry workflows.
When a business user edits a record in a workflow, the interface warns him immediately if he is about to create:
- A record similar to one that already exists (according to the matcher), allowing him to check this record out and modify it instead of creating a duplicate.
- A record that violates a unique key definition.
Developers enable duplicate detection on ID Matching Entities by creating Matchers for these entities. Unique key validation is configured as a validation in a workflow task or transition.
Concurrent Change Detection
Data being processed in an activity may become out of sync if the original record is modified by another human workflow or by a publishing process.
Such concurrent change is now automatically detected in the workflows. A warning is raised to the user working on the out-of-sync data, allowing him to ignore or merge these changes into his data transaction.
Concurrent changes are automatically detected and raised as needed when processing data entry workflows.
Design-Time Enhancements
Designers benefit from the productivity features of Convergence for MDM 2.2 to deliver faster iterations for their MDM initiatives.
Workflow Design Productivity
The workflow design has been enhanced with capabilities to support not only Interactive Data Augmentation and Validation, but also with the ability to add Customized Labels on transitions.
The design-time workflow editor now includes a Properties view. Using this view, developers can modify tasks and transitions without leaving the diagram, enhancing their productivity in workflow design.
Filters on Child Records
SemQL has been enhanced to support conditions based on child records.
For example, if a Customer has several Contacts, you can now easily design filters involving the customers' contacts:
- Customers with at least one contact.:
ANY contacts HAVE (1=1)
- Customers with all contacts without email.
ALL contacts HAVE (email IS NULL)
- Customers with contacts located in a different country than the customer:
ANY contacts HAVE (country != customer.country)
The new ANY/ALL syntax is available from the Expression Editor. For more information, see the new "Semarchy Convergence for MDM SemQL Guide" available in the documentation library.
Export/Import Models Everywhere
Model edition export is now allowed from deployment repositories. With this option, administrators can transfer models as they were originally deployed between test/UAT and production environments.
Model edition import is now possible to development repositories. Import closed or open model editions either as new models, or on top of open model editions.
Using this feature, developers can transfer models across repositories at design-time with a just few clicks.
New Plug-in: Text Normalization and Transliteration
This new plugin applies normalization, transliteration (including Cyrillic, Arabic, Japanese and other eastern languages) and phonetic (metaphone, soundex, double metaphone, caverphone, refined soundex) transformations to text strings.
With this plug-in, the data certification process can transform international strings to a common standard, which makes fuzzy matching possible even for data published in different languages and character sets.
Other Changes
Design-Time
- Field-Level Consolidators using the Preferred Publishers strategy now have a Skip Null option.
- New golden record attributes: Masters Count stores the number of master records contributing to a golden and Is Confirmed indicates whether a user has validated the matching group.
Administration
- Web Services management is now attached to the Execution Engine platform privilege
- Notification Servers and Variable Value Providers management are now attached to the Data Location platform privilege.
Deployment
- Administrators can now close data editions with open workflows, and have these workflows continue in the new data edition.
- New closeAndCreateNewDataEdition web service to support Data Edition management automation.
- External Loads are no longer attached to a data edition:
- In the Data Locations editor, the Latest Loads are now under the data branch node, and no longer under each data edition.
- Loads start automatically on the latest edition of the data branch and the Data Edition ID is no longer needed to start a load.
- The new version 1.1 of the Integration Web Services is updated and the
dataEditionID
element is no longer needed for the getNewLoadID operation. - In the repository schema, the
MTA_GET_NEW_LOADID
, MTA_CANCEL_LOAD
and MTA_SUBMIT_LOAD
PL/SQL functions and procedures are deprecated (but still work) and replaced by the GET_NEW_LOADID
(this new function does not have a Data Edition ID parameter), SUBMIT_LOAD
functions and the CANCEL_LOAD
procedure in the INTEGRATION_LOAD
package.
- In the Activity web service, the
CompleteTask
request now requires a transition name (TransitionName) instead of a task name (TransitionTaskName is deprecated). Existing workflows will work with the new web services as the upgrade names the transitions as their target tasks.
New Features in Version 2.1
Overview
Semarchy Convergence for MDM 2.1 introduces new features to make the life of business users and data stewards easier and more productive: As they browse the data, then can perform quick records checkouts and immediately start authoring and managing data in newly organized editors. While working on this data, which now can includes errors and rejects, the are assisted with features such as automated ID generation and inline and bulk data validation. They can also take advantage of the improved data import/export in Excel and CSV and work with their favorite data editor.
With this release, developers and administrators are also invited to use the new design options for entity matching behavior and create retention policies and scheduled purges to enforce data governance and compliance policies.
Detailed Features
Entity Matching Behavior
This release introduces a new naming convention for entity types that replaces the Primary Key Type (SDPK, UDPK).
Entities are now identified by their Matching Behavior:
- ID Matching (formerly known as UDPK): Records in entities using ID Matching are matched if they have the same ID. This matching behavior is well suited when there is a true unique identifier for all the applications communicating with the MDM hub and for simple Data Entry use cases.
- Fuzzy Matching (formerly known as SDPK): Records in entities using Fuzzy Matching are matched using a SemQL expression defined in a matcher.
The matching behavior is defined when creating the entity and is modified using the Alter Entity action.
Automated ID Generation
Entities Primary Keys (IDs) can now be automatically generated in the data entry forms. The method for generating IDs is configured in the entity definition and may use sequence or a built-in UUID generator.
This feature facilitates data authoring through applications for business users and data stewards and they no longer need to enter ID values.
Error Processing Workflows
Contributions via data entry workflows now include fixing rejects, in addition to authoring or modifying data.
Model designers can define whether golden data, master data and/or rejects can be brought into the workflow that they create.
Using this feature, data stewards can now address data issues detected in the golden data certification process using regular data manipulation workflows, which are managed in the Convergence for MDM platform.
Improved Experience for Data Authoring and Stewardship
The data entry and duplicate management activities are now made easier to use through subtle improvements of the data entry and duplicate management editors.
This includes a complete reorganization and renaming for the actions. The are now grouped in a single Actions menu. Users can flag frequently used actions as Quick Actions to make them available in the editor toolbar.
Quick Records Check out
Users can now quickly select and check out records as they browse them. This operation adds these records to an existing activity or creates a new activity with these records. This activity automatically opens and the user can immediately start working on these records.
With this feature, users can naturally and quickly trigger activities as they see the data, dramatically boosting their productivity.
Workflow Data Validation
Data modified or entered in the context of a data entry activities is now be validated at two levels:
- Form Data Validation: Within data entry forms, information not compliant with the data quality rules defined in the model is detected and errors are raised to the user.
- Bulk Data Validation: All the data modified or entered in the context of a data entry activity can be validated against the data certification rules in bulk using the new Validate action.
Using these two features, data authors can now pro-actively fix issues that may cause data rejection before saving each data record and before completing a task.
Improved Data Import/Export in Excel and CSV
The import/export feature available to extract data from the hub or bulk import data is now improved with the following capabilities:
- CSV Files Support: Data import and export now support CSV files in addition to Microsoft Excel workbooks.
- Reusable Import Settings: Import settings, including file format specification and columns to attributes mappings can be saved and reused for subsequent imports.
- Advanced Export Settings: The format of the exported files (list of values, references, complex attributes and header columns) can be customized through advanced options.
These new capabilities help business users and data stewards manage customized exports and import for data viewing and bulk changes.
Retention Policies and Scheduled Purges
Preserving the lineage and history of the golden data is a frequent master data governance and regulatory compliance requirement. To make sure that the data lineage and history are preserved according to the governance and compliance requirements, model designers can now define Data Retention Policies for the model and for individual entities.
For example:
- The hub is configured to retain no history at all. This is the general policy.
- Employee data is retained for 10 years.
- Product and Financial data is retained forever.
However, keeping this information may also create a large volume of data in the hub storage. To keep a reasonable volume of information, administrators can now schedule Purges for this data. These schedules are handled by a Purge Scheduler, accessible from the administration view. These purges respect the retention policies defined in the model design.
Retention policies and scheduled purges guarantee ease of administration, data volume control as well as compliance with data retention policies for regulatory compliance.
For more information about Retention Policies, see the "Defining Data Retention" chapter in the "Semarchy Convergence for MDM Developer’s Guide". For more information about purge scheduling, see the "Scheduling Data Purges" section in the "Semarchy Convergence for MDM Administration Guide".
New Features in Version 2.0
Major Features
Support for High-Availability Deployment
Convergence for MDM 2.0 supports the clustered deployment of the Convergence for MDM web application for high-availability and failover. A clustered deployment can be set up for example to support a large number of concurrent users performing data entry or duplicate management operation.
For more information, refer to the "High-Availability Configuration" section in the "Semarchy Convergence for MDM Installation Guide".
Display Components
The display of form and table view attributes can be configured by setting a Display Type and optionally the height and width of the display component. Display types allow including Embedded Content or URL, Images and Hyperlinks into the data access form and table views.
For more information, refer to the "Display Types" section in the "Semarchy Convergence for MDM Developer’s Guide".
Row-Level Security
Convergence for MDM 2.0 introduces a new level of details for securing data access.
It is possible to define SemQL Filters for the entities in a Model Privilege Grant. This filter will make accessible only the filtered records for the user having this role. Using filters, model designer can choose to restrict the access to specific entity records depending on the roles.
For more information, refer to the "Securing Data" chapter in the "Semarchy Convergence for MDM Developer’s Guide".
Model Variables
Model Variables can be defined in the model, these variables' values are refreshed from a query to an external provider. The Variable Value Providers, defined in the Administration Console perspective, can be either an LDAP-compatible directory or a database connected via a JDBC Datasource.
Variable values are refreshed when a user connects to access the hub data, and are local to this user’s session. The variable can be used for example in the filters defined for row-level security.
For more information, refer to the "Model Variables" section in the "Semarchy Convergence for MDM Developer’s Guide" and the "Configuring Variable Value Providers" section in the "Semarchy Convergence for MDM Administration Guide"
Model Documentation
Convergence 2.0 introduces a new feature to generate a model documentation set in HTML format.
This documentation set includes the Logical Model, Applications and Physical Model documentation.
For more information, refer to the "Generating the Model Documentation" section in the "Semarchy Convergence for MDM Developer’s Guide".
Client API
A new client API is available to design and develop customized user interfaces to:
- Explore the structure (metadata) of the MDM hub content.
- Access the data stored in the MDM Hub,
- Interact with the workflows
This API is available in the semarchy-mdm-client-<version tag>.zip
file with documentation and samples.
Other Changes
Administration
- The Plug-ins editor now shows only plug-ins added by the user and supports plug-in removal.
- Plug-ins added by the user are stored in the repository and not deleted when re-deploying the application in some application servers (Tomcat).
- New Include Model Edition in Namespace option in the Web Service Manager.
- Batch Poller frequency is now configured by default to 10 seconds.
- Auto-start preferences for the web services are lost in the upgrade process and must be reset.
Deployment
- It is possible switch the deployed model edition of a given data edition without closing and opening a new data edition. Switching a model edition preserves the old version of the jobs under a Deprecated Jobs node.
- Data edition Closing mode is now called Maintenance mode.
Integration
- The following table structure changes must be taken into account in the integration flows targeting the MDM hub:
- In the
SD_
tables, the B_BATCHID
column no longer exists. - In the
SD_
tables, the B_BRANCHID
column is mandatory and must be loaded with the data branch ID.
- New/updated web service in this release:
- Platform Services > Metadata Web Service, for the client API.
- Data Services now expose two new WDSL per data edition: ActivityService and GenericDataService. See the "Convergence for MDM Integration Guide" for more information.
Change Log
Version 2.0.1.
- 590 – The popup window for an image attribute does not preserve the aspect ratio
- 595 – Missing Dependency Error when installing the Semarchy Plugin SDK 2.0.0
- 596 – Attribute names in a form view are incorrect for the attributes of a parent entity.
- 597 – MTA_SUBMIT_LOAD to submit Deprecated Jobs causes an ORA-01422 Error
- 600 - “RuntimeException: Cannot update a deployed Model Edition in a production environment.” on Install Model Edition in Repository with DEPLOYMENT type
- 604 – Tomcat Server does not shut down if a session is running
- 605 – OutOfMemory PermGen Space error when validating a model
- 607 – Button requires a double-click to open the SemQL editor (Enricher and Binning Expression)
Version 2.0.2
- 87 – Contextual menu is empty on the model edition tree view after a validate action
- 125 – Non admin users connecting while the repository is down have no privileges until they logout and login again
- 423 – Update to the workflow notification message and subject
- 433 – Editor toolbars stop working after perspective switching
- 442 – Notification Servers: wizard should automatically set first server as default
- 470 – Improved user experience when upgrading a model edition to fix a job that failed
- 472 – Job Logs view allows deleting running Jobs
- 498 – Validator for Plugin should raise warning when some input/outputs are not mapped but enricher/validation is disabled
- 499 – Model Validation should raise a warning when an entity is not processed by any job
- 507 – Right-click Validate should put the focus back on the Progress Editor
- 550 – Fonts used are now suitable for Linux, Mac and Windows
- 562 – Columns displayed in duplicate management workflows' tables are persisted in the user preferences
- 598 – Job are not ordered correctly under the data location tree
- 599 – Model Edition Import Wizard should refresh the Model Edition tree after import
- 611 – LOV import from excel imports formula text instead of formula result
- 613 – Validator now prevents using Large Objects (LOB) attributes in entity or complex type subject names
- 615 – Duplicate Management workflows: The treeview status (expanded) is lost when any action is done
- 616 – Error ORA-00904: “GD”.“FS_XXX” when starting a data entry workflow with a UDPK entity referencing a SDPK entity
- 618 – Excel Import Wizard: Added a progress bar during the file processing
- 626 – NullPointerException error when an importing Excel data with rows containing only blank cells with formatting info
Version 2.0.3
- 636 – Data Entry: Unable to create a child record if parent entity is inherited
- 637 – Missing Validator for a Record Level Consolidator with Publisher Ranking and no Publisher in the List
- 642 – GD analyze statistics analyzes the wrong table (MD)
- 643 – In the Reference creation wizard a whitespace in the physical name causes an error flag that never disappears
- 644 – Error "This binding expression “S.B_LOADID” is not present in this row" in data entry workflows when entering a new record with a row filter on the entity
- 653 – Convergence Plugin SDK is now signed
- 654 – Home Dashboard has an incorrect scrolling behavior
- 661 – Attribute Group Namespace is incorrectly checked. Namespace should be across entity inheritance hierarchy
- 662 – Support inherited entities in data entry workflows
- 663 – Entities are not ordered in the Job Creation Wizard
- 664 – Publisher code is now autofilled in uppercase in the publisher creation wizard
- 666 – On BO Views, search is not persisted when using the “Back” button
- 672 – Validation does not raise any issue for form views with no attributes
- 673 – Importing of large Excel file cause the application to become unresponsive
- 677 – Data Entry usability improvements for dates: display a format hint and a decorator for invalid values
- 678 – Data Entry: ClassCastException when displaying a record with invalid Multi-LOV values in a table view
- 696 – Date picker displays date format helper message and picker button even for read only fields
Version 2.0.4
- 704 – Incorrect French translation “La ClĂ© de Licence est invalide” when registering a valid license key
- 706 – Excel Import Fails with Empty Cell
- 702 – Error when importing Excel an worksheet with cells containing formulas returning error values
- 700 – IE9/IE10 is unable to display HTML object type "image/png"
- 712 – Excel Import adds “.0” to a numeric cell value imported in a string attribute
- 715 – java.lang.IndexOutOfBoundsException in the Excel Import wizard when previewing a different worksheet with a larger number of columns
Version 2.0.5
- 721 – Model Import on in a production repository fails
Version 2.0.6
- 724 – New applications do not appear after moving a model to production
Version 2.1.0
- 432 – Count query to display the total number of rows in tables are computed on demand
- 471 – New Batch Poller option “Plugin Tasks Feedback Interval” defines row count refresh interval for long running plugin tasks
- 520 – Session Timeout Window has a broken layout
- 572 – Refresh button in Data Entry View does not correctly refresh the table content
- 586 – Semarchy workbench incorrectly freezes on “Loading” page if the repository database is unavailable.
- 609 – No scrollbar on the workflow editor with small browser windows
- 612 – Excel Import resolves formulas while importing data
- 620 – Excel import mapping suggestion is not case insensitive
- 625 – A new dialog show the number of records imported successfully or failed
- 641 – Scripts in the bin folder do not have execution permission on after uncompressing the distribution
- 655 – The initial focus is not correctly set in the wizards with Firefox
- 658 – Home Dashboard fails to load with a DataAccessPermissionDenied exception if user has row-level security defined
- 684 – Certain actions are incorrectly enabled for multiple-selections in the duplicate management editor
- 686 – Dialog for selecting candidate values (for example in a filter) incorrectly allows multiple values selection
- 692 - “ORA-00001: unique constraint (XXX) violated” if the same complex type is used twice in the same entity and if both attribute are in error.
- 693 – A value selected in the selection dialog is ignored for Date types in criteria filter definition
- 695 - “Finish” button is now disabled on the first page of the Open Data Edition wizard
- 697 – A zero rows sample raises an exception when clicking Next in the Excel Import Wizard
- 698 – Export button should be disabled when list of records is empty
- 701 – Default validation is now pre-consolidation for newly created validation elements
- 705 – Reference validation scope is not exported in Model Documentation export for References that are not mandatory
- 707 – Excel Import fails with an Excel file with lines that have been emptied.
- 716 – Incorrect display type used for complex attribute’s definition attributes in form and tables views.
- 718 - “ORA-30926: unable to get a stable set of rows in the source tables” error occurs on the “Consolidate singleton master records into GI table” task.
- 727 – Erratic layout behavior of the sections in the Home Dashboard
- 730 – Folder Names instead of labels incorrectly shown in the model tree view
- 739 – Getting Started Actions are now hidden if user does not have the semadmin role
- 740 – Changing the name of an object does not change the editor’s tab label
- 741 – It is no longer possible to remove all the displayed columns from a data table
- 743 – Business Object Views are not ordered alphabetically by label in the Structure of a Data Entry Activity
- 746 – New Display Format and Export Format options for List of Values in User Preferences and Export Dialog
- 747 – Integration Job incorrectly validates mandatory attributes existing only in child entities (inheritance)
- 749 – Better error message when a multi-LOV value cannot be stored due to the attribute size
- 750 – Missing Remove button for Embedded Content display type during Data Entry
- 754 – Image are displayed too large in the Data Entry activity table
- 756 – Wrong label for BO views selection step in the Data Entry workflow creation wizard
- 776 – Invalid SQL generated when using BETWEEN in SemQL
- 787 – Job Remains Running after a repository crash
Version 2.1.1
- 898 – Fixed slower opening of data editions in 2.1 compared to 2.0
- 889 – Submitting a workflow while a record is displayed in a form view generates an AssertionFailedException
- 888 – A model validation is added to have at least one output for plug-in enrichers
- 895 – End of record error with CSV files
- 906 – Filters do not seem to apply correctly to data editors opened twice
- 896 – Editable table cells containing SemQL expressions incorrectly keep the focus on exit
- 890 – Documentation export on a model using inheritance and attribute privileges generates an IllegalArgumentException
- 905 – The overview page does not appear when the engine is stopped
- 892 - “AssertionFailedException: assertion failed: Getter called on disposed observable” is logged when closing a data editor
- 891 – A NullPointerException appears when checking rejects out if the table view contains attributes using SemQL expressions
Version 2.2.0
Known Issues
- MDM-1298 - [Weblogic 12] 403 error page is not displayed when user is not authorized
- MDM-1201 – Incorrect Mixed Content Warning in IE8 with HTTPS Configuration (IE Bug)
New Features
- MDM-970 – Support Filters on the Many relationships
- MDM-971 – Support for enrichers and validations in task and transition in data entry workflows
- MDM-975 – Support for BO Views defined at task level for data entry workflows.
- MDM-1000 – Design time Import/Export of Model Edition
- MDM-1041 – BO View display order can be defined for data entry workflows.
- MDM-1083 – Automated ID generation in Data Entry for Fuzzy Matching Entities
- MDM-1110 – Support export from Deployment repository
- MDM-1140 – Add Masters Count on Golden Records
- MDM-1141 – Add a new attribute on Golden records to tell whether Golden Is Confirmed or not
- MDM-1144 – Closing and creation new data editions should keep running workflows and loads
- MDM-1146 – New Web Service to Close and Create a New Data Edition
- MDM-1213 – New xframeoptions context parameter (web.xml/semarchy.xml) to configure iframe embeddability (X-Frame-Options)
- MDM-290 – Web Service Administration is now attached to the Execution Engine Privilege, and the Notification Servers to the Data Location Privileges.
- MDM-847 – Improved user feedback when using reserved names for attributes
- MDM-870 – Support for Browser Multi-Tab
- MDM-1126 – First Form/Table View created for an entity is called “DefaultFormView/DefaultTableView” by default
Bug Fixes
- MDM-622 – Search/filter is not persisted when using the “Back” button on BO Views
- MDM-743 – New option for default Data Import settings
- MDM-746 – Data Import: Date and DateTime format preferences do not have default values
- MDM-756 – New Warning in model validation if an integration job has a possible wrong order in tasks
- MDM-796 – Sequences might not be ordered sequentially when using RAC
- MDM-840 - [Address Enricher] OnDemand mode doesn’t work anymore
- MDM-850 – In data import, if no PK is defined in the form view, the mapping is impossible
- MDM-860 – Incorrect attributes order in attribute picker: foreign attribute is always listed at the end
- MDM-863 – Setting an empty field separator in data import wizard hangs preview and allows the Next button
- MDM-864 – Display types not used in record checkout tables view
- MDM-866 – Refresh Button does not work on a BO View after it was modified in data entry
- MDM-867 – Session ending do not redirected to the login screen on Internet Explorer
- MDM-868 – Data Import Fails if the option “The imported file contains an ID column” is selected and the form view does not contain SourceID or the preferences reference obsolete attributes
- MDM-873 – Incorrect ordering of the BO Views in the hierarchy of the data entry editor
- MDM-874 – Data Entry raises a “Not Yet Implemented” exception when there is a unique key check marked as "pre-consolidation"
- MDM-875 – LOVs contained in Complex Types do not appear according to the “LOV Display Format” Preference
- MDM-1162 – Data export fails when a Form Attribute is an expression
- MDM-1191 – HTTP Status 408 Error when accessing the login page
- MDM-1192 – Checking out a record already checked out does not refresh the record from the hub
- MDM-1196 – Duplicate Management Checkout filter expression editor warns when an unknown function is used
- MDM-1198 – Link to a Grand-Parent FDN causes an "Unhandled event loop exception"
- MDM-1275 - [Weblogic 12c] Data UI cannot be opened and Data Edition Web services cannot be started (Issue with JAXB)
- MDM-1276 - [Weblogic 12c] Error 404 when accessing http://host:port/semarchy instead of http://host:port/semarchy/
- MDM-1295 – Unable to the Email of a Role in the Administration Console
- MDM-1317 – Incorrect definition for the entity “Remove” privilege indicated in the Administration Guide
- MDM-1326 – NullPointerException and Action buttons disappear when clicking record with specific record level privileges defined
- MDM-1329 – SQL Query Generation generates aliases containing reserved keywords
- MDM-1330 – Data Import now handles files with a large number of columns detected due to incorrect separator definition
- MDM-1331 – Embedded content in form views does not display correctly in Internet Explorer
- MDM-1335 – Checking-out a cluster of objects containing a child with no privileges is enabled but causes an exception.
- MDM-1383 – Export Menu appears even without export privilege on entity
Version 2.2.1
New Features
- MDM-58 – Excel and CSV export limits can be configured from the Administration Console.
- MDM-664 – Email Enricher now provides an Offline mode.
- MDM-846 – Purge Scheduler wizard and editor: Schedule definition interface review.
- MDM-1012 – Google Maps Plug-in now supports Client ID and Key.
- MDM-1161 – DataSource Value Provider now supports JDBC datasource selection in a dropdown component.
- MDM-1301 – New Microsoft Bing Maps plug-in for address enrichment
- MDM-1340 – Enricher’s “Active” property label is renamed to “Run in Jobs”.
- MDM-1377 – Editable state of the Source ID field is made more obvious in data entry forms.
- MDM-1389 – Engine Administration: “Ignore Failure” action is renamed to “Cancel Job”.
- MDM-1392 – Convergence for MDM is now certified on Glassfish 4.0.
- MDM-1403 – Reviewed title and button labels for the “Open Data Edition” dialog.
- MDM-1437 – Convergence For MDM is now certified on non-CDB Oracle 12c instances.
- MDM-1438 – Convergence For MDM is now certified on Tomcat 8 and Wildfly 8. Dropped support for JBoss 5.x.
- MDM-1455 – MDM Applications Logo can be customized from the Administration Console.
- MDM-1467 – Date management is now consistently based on the application server time zone.
- MDM-1477 – Workbench and Applications URLs changed to /semarchy/workbench and /semarchy/data.
- MDM-1478 – Added a view action when browsing BO View records.
- MDM-1479 – Added Start/End/Duration values to the Data Certification Queue page.
- MDM-1480 – New Welcome Page for /semarchy.
Bug Fixes
- MDM-710 – Overview page not correctly refreshed when a data location upgrade fails.
- MDM-1343 – Data location upgrade now fails with an appropriate message if the model edition has validation errors.
- MDM-1359 – Data location’s datasource selection drop-down misses certain datasources if some of them are invalid.
- MDM-1369 – Activity task overview in the applications does not have enough space for activity diagram.
- MDM-1404 – Cryptic warning message during checkout is now removed "One or more records in the hierarchy to check out already exist in Data Entry publisher Product Hub Data Entry. If you proceed, those Data Entry records..."
- MDM-1426 – Missing Scrollbar on Home Page’s “Navigate” view.
- MDM-1428 – In the data entry forms, the Save button is now disabled if errors prevent from saving the record.
- MDM-1429 – In data entry forms, attributes with embedded content display type are displayed twice.
- MDM-1434 – Client API method completionResult.getNewTask() returns null value.
- MDM-1435 – Attribute with Image Display Type is not updated when using Previous/Next record if new record contains null image.
- MDM-1456 – Character “&” disappears from labels coming from Model Design.
- MDM-1462 – Paginated Queries are too slow due to wrong pagination query.
- MDM-1468 – Import (Exact ID Matching/ID generated) fails with “could not find row with ID xxx from hub” when record exists only with non data entry publisher id in hub.
- MDM-1471 – Missing Horizontal Scrollbars in Form Editor.
- MDM-1472 – Data entry Enricher on Field Exit is not triggered when exiting a LOV field.
- MDM-1482 – Exporting Documentation should raise an error for an invalid model.
- MDM-1484 – REGEXP_SUBSTR Syntax misses subexpr parameter.
- MDM-1486 – Multiple malfunctions with the Refresh button of the Validation report.
- MDM-1487 – SemQL does not support CURRENT_TIMESTAMP() without precision.
Version 2.2.2
Known Issues
- MDM-1463 – Geronimo 3.0.1 and WebSphere Liberty Profile 8.5 are not supported due to classloading incompatibility.
- MDM-1393 – Data export (XLSX) opens in Excel 2010 with hidden columns. This problem is due to a JVM versions 1.7.0_21. To solve it, upgrade to a later JVM Version.
- MDM-1386 - Fuzzy Matching Entities with a single attribute are not correctly handled by the integration process. These entities can be used for inheritance purposes.
Bug Fixes
- MDM-1509 – The Welcome page raises a HTTP-500 error when a model is not valid.
- MDM-1508 – Upgrading to version 2.2 generates invalid validation configuration errors on data entry workflows.
Version 2.2.3
Known Issues
- MDM-1463 – Geronimo 3.0.1 and WebSphere Liberty Profile 8.5 are not supported due to classloading incompatibility.
- MDM-1393 – Data export (XLSX) opens in Excel 2010 with hidden columns. This problem is due to a JVM versions 1.7.0_21. To solve it, upgrade to a later JVM Version.
- MDM-1386 - Fuzzy Matching Entities with a single attribute are not correctly handled by the integration process. These entities can be used for inheritance purposes.
New Features
- MDM-1597 – Field Level Consolidation performance improved when using the Preferred Publisher (with Skip Null options), Largest or Smallest Value consolidation strategies.
- MDM-1577 – Google Maps Plugin Enricher uses the system proxy configuration specified with -Dhttp.proxy and -Dhttp.port.
- MDM-1553 – Matching performance improvement for the “Assigned SDPK to integration table for detected duplicates” task.
Bug Fixes
- MDM-1617 – NullPointerException when using the Google Maps Enricher with empty parameters.
- MDM-1595 – Upgrading no longer automatically activates the Skip Nulls option in Field Level Consolidators using the Preferred Publisher strategy.
- MDM-1582 – Business object views selection wizard on data entry task wizard looses the existing business object views order.
- MDM-1545 – Model validation fails after an upgrade if workflows have been removed between model editions.
- MDM-1530 – Model validation fails after an upgrade to version 2.2 when an entity is refereced several times from the same workflow.
- MDM-1491 - “IllegalArgumentException: Argument cannot be null” error appears when accessing the Dashboard. This error occurs when an integration batch has no attached job log.