TIBCO® MDM Release Notes
Software Release 9.0.0 December 2015
Two-Second Advantage® 2
Important Information
SOME TIBCO SOFTWARE EMBEDS OR BUNDLES OTHER TIBCO SOFTWARE. USE OF SUCH EMBEDDED OR BUNDLED TIBCO SOFTWARE IS SOLELY TO ENABLE THE FUNCTIONALITY (OR PROVIDE LIMITED ADD-ON FUNCTIONALITY) OF THE LICENSED TIBCO SOFTWARE. THE EMBEDDED OR BUNDLED SOFTWARE IS NOT LICENSED TO BE USED OR ACCESSED BY ANY OTHER TIBCO SOFTWARE OR FOR ANY OTHER PURPOSE. USE OF TIBCO SOFTWARE AND THIS DOCUMENT IS SUBJECT TO THE TERMS AND CONDITIONS OF A LICENSE AGREEMENT FOUND IN EITHER A SEPARATELY EXECUTED SOFTWARE LICENSE AGREEMENT, OR, IF THERE IS NO SUCH SEPARATE AGREEMENT, THE CLICKWRAP END USER LICENSE AGREEMENT WHICH IS DISPLAYED DURING DOWNLOAD OR INSTALLATION OF THE SOFTWARE (AND WHICH IS DUPLICATED IN THE LICENSE FILE) OR IF THERE IS NO SUCH SOFTWARE LICENSE AGREEMENT OR CLICKWRAP END USER LICENSE AGREEMENT, THE LICENSE(S) LOCATED IN THE “LICENSE” FILE(S) OF THE SOFTWARE. USE OF THIS DOCUMENT IS SUBJECT TO THOSE TERMS AND CONDITIONS, AND YOUR USE HEREOF SHALL CONSTITUTE ACCEPTANCE OF AND AN AGREEMENT TO BE BOUND BY THE SAME. This document contains confidential information that is subject to U.S. and international copyright laws and treaties. No part of this document may be reproduced in any form without the written authorization of TIBCO Software Inc. TIBCO and Two-Second Advantage are either registered trademarks or trademarks of TIBCO Software Inc. in the United States and/or other countries. Enterprise Java Beans (EJB), Java Platform Enterprise Edition (Java EE), Java 2 Platform Enterprise Edition (J2EE), and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle Corporation in the U.S. and other countries. All other product and company names and marks mentioned in this document are the property of their respective owners and are mentioned for identification purposes only. THIS SOFTWARE MAY BE AVAILABLE ON MULTIPLE OPERATING SYSTEMS. HOWEVER, NOT ALL OPERATING SYSTEM PLATFORMS FOR A SPECIFIC SOFTWARE VERSION ARE RELEASED AT THE SAME TIME. SEE THE README FILE FOR THE AVAILABILITY OF THIS SOFTWARE VERSION ON A SPECIFIC OPERATING SYSTEM PLATFORM. THIS DOCUMENT IS PROVIDED “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. THIS DOCUMENT COULD INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS. CHANGES ARE PERIODICALLY ADDED TO THE INFORMATION HEREIN; THESE CHANGES WILL BE INCORPORATED IN NEW EDITIONS OF THIS DOCUMENT. TIBCO SOFTWARE INC. MAY MAKE IMPROVEMENTS AND/OR CHANGES IN THE PRODUCT(S) AND/OR THE PROGRAM(S) DESCRIBED IN THIS DOCUMENT AT ANY TIME. THE CONTENTS OF THIS DOCUMENT MAY BE MODIFIED AND/OR QUALIFIED, DIRECTLY OR INDIRECTLY, BY OTHER DOCUMENTATION WHICH ACCOMPANIES THIS SOFTWARE, INCLUDING BUT NOT LIMITED TO ANY RELEASE NOTES AND "READ ME" FILES. Copyright © 2010-2016 TIBCO Software Inc. All rights reserved. TIBCO Software Inc. Confidential Information
TIBCO® MDM Release Notes 3
Contents
TIBCO Documentation and Support Services ...... 4 New Features ...... 5 Changes in Functionality ...... 18 Deprecated and Removed Features ...... 19 Migration and Compatibility ...... 22 Closed Issues ...... 24 Known Issues ...... 56
TIBCO® MDM Release Notes 4
TIBCO Documentation and Support Services
Documentation for this and other TIBCO products is available on the TIBCO Documentation site: https://docs.tibco.com Documentation on the TIBCO Documentation site is updated more frequently than any documentation that might be included with the product. To ensure that you are accessing the latest available help topics, please visit https://docs.tibco.com.
Product-Specific Documentation
Documentation for TIBCO products is not bundled with the software. Instead, it is available on the TIBCO Documentation site. To directly access the documentation for this product, double-click the following file:
TIBCO_HOME/release_notes/TIB_mdm_version_docinfo.html where TIBCO_HOME is the top-level directory in which TIBCO products are installed. On Windows, the default TIBCO_HOME is C:\tibco. On UNIX systems, the default TIBCO_HOME is /opt/tibco. The following documents for this product can be found on the TIBCO Documentation site:
● TIBCO MDM Release Notes ● TIBCO MDM Installation and Configuration Guide ● TIBCO MDM User’s Guide ● TIBCO MDM System Administration ● TIBCO MDM Customization Guide ● TIBCO MDM Workflow Reference ● TIBCO MDM Web Services Guide ● JAVA API Reference ● TIBCO MDM Best Practices Guide ● TIBCO MDM Performance Tuning Guide
How to Contact TIBCO Support
For comments or problems with this manual or the software it addresses, contact TIBCO Support:
● For an overview of TIBCO Support, and information about getting started with TIBCO Support, visit this site: http://www.tibco.com/services/support
● If you already have a valid maintenance or support contract, visit this site: https://support.tibco.com Entry to this site requires a user name and password. If you do not have a user name, you can request one.
How to Join TIBCOmmunity
TIBCOmmunity is an online destination for TIBCO customers, partners, and resident experts. It is a place to share and access the collective experience of the TIBCO community. TIBCOmmunity offers forums, blogs, and access to a variety of resources. To register, go to the following web address: https://www.tibcommunity.com
TIBCO® MDM Release Notes 5
New Features
The following new features have been added to version 9.0.0 of TIBCO MDM. Interactive Installation To install TIBCO MDM on any specific installation combination, you may need to refer to multiple chapters and sections of the TIBCO MDM Installation and Configuration Guide. This is a time- consuming process and sometimes, causes installation and configuration issues. For user-friendly and hassle-free installation and to resolve the installation and configuration issues, an interactive installation is introduced in the TIBCO MDM Installation and Configuration Guide. Using the interactive installation, you can select your choice of application server, database, messaging server, and web server. On selecting, a list of topics is displayed. Using this list, you can install TIBCO MDM in one go. To use interactive installation, refer to the Web Help of the TIBCO MDM Installation and Configuration Guide on https://docs.tibco.com. Limitation : Interactive installation does not work in the PDF output and in the offline mode. To know about the offline mode, refer to the section "Setting Configuration for Decoupling of Documentation", in the TIBCO MDM Installation and Configuration Guide.
Data Quality Data quality now has the option to manually merge, multi merge, and merge through a web service. The joined tables feature of TIBCO Patterns has also been integrated into data quality. Using the joined tables feature to do a joined search eliminates the issues with denormalization and merging of separate query results. With this feature, you can search data spread across multiple tables in a way that the fields of each table appear to be merged into a single table while still being managed separately. A new match and merge user interface is available, which exposes the new features to the end user, as well as simplifies the merge process. Furthermore, using this feature, you can manually edit the merged record values. For information regarding manual merge, multi merge, and TIBCO Patterns joins, refer to the following sections in the "Setting Up Data Quality Process" chapter in the TIBCO MDM Customization Guide:
● ManualMerge
● Patterns Joins
● MultiMerge
For information on merging a record through web service, refer to the following sections in the TIBCO MDM Web Services Guide:
● Merge Record Service
● Merge Record Service Samples
● Merge Record Service Inputs
Synchronization Enhancements The following synchronization features are introduced to improve the synchronization process, activities, and performance in general:
● Support for related output maps in self and reverse relationships
● Relationships from either output maps or perspective are considered for publishing
TIBCO® MDM Release Notes 6
The earlier way of specifying the relationships in the wfin26catsyncv7.xml workflow is no more supported. For information on these features, refer to the TIBCO MDM User's Guide.
● Synchronization Enhancements on the UI: The following new options are available on the Create Synchronization Profile screen:
— Incremental Bundle Option
— Skip Identity Protocol Operations
For information on these options, refer to the "Creating a Synchronization Profile" section in the TIBCO MDM User Guide.
● Synchronization Enhancements in Workflow Activities:
— The synchronization workflow file wfin26catsynchv7.xml is modified to skip the IdentifyProtocolOperations activity, improve the performance, and avoid the generation of product logs, which are rarely used during the local publish.
Perspective Enhancements
● Perspective Enhancements on the UI: Perspectives can now be defined with attribute granularity, exposing only a limited subset of attributes in each repository if so designed. You can view a subset of relationship, repository attributes and attribute groups, and relationship attributes by selecting a perspective. For more information, refer to the section "Browsing Perspective Based Records", in TIBCO MDM User's Guide.
● Perspective Enhancements in Workflow Activities: the PerspectiveName input parameter is added in the following workflow activities to pass the perspective instead of relationships:
— CreateWorkItem
— DeleteRecord
— EvaluateRuleBase
— EvaluateSubset
— GetRecord
— ManageRecordCollection
— SaveRecord
— SpawnWorkflow
For information on the PerspectiveName parameter, refer to the TIBCO MDM Workflow Reference.
● Perspective Enhancements in Web Services: the web service query call can now be used to retrieve only a small subset of data using a perspective. The PERSPECTIVENAME context variable is added in the Record Add or Modify web service and the Record Query web service. For more information, refer to the sections "Record Add Modify Services - Inputs" and "Record Query Based On Perspectives" in TIBCO MDM Web Services Guide.
● Support for Perspective Cache: the PERSPECTIVE cache object is defined in the CacheConfig.xml file to cache the perspective data. For more information, refer to the following sections in the TIBCO MDM Installation and Configuration Guide:
— Perspective Space
— Cache Operation on Perspective
TIBCO® MDM Release Notes 7
— Perspective Cache Keys
Correction The correction feature is similar to the modification of the existing record, except that no new version is created. This can reduce the number of versions, reduce memory requirement on the database side, and eventually improve database query performance. Use this feature in the following scenarios:
● When the record goes through many changes in the workflow before it is published
● When version tracking is not needed
● Correction feature on UI: the Correction toolbar operation is available on the following screens:
— Browse and Search
— View Record
— Modify Record
— Work Item
— Text Search
For information on using the Correction operation, refer to the TIBCO MDM User's Guide.
● Resource Security Permission for Correction: the Correction operation is controlled with resource security permission. For information on the list of permissions, refer to the section "Permissions for Resource Type", in the TIBCO MDM User's Guide.
● Correction feature in Workflow Activities: the correction capability is available at the workflow activity level. The VersionPolicy parameter is added in the following workflow activities:
— ImportCatalogRecords
— EvaluateRulebase
— SaveRecord
For information on these activities, refer to the TIBCO MDM Workflow Reference.
● Correction feature in Web Services: the VERSION_POLICY context variable is added in the Record Add and Record Modify web services. For information, refer to the section, "Record Add Modify Services -Inputs" in the TIBCO MDM Web Services Guide.
● Correction feature in Rulebases: A new sub-action available in rulebase for the Correction operation. For more details on RECORD_ACTION, refer to the section "Context Variables", in the TIBCO MDM Studio Rulebase Designer User's Guide .
Scheduler UI The Scheduling menu is added in Configurator. Using this option, you can add, modify, run, and delete jobs. The jobs include FEDScheduler, PurgeRecordSynchLog, Purge History, and so on. For information on the scheduler UI, refer to the section, “Scheduling Jobs Using Configurator” in the TIBCO MDM System Administration.
Bundle Caching Bundle caching is introduced to load the full bundles into the cache and to get it retrieved from the cache instead of the database for the next use of the bundle. Currently, you can use bundle cache through web service queries, validations, and modifications. You can increase the performance for repeated operations.
TIBCO® MDM Release Notes 8
For more information, refer to the following sections in the TIBCO MDM Installation and Configuration Guide:
● Bundle Caching
● Bundle Cache Space
● Configuration Properties for Bundle Caching
All-in-One Installer The all-in-one installer is enhanced to include the following features:
● Create an enterprise and administrator credentials
● Select the data model template and add sample data
● Configure TIBCO Patterns
After finishing the installation, the MDM server, netrics server, and Configurator automatically starts, and now you can log in to TIBCO MDM. For information on installing TIBCO MDM using the all-in- one installer, refer to the section "Installing TIBCO MDM (Simple Installation)", in TIBCO MDM Installation and Configuration Guide.
Precedence Management Precedence Management has been implemented to process records based on different external sources. The precedence can be specified down to each attribute and has a concept of a data quality decay over time. You can accept quality data for each attribute supplied by a source. While accepting data, you can accept data only if the quality of the incoming data is better than what is existing, as long as precedence matrix is defined for the repository attribute. For information, refer to the "Precedence Management" section in the TIBCO MDM Customization Guide.
Rulebase Execution Optimization Rulebases can now be executed in parallel if the rulebase constraints do not have order dependencies. This requires designing the rulebases with additional indicators on whether a constraint can be executed in isolation. With Rulebase Execution Optimization, you have more control on the order of records processed and validation. Rather than processing all the records in the bundle in a serial order, you can process them in any desired order, so there is more control over the process order and what should be validated or not. By default, rulebase parallelization is enabled. Therefore, migrating customers must evaluate rule dependencies and add directives to have more control. For information, refer to the "Rulebase Properties" section in the TIBCO MDM Studio Rulebase Designer User's Guide.
Rollback of Event Rollback provides the option to roll back and restart the workflow from any point in the workflow using the Event log UI or the command-line utility. With rollback, you can roll back an event completely or up to any step of an event, so that the workflow can run again without being constrained by the changes done in the previous run. For information, refer to the "Rolling Back Events" section in the TIBCO MDM User's Guide and the "Rollback Event" section in the TIBCO MDM System Administration.
TIBCO® MDM Release Notes 9
Additional Data Types Two new predefined data types are introduced: Long and URL. For more information on the predefined data types, refer to the table "Data Types for Attributes", in the TIBCO MDM User's Guide.
Configurator Support for Language Pack The Language Pack Installer option is added in Configurator, using which you can install and uninstall the language pack. A language pack is a JAR file, which contains translations of the TIBCO MDM GUI in a specific language. To install the language pack, you must download the JAR file. For more information, refer to the following sections in the TIBCO MDM Installation and Configuration Guide:
● Support for Language Pack
● Installing Language Pack
● Uninstalling Language Pack
SQL Server 2012 Sequences Support The sequence feature of Microsoft SQL Server 2012 is implemented to create sequences as a part of seed data and migration script. This improves performance. This forces the removal of the Microsoft SQL Server 2008 support. For more information, refer to the sections "Creating Seed Data Manually for SQL Server Database" and "Premigration Steps", in the TIBCO MDM Installation and Configuration Guide.
Security with ActiveSpaces ActiveSpaces security is introduced to restrict connecting any unauthorized external node to another node if metaspace name or discovery URL is known. For more information, refer to the following sections in the TIBCO MDM Installation and Configuration Guide:
● AS-Agent Parameters
● ActiveSpaces Security
● Configuration Properties for ActiveSpaces Security
● Environment Variables for ActiveSpaces Security
● Starting MDM Node as Domain Controller
● Starting MDM Node as Domain Requestor
Command-line Interface You can call the TIBCO MDM classes through the command-line framework. You can execute management actions, such as cancel, resubmit, and restart through the command-line interface now. In previous versions, this could only be done from the UI. For more information, refer to the section “Command-Line Interface”, in the TIBCO MDM System Administration.
Process Record Service The Process Record web service is introduced to fire any named workflow to process records. For information on using this web service, refer to the following sections in the TIBCO MDM Web Services Guide:
● Process Records Service
● Process Record Service Samples
● Process Record Service Inputs
TIBCO® MDM Release Notes 10
● Resource Security Permission for Process Record web service: the resource security permission is defined for the Event resource type so that users can execute the web service. For information on the list of permissions, refer to the section, "Permissions for Resource Type" in the TIBCO MDM User's Guide.
Refresh Subset Activity The RefreshSubset workflow activity is introduced to refresh the selected records for a subset by list. For information on using this activity, refer to the following sections in the TIBCO MDM Workflow Reference :
● RefreshSubset Activity
● RefreshSubset Parameters and Valid Execution Modes
● Example for RefreshSubset Activity
Miscellaneous Enhancements The following table lists the miscellaneous enhancements that are added in the 9.0.0 release of TIBCO MDM:
Name Description Impact on Documentation
Cache Use cache computation to For more information, refer to the Computation suppress the auto cache section, "Cache Computation" in the calculation and to make the TIBCO MDM Installation and memory computation for cache Configuration Guide. easy.
Checkpointing Before firing the FireWorkflow For more information refer to the before activity, an implicit checkpoint sections, "FireWorkflow" and FireWorkflow ensures that the workflow is "CheckpointWorkflow" in the TIBCO committed before the activity. MDM Workflow Reference.
New workflow The following new types are for For more information, refer to the eval and new data the workflow parameter: following sections in the TIBCO types MDM Workflow Reference: ● file ● Parameter Definition ● date ● Parameter Types ● timestamp ● Parameter Evaluation The following values are for the eval attribute in the workflow parameter:
● event
● userprofile
● system
TIBCO® MDM Release Notes 11
Name Description Impact on Documentation
New activities to The following are the new For more information, refer to the zip and unzip files activities: following sections in the TIBCO MDM Workflow Reference: ● ZipFiles ● ZipFiles Activity ● UnZipFile ● ZipFiles Parameters and Valid Execution Modes
● Example for ZipFiles Activity
● UnZipFile Activity
● UnZipFile Parameters and Valid Execution Modes
● Example for UnZipFile Activity
Display Name The new Display Name For more information, refer to the support for property is added to the following sections in the TIBCO Repository repository metadata. MDM User's Guide:
● Sections on the View Repository Screen
● Copying a Repository
Import Runtime Parameters ● UI Changes: use the ● For the UI changes, refer to the following two new options "Importing Records" section of from the Start Import screen: the TIBCO MDM User's Guide.
● For the FileWatcher changes, — Validate Only refer to the sections "LoadImport — Confirm Immediately Action Parameters" and "ImportAction Parameters" in the ● FileWatcher: use the TIBCO MDM Customization Guide. following two new ● For web services, refer to the parameters in the Import and sections "Load Import Records LoadImport actions: Service - Inputs", "Import Records Service-Inputs", and "Process — ValidateOnly Records Service - Inputs" in the — ConfirmImmediately TIBCO MDM WebServices Guide.
● Web services: specify the following two new context variables in the Process Records, Import Records, and Load Import Records web services:
— ValidateOnly
— ConfirmImmediately
TIBCO® MDM Release Notes 12
New Configuration Properties The following table lists the configuration properties that are added in the 9.0.0 release of TIBCO MDM:
New Configuration Properties
Display Name Location in of Property Property Name Configurator Description Default Value
Record UI com.tibco.mdm Cluster Outline This property The default golden view .ui.record.go > InitialConfig enables the link value is false. ldenview > Cluster to view the Miscellaneous golden version of records and bundle
Websphere com.tibco.mdm Cluster Outline Websphere The default server name .websphere.se > InitialConfig server name value is jndi string rvername.jndi > NodeID > jndi string servername. lookup.string Application Server > WEBSPHERE
Hibernate Log log4j.logger. Cluster Outline The Hibernate The default Class Criteria org.hibernate > InitialConfig log class criteria values are > NodeID > DEBUG,elink, Logging and error.
Hibernate Log log4j.logger. Cluster Outline The log file for The default Appender File org.hibernate > InitialConfig debugging values are .hql.ast.AST > NodeID > information DEBUG,elink, Logging and error.
Create com.tibco.mdm Cluster Outline Using this The default relationship .optimization > InitialConfig property, you value is false. with latest .secondpass.r > Optimization can create version only elationship.l relationship atest.recordv entries only ersion between the latest record versions. Disabling the flag creates relationship with the golden copy version along with the latest version, which has little performance impact.
TIBCO® MDM Release Notes 13
Display Name Location in of Property Property Name Configurator Description Default Value
Record UI com.tibco.mdm Cluster Outline This property The default golden view .ui.record.go > InitialConfig enables the link value is false. ldenview > Cluster to view the Miscellaneous golden version of records and bundle.
Database com.tibco.cim Cluster Outline This property The default Debug Mode .db.debug > InitialConfig enables a trace value is true. > NodeID > to be generated System for database Debugging interactions. Used for debugging of database query issues. This value should only be enabled if requested by TIBCO support.
AS Security com.tibco.mdm Cluster Outline The The default Domain node .cache.as.sec > InitialConfig ActiveSpaces value is type urity.domain. > NodeID > security domain SECURITY_DOMA nodetype Optimization - type of node IN_CONTROLLER Member .
AS Security com.tibco.mdm Cluster Outline Encrypted The default Encrypted .cache.as.sec > InitialConfig password of value is empty. Domain or uritydomain.i > NodeID > domain if the token password dentity.passw Optimization - node is working ord Member as the controller or encrypted token password if node is working as requester
AS Security com.tibco.mdm Cluster Outline The network The default Network .cache.as.req > InitialConfig domain name value is empty. domain name uesternode.os > NodeID > when .networkdomai Optimization - ActivesSpaces n Member system authentication is enabled
TIBCO® MDM Release Notes 14
Display Name Location in of Property Property Name Configurator Description Default Value
AS Security com.tibco.mdm Cluster Outline The logged in The default Logged in .cache.as.req > InitialConfig operating value is empty. operating uesternode.os > NodeID > system system .username Optimization - username of the username of Member requester node requester node when ActiveSpaces system authentication is enabled
AS Security com.tibco.mdm Cluster Outline The logged in The default Encrypted .cache.as.req > InitialConfig operating value is empty. password of uesternode.os > NodeID > system user logged in user .password Optimization - password. The of requester Member password must node be encrypted.
AS Security com.tibco.mdm Cluster Outline The encrypted The default Encrypted .cache.as.req > InitialConfig password of the value is empty. password of uesternode.x5 > NodeID > x509v3 system x509v3 system 09v3.password Optimization - authentication. authentication Member
AS Security com.tibco.mdm Cluster Outline The key file The default Encrypted .cache.as.req > InitialConfig path of the value is empty. password of uesternode.x5 > NodeID > x509v3 x509v3 system 09v3.keyfile Optimization - certificate when authentication Member the x509v3 system authentication is enabled in policy.
Enable com.tibco.mdm Cluster Outline This property The default password for .clipassword. > InitialConfig enables value is true. CLI enable > password Authentication checking for rollback, restart, cancel, and resubmit CLI.
SMTP com.tibco.cim Cluster Outline Enables the SSL The default Additional .smtp.additio > InitialConfig connection to value is false. property - SSL nal.prop.mail > Email the SMTP email .smtp.ssl.ena server. ble
TIBCO® MDM Release Notes 15
Display Name Location in of Property Property Name Configurator Description Default Value
SMTP com.tibco.cim Cluster Outline The SMTP The default Additional .smtp.additio > InitialConfig timeout in value is 60000. property - nal.prop.mail > Email milliseconds. timeout .smtp.timeout Example : 60000 means 1 minute.
SMTP com.tibco.cim Cluster Outline The SMTP The default Additional .smtp.additio > InitialConfig connection value is 60000. property - nal.prop.mail > Email timeout in connectiontime .smtp.connect milliseconds. out iontimeout Example : 60000 means 1 minute.
Password mod com.tibco.cim Cluster Outline The password The default date file init .init.Passwor > InitialConfig mod date file value is loader dExpirationMa > Initialization init loader com.tibco.mdm nager.class .directory.se curity.authen tication.clou d.PasswordExp irationManage r.
Backward com.tibco.cim Cluster Outline Set this value to The default compatible .service.back > InitialConfig true to enable value is false. Web Service wardcompatibl > the backward Data types e83 Miscellaneous compatible data types (release 8.3) in the web service reply. Such replies cannot be validated using the supplied web service schema.
Enable Record com.tibco.mdm Cluster Outline Uses the Record The default Bundle Caching .bundlecache > InitialConfig Bundle caching. value is false. > Optimization
TIBCO® MDM Release Notes 16
Display Name Location in of Property Property Name Configurator Description Default Value
Cache com.tibco.mdm Cluster Outline Determines if The default Calculation .cache.autoco > InitialConfig auto cache value is false. Suppression mpute.disable > Optimization capacity calculation is suppressed. The value true suppresses the calculation.
Web Service com.tibco.mdm Cluster Outline Use this The default Query based .optimization > InitialConfig property for value is false. access rule .cacherbacces > Optimization local caching of caching s access rules while running WS-Query to increase the performance. Do not use when value- based access rules are used.
Enable com.tibco.mdm Cluster Outline Use this The default hibernate for .perspective. > InitialConfig property for the value is true. Perspective hibernate.ena > Optimization use of feature ble Hibernate technology for the perspective feature. If it is disabled, JDBC queries are used.
Default com.tibco.cim Cluster Outline Indicates if no The default rulebase .rulebase.dir > InitialConfig directive is value is true. directive - ective.canpar > Rulebase specified for a canParallalize allelize rulebase, should the rulebase execution be parallalized.
Default com.tibco.cim Cluster Outline Indicates if no The default rulebase .rulebase.dir > InitialConfig directive is value is false. directive - ective.skipif > Rulebase specified for a skipifnochange nochange rulebase, should rulebase be skipped if there is no data change.
TIBCO® MDM Release Notes 17
Display Name Location in of Property Property Name Configurator Description Default Value
Enable com.tibco.mdm Cluster Outline Enabling of The default activespaces .cache.as.sec > InitialConfig activespaces value is false. security urity.enabled > ActiveSpaces security security configuration
ActiveSpaces com.tibco.mdm Cluster Outline ActiveSpaces The default security .cache.as.sec > InitialConfig security value is implementation urity.impleme > ActiveSpaces implementation com.tibco.mdm class ntationclass security class which is .infrastructu configuration responsible for re.cache.as.s retrieving the ecurity.MqAct required iveSpacesSecu parameters for rity. AS Security.
ActiveSpaces com.tibco.mdm Cluster Outline ActiveSpaces The default security .cache.as.req > InitialConfig security value is NONE. authentication uesternode.au > ActiveSpaces authentication thentication. security type configuration
Activespaces com.tibco.mdm Cluster Outline TIBCO The default authentication .cache.as.sec > InitialConfig ActiveSpaces value is callback class urity.authent > ActiveSpaces security allows com.tibco.mdm name ication.class security to authenticate .infrastructu configuration the users of re.cache.as.s security domain ecurity.MqAct requestors. This iveSpacesDefa is the callback ultAuthentica class called by tor . activespaces when authentication is enabled in policy file. UserPwd and X509V3 is supported for system source.
TIBCO® MDM Release Notes 18
Changes in Functionality
The following are the changes in functionality in version 9.0.0 of TIBCO MDM: Changes in Golden Bundle Support Prior to TIBCO MDM 9.0 release, when related records were saved, the relationship entries were created only with the latest version of the related records. In TIBCO MDM 9.0 release, a new property (com.tibco.mdm.optimization.secondpass.relationship.latest.recordversion) controls the versions of records to be used while creating relationships. Also, the default behavior has been changed in this release, where the relationship is created with the latest version of the related record, and the golden copy version, if both are not the same. To enable the golden bundle feature on the View Record screen, set the value of the Record UI golden view (com.tibco.mdm.ui.record.goldenview) configuration property to true in Configurator. For more information on the new property, see the New Configurations Properties table in New Features.
Changes in Purge Using Command-line With the release 9.0, purge through the command-line interface requires the password to be mandatory, as well as permission to execute the command-line interface.
Rulebase Parallelization Prior to TIBCO MDM 9.0 release, all records in a bundle were processed in a serial order. With the release 9.0 onwards, you can have more control over the processing order. You can define dependencies in rulebases and can utilize parallel execution within a bundle. With no dependencies to define, almost all records in a bundle can be processed in parallel to optimize the overall rulebase execution time. In the TIBCO MDM 9.0 release, by default the parallel execution of ruleabse is enabled. Therefore, if you are migrating from the previous version, you must review rulebases and define correct dependencies in the ruleabse.
Validation of Records on Record UI Prior to TIBCO MDM 9.0 release, while navigating the hierarchy of related records on the Add, Modify, and View Record screens, the record bundle was evaluated upto depth level two. This default level depth is defined in Configurator for the Validation Record Bundle Depth property. With release 9.0, the records are evaluated from the depth of the selected top root record.
Undo Replaced by Rollback For more information, refer to Deprecated and Removed Features.
TIBCO® MDM Release Notes 19
Deprecated and Removed Features
The following tables list the features that have been deprecated or removed in the version 9.0.0 of TIBCO MDM.
Deprecated Features
Affected Deprecated Component Description Release
Record UI The record UI renderer feature has been deprecated. 9.0.0 Renderer
Patterns Support for the patterns partitioning functionality has been 9.0.0 Partitioning dropped. This functionality has been superseded by the Patterns gateway setup (also called federated queries). The clusterIndex inside the IndexerConfig.xml file should always be equal to one (1) and never larger. The Patterns gateway setup replicates the partitioning functionality, and is faster and more accurate.
The CATALOGATTRIBUTEDATATYPE database table has been 9.0.0 deprecated.
TIBCO® MDM Release Notes 20
Removed Features
Affected Compone Impact on Deprecated Removed nt Description Documentation Release Release
TIBCO The following utilities are The references of these 9.0.0 9.0.0 MDM removed from the utilities are removed $MQ_HOME/bin directory: from the TIBCO MDM Installation and ● browseQueue.* Configuration Guide and the TIBCO MDM ● Checksum.* System Administration. ● CommTestSimple. ● commTest. ● Communicator.* ● Db2b.bat ● db2ldr ● eventUndoTest.bat ● execGC.* ● fixOSSpecific.sh ● GenerateData.pl ● HotDeployConfiguration. * ● HtCommandLineTool.* ● httpSender.* ● HTUITool.* ● Psql.* ● queueChat.* ● replaceRules.* ● rulelist.* ● showqueues.txt ● replaceSQLQuery_80_82 ● testemail.* ● tibcoappcheck.* ● topicchat.* ● tibcoMDMMigration.sh/ bat ● updateEARForJboss510.*
TIBCO® MDM Release Notes 21
Affected Compone Impact on Deprecated Removed nt Description Documentation Release Release
The following folders are Not applicable 9.0.0 9.0.0 deleted from the $MQ_HOME/db directory:
● altibase ● db2
Raw Mode The Raw mode was used for The description of the 9.0.0 9.0.0 the bulk update of record Raw parameter is status to gain performance. removed from the However, it caused UpdateRecordState inconsistency in the cache activity in the TIBCO and index. MDM Workflow Reference.
Cache The Clear Record Cache The reference of this 9.0.0 9.0.0 Clear on on Update property was property was Update used to control if the cache mentioned in the Property should be cleared or updated "Record Cache on record update. The cache Clearing" section of is now always updated. the TIBCO MDM Therefore, the property is Installation and removed from Configurator. Configuration Guide. This section is removed.
Undo Undo is replaced by the The reference of this 9.0.0 9.0.0 Rollback feature. The undo feature has been feature was only supported replaced with rollback to undo the whole event. It is information in the now possible to roll back the "Actions on Events" workflow up to a specific section of the TIBCO step or event. Rollback can MDM User's Guide. be done through the command-line interface or the TIBCO MDM UI.
TIBCO® MDM Release Notes 22
Migration and Compatibility
This section explains the impact of migration from a previous release to this release to various parts of the application.
Upgrade to 9.0 from 8.3.x and 8.2.X
You can upgrade TIBCO MDM to 9.0 from 8.3.x and 8.2.x versions. Consider the following points while upgrading to the 9.0 version:
Upgrade to Microsoft SQL Server 2012
The support of Microsoft SQL Server 2008 is removed from release 9.0. If you are using Microsoft SQL Server 2008, upgrade to Microsoft SQL Server 2012, and then follow the database migration process. For more information, refer to the section "Upgrade to TIBCO MDM" in the TIBCO MDM Installation and Configuration Guide.
Application Server Configuration
For the JBoss Application server, define the MDM EJB pool with the appropriate pool size. For more information, refer to the section "Installing on JBoss Application Server" in the TIBCO MDM Installation and Configuration Guide.
New Configuration Properties
For new configuration properties, refer to New Features.
Migration Components
If you are migrating from 8.3.x and 8.2.x versions to 9.0, you must migrate the following components:
● Configuration migration ● Database migration ● Cache configuration migration ● Common directory migration For more information on migrating these files, refer to the section, "Upgrade TIBCO MDM" in the TIBCO MDM Installation and Configuration Guide.
Migration for Language Pack
If you have installed a TIBCO Multilingual User Interface (MUI) pack in the previous version, uninstall the MUI before installing the new language packs. For information on installing a language pack, refer to the section "Installing Language Pack", in the TIBCO MDM Installation and Configuration Guide.
Migration for Synchronization Enhancements
The alterForSelfOutputMaps.sql script is provided in the $MQ_HOME/db/databasename/ migration/Migrate83_90 directory. Run the script to support out-of-the-box self relationships between output maps for the existing metadata and to add self-related output maps to the repository that contains self-active relationships. For more information on executing the script, refer to the section "Self Relationship between Output Maps" in the TIBCO MDM User's Guide.
Migration for Golden Bundle
The fixRelationshipGoldenBundle.sql script is provided in the $MQ_HOME/db/databasename/ migration/Migrate83_90 directory. Run the script to use the golden bundle feature for the existing
TIBCO® MDM Release Notes 23 records. The script ensures that the relationship between the golden copies is established and also the relationship between the latest version and the golden copy version.
Migration for Rulebase Parallelization
For more information, refer to Changes in Functionality.
Impact of Precedence Management
New SQL views are added to the seed data and to the migration scripts. For information on precedence management, refer to the section "Precedence Management" in the TIBCO MDM Customization Guide.
Backward Compatibility for Rulebase Execution Optimization
Change the following default directives to restore backward compatibility:
● com.tibco.cim.rulebase.directive.canparallalize: set to False.
● com.tibco.cim.rulebase.directive.skipifnochange: set to False. For information on rulebase execution optimization, refer to the TIBCO MDM Studio Release Designer User's Guide.
Impact of All-in-One Installer
The all-in-one installer, that is, simple installation with PostgreSQL uses HornetQ Messaging Server instead of EMS.
Impact of Data Quality Enhancements
The data quality work item has been redesigned to show the source record and its child irrespective of the matching. Additional functionality, such as inline edit, drag and drop, and rejecting multiple source records have been implemented.
Impact of Miscellaneous Enhancements
● Cleanup of components: all migration related files and tools are moved to the $MQ_HOME/bin/ migration directory.
● Display name support for repository: the migration script is provided to copy the NAME to DISPLAYNAME column for the old repository entries.
Troubleshooting for Migration
To resolve the migration errors that you might come across postmigration, refer to the section "Migration Troubleshooting" in the TIBCO MDM Installation and Configuration Guide.
TIBCO® MDM Release Notes 24
Closed Issues
The table lists the closed issues in version 9.0.0 of TIBCO MDM.
Closed Issues
Key Summary
CIM-22693 Text search result did not sort records based on the similarity score.
CIM-21872 Millions of records were imported using database loader. On clicking Search on the Browse and Search screen did not return the records in the search result.
CIM-21843 When split and join transitions were used in a workflow, the activities appeared to split correctly, but continued through to the next activities without stopping and waiting to join with the parallel activities.
CIM-21841 An error occurred after modifying a record through the work item using the custom UI, if the repository contained a future effective attribute.
CIM-21840 An error occurred after clicking the Duration (D:H:M:S) column in the Event Log screen to sort events by duration.
CIM-21677 The IN_LISTSTR function has been optimized for the SQLServer database.
CIM-21674 Using a web service, if only a single record was modified in a large record bundle, the complete record bundle was validated instead of the records that were present in the request. To have this capability, the web service can be used with the following context variable:
● Internal name: com.tibco.cim.rulebase.directive.skipifnochange ● Version: 8.3.2 ● Visibility: Advanced ● Description: It validates only changed records. This flag is only applicable when you click Save or Save & Process. Not applicable in the case of Validate or Record View. When this flag is specified as true, it is assumed that, dependent constraints and propagation rules do not exist for unchanged records.
● Current value: true
● Default value: true
● Category: Optimization
CIM-21546 With the Load Relationship mode, relationships did not get established between expected records for direct load import.
CIM-21538 The RecordQuery web service was returning related records in random order.
TIBCO® MDM Release Notes 25
Key Summary
CIM-21458 The Get Event Details web service failed when an event was not completed.
CIM-21457 The attributes configured using the Configure window for the Add Relationship screen did not display on the Record Search Relationship page.
CIM-21429 When a record was opened for modification from the Record Introduction page of a work item, a record was displayed in the non-editing mode along with an error message.
CIM-21402 SQLException was observed while executing the VerifyRecordStatus activity when the special character ? was used in the external key.
CIM-21356 The increased usage of cursors in the user-defined functions to drive the string creation, caused unnecessary I/O and a burden on the SQL server.
CIM-21326 Synchronization with relationships did not produce the output file in the expected format.
CIM-21307 The recordui-render.xml was configured to have relationships under tabs. The related records contained attributes of type boolean and date. On subsequently modifying the related records, the drop-down lists and date picker did not work. The issue occurred on Internet Explorer 11.
CIM-21290 The Propagate-Rulebase action was used to propagate the product ID from the parent record to the child record. The propagated values were not shown on the UI due to the wrong depth calculation and ProductID attribute name mapping.
CIM-21223 The information provided in the record change notification was not sufficient to distinguish the golden copy records and future dated records. Now on changing the record, the notification has the following xml tag to convey that the record is future dated:
TIBCO® MDM Release Notes 26
Key Summary
CIM-21220 The record query web service did not have the capability to fetch only the golden bundle. To have this capability, use the record query web service with the following context variable:
● Internal name: com.tibco.mdm.optimization.secondpass.relationship.latest.recordversion ● Version: 8.3 ● Visibility: Advanced ● Description: This flag enables the creation of relationship entries only between the latest record versions. Disabling the flag creates the golden copy version along with the latest version, which has little performance impact. ● Value Type: Boolean ● Current Value: false ● Default Value: true ● Category: Optimization
CIM-21219 For the same user credentials, an error occurred while modifying a record using the TIBCO MDM UI and the TIBCO MDM plug-in for Business Works.
CIM-21208 The CAT-1281:Record Not Found error was displayed while opening a work item.
CIM-21193 A validation error occurred because special characters were not transformed back to their initial form.
CIM-21116 For a user with a data steward role, after clicking Save while modifying the record through the work item, the Inbox screen was displayed instead of the Work Item Details screen.
CIM-21097 Although the Edit when record is in workflow record permission was set to Allow, an error was displayed on modifying the related record through the work item for another user with the same role.
CIM-21059 The classification scheme deployment took a long time and threw a read time out error.
CIM-21042 The InDocument did not have the ActionCode section populated for new related records added through a work item.
TIBCO® MDM Release Notes 27
Key Summary
CIM-21024 Using Database Loader, on importing the same record multiple times with fresh data unchecked and then modifying the record using the TIBCO MDM Plugin Palette, the incorrect parent version of the record was displayed in the principal key table.
CIM-21020 In the data quality work item, the repository names and attribute names were displayed in English, even though the localization support for Japanese language was defined.
CIM-21019 In the Match activity, while using the predicate functionality of the Netrics server, empty or null values were not displayed in the search result. To resolve this issue, add the following parameter in the Match activity:
CIM-21015 On MS-SQL Server 2012, using Database Loader, importing of relationship failed if sequencing was enabled.
CIM-20974 On the Browse and Search page, for the IN operator, the attribute configured to display as a drop-down list for the record search did not work.
CIM-20972 In the data quality work item, relationship records were not merged if source and target records had the same relationship record.
CIM-20963 After applying the Delete permission resource security for a record, the Delete Record option did not work as expected.
CIM-20946 Entries were found in the FUTUREDATEDRECORD table, even though EFFECTIVEDATE attribute was not defined. Therefore, when trying to update the repository and redeploy from TIBCO MDM Studio an error was thrown: CAT-1017: Invalid attribute definitions: 'null' attribute cannot be deleted as there are existing future dated record(s) for the repository.
CIM-20935 While adding and viewing records with a large number of multivalue or category specific attributes sharing the same data table, the STACKTRACE: java.sql.SQLException: ORA-01460: unimplemented or unreasonable conversion requested error occurred. This happened because the SQL query failed on Oracle as the IN clause parameter exceeded the 4000 characters limit.
CIM-20934 The multi_relationship_record link was not evaluated for the Record Query Web service.
CIM-20912 In the Japanese language pack, the pagination forward button on the Browse and Search result screen did not appear.
CIM-20906 The rulebase nvl function returned null value, when the first value was null, even though the second value (constant or variable) had non-null values.
TIBCO® MDM Release Notes 28
Key Summary
CIM-20905 The rulebase execution for the USER_ACTION context variable returned null values.
CIM-20904 On the incremental deployment of workflows, the same workflow was listed multiple times in the Process drop-down list on the Process Definition Selection rule list page.
CIM-20857 When the doall.sh utility was used, seed data creation failed on the Oracle 12c database.
CIM-20844 In the Save Record activity, while retrieving the relationship attribute from InDocument, if the relationship attribute was of the type Timestamp, the value returned was in ISO format.
CIM-20837 In Internet Explorer 8 compatibility view mode, on the Browse and Search page, the drop-down values for the record search was displayed beneath the content.
CIM-20807 On the data quality work item and the Record UI (tree panel) page, incorrect values were displayed for the shownoninput parameter.
CIM-20758 When manually merging records, NullPointerException occurred and the work item was not created.
CIM-20728 On the Record UI, if a rulebase was applied, all the values of a multivalue attribute were not viewed for relationship as a tab.
CIM-20679 On the TIBCO MDM UI page for the Date or Timestamp picker widget, you could not select the year value as less than 1900.
CIM-20660 On the Record UI page, when clicking the Configure button, the same attributes were displayed for all the relationships.
CIM-20590 The following Merge work item UI enhancements were requested:
● Increase in vertical window size on the Merge Record Details window ● Remove unused fields ● Increase in vertical scroll bar on the Merge Record work item screen
CIM-20589 When a rulebase was configured with multiple "hide_record" actions in different constraints, the records' search SQL generated query was incorrect. This resulted in the unexpected output in the response of the RecordQuery web service.
CIM-20536 The attributes were displayed on the relationship tree and view record header page, even though the attributes were defined as hidden.
CIM-20531 While importing records, the data load was stuck at the ImportCatalogRecords activity in a highly concurrent environment.
TIBCO® MDM Release Notes 29
Key Summary
CIM-20506 The context variable, EFFECTIVEDATE, passed in the Record Query web service was conflicting with the record attribute EFFECTIVEDATE while executing the access constraint in a rulebase.
CIM-20493 The URL example of the Record View and Record Modify pages mentioned in the TIBCO MDM Customization Guide was not updated.
CIM-20489 The Record UI was customized for a relationship as a tab using the recordui- render.xml file. The related record contained multi-value attributes, which were displayed in the record list. On selecting the value in the drop-down list for a multi-value attribute and clicking Done, no action was performed.
CIM-20484 While validating the TIBCO MDM project for deployment in TIBCO BusinessWorks version 5.8, schema validation errors were thrown. To fix this issue, copy the cimDesignDeploy.wsdl file from $MQ_HOME/customEAR/schema/ DataService/2.0 to the schema folder in the TIBCO BusinessWorks project.
CIM-20442 For already published records, if the value of a relationship attribute, that is, Quantity was changed, and then the records were republished, an error occurred. This issue is specific to TIBCO MDM Add-on for Global Data Synchronization.
CIM-20433 The Internet Explorer 10 and 11 version browser support issue occurred for the TIBCO MDM 8.3.2 version.
CIM-20418 When JMX was disabled and SMTP was enabled, the server start up failed with a JMS-8402 exception.
CIM-20417 Using import, if a record was deleted and a record was created again with the same ProductID and ProductIDEXT, an error occurred.
CIM-20415 When the parent of a child record was deleted in a highly concurrent environment, the parent record was still visible when viewed from the reverse relationship. After modifying the deleted parent record through reverse relationship, the "Record cannot be bundled unless it is sent for processing" message was displayed.
CIM-20413 While viewing Calendar for the Timestamp datatype attribute, the month and year pickers were not visible.
CIM-20410 During migration from the TIBCO MDM 8.2.1 to 8.3.1 version, the MigrateRules.sh utility using the -migrateRulebase parameter did not migrate rulebases for relationship. This resulted in a null pointer exception while adding a record from the parent repository and adding a related record to the child repository.
CIM-20381 HTTP 404 error occurred if you locked a work item and if another user other than the work item owner tried to open the work item.
CIM-20348 The Record Add/Modify/View page did not show the correct display name for the PRODUCTID and PRODUCTIDEXT attributes.
TIBCO® MDM Release Notes 30
Key Summary
CIM-20338 The number of years set in the Calendar was limited to 40. The Calendar has been enhanced to display 100 years.
CIM-20334 The UpdateRecordState activity did not reject all the records, whose Record keys were passed in the input.
CIM-20331 If an attribute was changed or deleted from the repository model and the same model was redeployed on the TIBCO MDM server, the updated attributes were not correctly displayed on the repository metadata page.
CIM-20314 When the LDAP referral context was set to FOLLOW, an error occurred while logging into TIBCO MDM with an LDAP user. To resolve the issue, replace LDAPHelper.class in ECMClasses.jar.
CIM-20308 When TIBCO MDM was configured with DEBUG level logging and datasource upload operation was performed, the database password was displayed in the elink.log file.
CIM-20300 The attributes of all the repositories were not visible under the Repository tab if the Application Provider name value was other than the default value.
TIBCO® MDM Release Notes 31
Key Summary
CIM-20297 For a relationship with multilevel depth, on validating the parent level, errors were not displayed even though there were errors at the child level. To resolve the issue, add the following property in Configurator: (Configurator > Add New Property):
1. Configuration value name: Enable to evaluate display actions
● Internal name: com.tibco.mdm.ui.record.alwaysExecute.displayAction ● Version: 8.3 ● Visibility: Advanced ● Description: This flag permits validation of invalid data set in the record against valid values defined in the rulebase. ● Value Type: Boolean
● Current Value: true
● Default Value: false
● Category: Miscellaneous 2. Configuration value name: enable to find all error records
● Internal name: com.tibco.mdm.ui.record.showAll.errorRecords ● Version: 8.3 ● Visibility: Advanced ● Description: This flag permits a list of all records that have errors. ● Value Type: Boolean
● Current Value: true
● Default Value: false
● Category: Miscellaneous
CIM-20287 The Properties panel of Configurator was not refreshed after selecting different member nodes. This issue occurred in the case of the default configuration menu.
CIM-20267 While comparing deleted records, the CompareRecord activity failed with NullPointerException.
CIM-20254 Data source upload failed if the character length of a data source attribute was greater than the default value.
CIM-20240 The rulebase was configured with the following two conditions:
● If the condition was true, a drop-down list should be displayed
● If the condition was false, the text box should be displayed
In this case, when the condition was false, a drop down list with no values was displayed instead of a text box.
TIBCO® MDM Release Notes 32
Key Summary
CIM-20223 While adding a related record through a web server URL, a blank screen was returned. The issue occurred on the WebSphere Application Server and Internet Explorer 8 version.
CIM-20179 Special characters were not allowed in the property name. For example, if a hyphen ('-') was specified in the relationship name, the customization did not work. The "Displaying Attributes in a Relationship Tree" section has been updated in the TIBCO MDM Customization Guide.
CIM-20147 The user name was not updated for the "Modified By" system attribute, when a related record was modified from the UI.
CIM-20146 The support of 'Display name' property for repository was requested.
CIM-20117 The OutDocument of the CompareRecord activity showed changes in multivalue attributes even though no changes were made to the multivalue attributes' list.
CIM-20113 The IndexEntityNameToSearch parameter specified intermittently for multiple MatchRecord activities was not populated as expected.
CIM-20077 Rulebase was not applied during synchronization. To resolve the issue, add the following property in Configurator: (Configurator > Add New Property):
● Configuration value name: Cache Catalog Edition ● Internal name: com.tibco.cim.optimization.cache.catalogedition ● Version: 8.3 ● Visibility: Advanced ● Description: Disables catalog edition cache. ● Value Type: Boolean
● Current Value: false
● Default Value: true
● Category: Optimization
CIM-19988 An error occurred while importing records with the data quality workflow in the case of direct merge. This issue occurred only on the PostgreSQL database.
CIM-19975 When related records were entered, validation errors were thrown and the selection of options from the drop-down list triggered the page reload. This caused the New Related Record screen to disappear. However, a related record was created.
CIM-19972 Unable to assign or modify the value of the relationship attribute using the EvaluateRulebase Activity in a workflow.
TIBCO® MDM Release Notes 33
Key Summary
CIM-19930 The input value specified for the MatchingThreshold parameter of the MatchRecord activity was up to three digits, but the MatchingRecordRelevanceScore was limited to two digits after the decimal separator. To resolve the issue, add the com.tibco.cim.netrics.matchScoreDecimalPrecision property in Configurator. By default, the value is 2. You can specify the number of digits after decimal points. The maximum number is 6.
CIM-19928 While configuring the display attributes using the Configure window on the Add Relationship screen, the configuration was not saved.
CIM-19909 Hide attribute constraints did not work in the relationship catalog validation.
CIM-19855 The calculate-cachesize.cmd utility related to tangosol was no longer supported and was not available in $MQ_HOME. The reference from the TIBCO MDM System Administration has been removed.
CIM-19815 Imported records with attribute values containing accented characters were not displayed correctly on the record UI.
CIM-19803 In the MatchRecord activity, if cross-repository indexes were specified for the IndexEntityNameToSearch parameter, only parent records were matched.
CIM-19799 While viewing a record that contained PRODUCTID starting with #, the Record Not Found Exception was displayed.
CIM-19792 While running performance tests on large record bundles using the Record Add web service, a large number of relationship queries were executed impacting the performance.
CIM-19779 While merging records with the File type attributes, an error was displayed.
CIM-19774 An
CIM-19762 A user selected the time zone in Locale Settings. However, while adding or validating records, the selected time zone was not set for the Timestamp type attribute in the repositories when Daylight Savings Time (DST) was active.
CIM-19757 When the LDAP referral context was set to FOLLOW, an error occurred while logging into TIBCO MDM with an LDAP user.
CIM-19742 The session ID used in the CRUD web services through the Custom UI did not work.
TIBCO® MDM Release Notes 34
Key Summary
CIM-19741 Importing of metadata containing the previously exported business process rule (BPR) failed. The BPR contained instances or rules created only for the user-defined template.
CIM-19727 The AttributeGroup query used in the Record Query web service was executed multiple times and this put load on the database.
CIM-19719 Modification of a rejected record from a cancelled event did not work correctly.
CIM-19681 A record was viewed from the search result of the Browse and Search page, and then OK was clicked. In this case, on returning to the Browse and Search page, the search section displayed an HTTP error or 'page cannot be found' exception. A set of related repositories was displayed as a combined tab. After clicking Validate for the root repository, the Create and Delete buttons were disabled for the related repositories.
CIM-19673 Is Defined (id) operator did not work with the timestamp attribute.
CIM-19646 A list of related records was sorted on the Modify Record screen. After clicking one of the related records, the sorted list order reverted to the original order instead of maintaining the last sorted order.
CIM-19644 After running the AlterProcessState.sql script, an error occurred on the update statements when the STATEPARAM2 column exceeded 4000 characters.
CIM-19637 When the RECORD_ACTION variable was defined as COPY in a validation file, after clicking the Copy link for a record on the Browse and Search screen, the PRODUCTID was generated. However, after clicking Save and Process, RECORD_ACTION did not change from COPY to ADD and the new ID was assigned to PRODUCTID. To avoid regeneration of PRODUCTID, use RECORD_ACTION=COPY along with the USER_ACTION context variable in the catalogvalidation.xml using the following values:
● PAGE_INIT ● PAGE_REFRESH ● VALIDATE ● SAVE ● SAVE_PROCESS This ensures to generate the PRODUCTID in sequence only once according to the USER_ACTION context variable.
CIM-19629 Deploying TIBCO MDM 8.3.2 failed on the WebLogic Application Server version 12.1.3.
CIM-19605 The hide record rulebase functionality did not work correctly, if the true and false values were entered in lowercase for the BOOLEAN attribute type.
TIBCO® MDM Release Notes 35
Key Summary
CIM-19597 The flag to disable the column header was not working for the select type as 'Table' when configured through the rulebase select action.
CIM-19580 The CreateWorkItem activity failed intermittently when the DOCUMENTTYPE column size in the WORKITEM table was greater than 70. The issue occurred on Microsoft SQL Server and PostgreSQL databases.
CIM-19567 After deploying the Enum type for the Select action from TIBCO MDM Studio 4.0, defined for the boolean data type attribute, the validation errors were displayed for the existing records having Boolean values in uppercase letters.
CIM-19561 When the Record UI was customized for relationship as a combined tab using the recordui-render.xml file, NullPointerException was thrown while adding a related record.
CIM-19538 An error occurred while validating Indocument created for the Mass Update operation with mlxml schema.
CIM-19474 The Record Query web service request containing RelationshipData did not capture relationships between records, if the record was in the DRAFT state and the business process rule was set to repository.
CIM-19458 The scheduled duplicate detection job failed with an error for TIBCO MDM 8.3.1 HF04.
CIM-19433 Seed data creation failed with the ORA-01843 error during the Oracle database set up.
CIM-19332 While viewing a record or creating a record, the null pointer exception was shown. The issue was observed after recreating the relationship attribute with the same name but with a different data type and the com.tibco.cim.cache.repositoryspace.enable property was set to true.
CIM-19314 Information about changing the database type and copying the drivers before migration was missing from the TIBCO MDM Installation and Configuration Guide.
TIBCO® MDM Release Notes 36
Key Summary
CIM-19294 On clicking Save and Process for a record with errors, the workflow was triggered, even though the record had errors. To resolve the issue, add the following property in Configurator: (Configurator > Add New Property):
● Configuration value name: Enable JMX Monitor ● Internal name: com.tibco.mdm.ui.record.processWithError ● Version: 7.1 ● Visibility: Advanced ● Description: This property enable/disable processing of error records during save and process. ● Value Type: Boolean
● Current Value: true
● Default Value: true
● Category: Miscellaneous Limitation: This resolution does not work for the repository without relationship.
CIM-19290 On the relationship tree, when you right-click the record, all the related records in the hierarchy did not expand. To resolve the issue, add the following property in Configurator: (Configurator > Add New Property):
● Configuration value name: Expand to level ● Internal name: com.tibco.mdm.ui.expandToLevelMax ● Version: 8.3 ● Visibility: Advanced ● Description: Added to configure maximum level to which tree node can be expanded ● Value Type: Number
● Current Value: 8
● Default Value: 2
● Category: Miscellaneous
CIM-19288 If the combination of the first name and last name of the user name exceeded 80 characters, an error occurred in the CreateWorkitem activity during record creation.
CIM-19212 The resubmitted events did not get purged with history purge.
CIM-19126 With a softlink on an attribute that referenced records on another repository, when clicking the BACK button, an error page was displayed.
TIBCO® MDM Release Notes 37
Key Summary
CIM-19081 The catalog validation rule that was set for deleting the value from the drop-down list did not work on Internet Explorer 10 and 11 versions.
CIM-19016 The following issues occurred with the softlink:
● An error page was displayed after clicking the BACK button on the View Record screen for the related records. ● TIBCO MDM menus and title bar were shown within the child window, when the softlink record was selected.
CIM-19015 A record was viewed from the Mass Update screen. After clicking OK on the View Record screen, instead of returning to the Changed Records List screen, the default Mass Update screen was displayed with the search fields.
CIM-19014 For attribute values, number codes were shown instead of special characters on the View Record screen.
CIM-19013 The parent record was deleted after modifying the child record details and its effective date value.
CIM-18999 If the repository spaces were enabled, the Entry_TTL value of the RECORD space was overwritten by the value of
CIM-18998 While modifying a record with relationship from the work item, the related records were not shown in the Relationship tab.
CIM-18997 If the workflow contained multiple CompareRecord activities, the OutDocument generated by the CompareRecord activity failed on validation against the mlXML schema.
CIM-18996 The Load Relationship mode of the database loader failed to establish relationships when the RecordIDExtension value was empty.
CIM-18994 On the Browse and Search screen, the following issue was observed:
● If the previous searched criteria was cleared, clicked View All, and then navigating to the next page, the subsequent pages displayed the previously searched result and an incorrect page count.
CIM-18993 When the child record was modified through the parent record modify operation, the record was not saved after clicking Save and Process.
CIM-18992 The recordui-render.xml file was configured to display relationships in a single tab. On the Modify Record screen, after clicking the column header of an attribute in the Relationship tab, the entire table disappeared.
CIM-18991 A query that was used to validate subset rules by expression was slow.
CIM-18990 The stale data error occurred during execution of the rulebase activity in the spawned workflow.
TIBCO® MDM Release Notes 38
Key Summary
CIM-18989 The stale data error occurred during the modification of records without concurrency.
CIM-18988 The value of the relationship attribute disappeared after modifying the related record of a child record.
CIM-18987 The drop-down lists disappeared while scrolling down the attribute values on the Add Record and Modify Record screens. This issue occurred on Internet Explorer Version 9.
CIM-18986 If the com.tibco.mdm.indexing.indexOnStartup property was set to false and the TIBCO MDM server restarted, the text indexing failed with the Java null pointer exception.
CIM-18984 An SQL error occurred for subset rules when a rulebase was specified to hide records.
CIM-18982 While selecting workflows on the Export Metadata wizard, a workflow file was replicated in the Available WorkFlows list. One file was appended with .xml extension whereas another file did not have an extension. For example, the wfin26catsourcev6.xml and wfin26catsourcev6 files.
CIM-18981 If the parent record ID contained a special character while creating a related record or modifying the existing related record, a null pointer exception was displayed.
CIM-18980 The attribute group with all category specific attributes was specified as the first group tab in the recordui-render.xml file. However, on the record UI, when a record was not available in that specific category, the customized combined tab disappeared.
CIM-18978 The Compare and Show History buttons were disabled on the View Record screen when any language pack, other than English was applied.
CIM-18969 While modifying a record using a perspective from the Browse and Search screen, an SQL database error was shown.
CIM-18960 The following issues occurred with the softlink:
● An error page was displayed after clicking the BACK button on the View Record screen for the related records. ● TIBCO MDM menus and title bar were shown within the child window, when the softlink record was selected.
CIM-18956 The recordui-render.xml file was configured to display relationships in a single tab. While changing the timestamp attributes of child records, the timestamp generated by the timestamp picker displayed DD/MM/YYYY 00:00:00. However, the correct timestamp format is YYYY-MM-DD HH:mm:ss.
CIM-18923 When importing metadata, the repository IDs were not properly substituted in a rulebase with an Include action.
TIBCO® MDM Release Notes 39
Key Summary
CIM-18894 The localization of reverse relationship names in the case of self-relationships was not working correctly.
CIM-18889 The attribute name translation did not work if the related records were displayed as an embedded tab.
CIM-18863 Emailing records using the Quick Export function of the Browse and Search screen did not work.
CIM-18840 The following command-line utility did not purge record versions, which were set older than the cut-off date: ./datacleanup.sh -o recordversions -r
CIM-18820 The parent record was deleted after changing the effective date value of a child record.
CIM-18817 The Showoninput clause was specified for the drop-down based constraints of a related record in the rulebase validation file. When the relationship name was clicked on the relationship tree, the attribute value of a child record was not displayed as per the specified rulebase in the record list.
CIM-18813 While executing the Record Query web service, the rulebase context variable RECORD_ACTION was evaluated as EDIT instead of VIEW.
CIM-18676 The Java null pointer exception was shown on uploading a file to the file type attribute. This occurred when the file type attribute name was the same or contained a substring of the repository name.
CIM-18670 The Hot Deployable field for a new configuration property was not available on the Add New Property window in Configurator.
CIM-18641 For SQLServer, on server startup, an SQLException occurred during indexing records with multivalue attributes.
CIM-18428 The PrepareForImportCatalog activity did not use the date format defined in the data source to parse the dates.
CIM-18423 The configured attributes were not displayed correctly on the search result page while searching for existing relationships.
CIM-18395 When the Record Query web service was used, the timestamp attribute was not displayed in the correct format for Oracle.
CIM-18386 On the View and Modify record screens, the html number code was displayed instead of special characters on the UI. For example, | was displayed instead of the character |.
TIBCO® MDM Release Notes 40
Key Summary
CIM-18371 The date calendar displayed on the Mass Update screen was not consistent with the date calendar displayed on other screens.
CIM-18370 Comparing records did not work if the order of record versions selected on the Compare Records screen was changed. This issue occurred for compare relationships and related target records.
CIM-18369 While redeploying a relationship along with the deleted relationship attributes in TIBCO MDM Studio, the Java NullPointer exception was shown.
CIM-18368 When a record with relation was modified and a few related records contained a validation error, an error exclamation was shown for all related records.
CIM-18367 The drop-down list values on the Mass update screen varied from the values on the Add Record and Modify Record screens.
CIM-18366 The performance of database loader import was very slow with Microsoft SQL Server 2012. To improve the performance, use sequences based on Microsoft SQL Server 2012 instead of trigger-based custom solution. Perform the following tasks:
● Run the CreateSequences.sql migration script to create sequences. ● Add the following property in Configurator to enable usage of the sequences:
— Configuration value name: Enable SQLServer 2012 based sequence — Internal name: com.tibco.mdm.optimization.sequence.sqlserver2012 — Version: 8.3.1 — Visibility: Advanced — Description: Enable SQLServer 2012 based sequence usage for PRODUCTKEY and RELATIONSHIP
— Current Value: true
— Default Value: false
— Category: Miscellaneous
Microsoft SQL Server 2008 does not support sequences. Therefore, rollback to this server is not supported.
CIM-18365 After comparing related records, when the user returned to the parent record, only the viewed relationship was displayed in the relationship tree. The remaining relationships disappeared.
CIM-18364 A performance issue occurred while loading the relationship tree.
CIM-18363 While searching records on the Browse and Search page, incorrect values were displayed in the search result after navigating to the next page. Also, the pagination displayed an incorrect number of records.
CIM-18362 While searching for records using Text Search (Attribute Based Search), duplicate values were displayed in the attribute field.
TIBCO® MDM Release Notes 41
Key Summary
CIM-18361 The catalog validation applied for the attribute other than the string data type did not execute correctly on the Classifications tab. This issue occurred after navigating to the next page.
CIM-18360 The alignment of the data was not in sync with the column headings in the search results of the Browse and Search page.
CIM-18359 The export of role permission metadata was failing with the following exception: Relationship not found for resourceID
CIM-18358 Subflow did not resume after the timed-out transitions of work items and closure of all timed-out work items.
CIM-18357 The Add Reocrd event name appeared in the spawned (associated) events instead of the specified eventDescriptor parameter in the UpdateEvent activity.
CIM-18356 When a subflow called by a SYNCHR InitiateSubFlow activity returned control, the parent workflow did not restart. To resume the suspended process, run the workflowUtility.sh utility. Before running the workflowUtility.sh utility, perform the following steps:
1. Run customUtil.sh -createCommonHotfixLibrary. 2. Specify the complete file path of the hotfix JAR file.
3. Enter Y when prompted with Copy $MQ_HOME/hotfixTemp/AllECMClasses- hotfix.jar to $MQ_HOME/lib/hotfix directory
4. Copy new AllECMClasses-hotfix.jar from $MQ_HOME/lib/hotfix to $MQ_HOME/lib/external.
5. If you enter N in step 3, copy new AllECMClasses-hotfix.jar from $MQ_HOME/ hotfixTemp to $MQ_HOME/lib/external. Usage:
● Copy workflowUtility.sh from $MQ_HOME/customEAR/bin to $MQ_HOME/bin directory.
● Run workflowUtility.sh with the following options: workflowUtility.sh - c
Options:
● c: command, currently only resume is supported.
● m: member ID
● e: event ID
● p: process ID For example: to restart process 789890, specify the following command: workflowUtility.sh -c resume -m 34254 -e 42500 -p 789890
This utility sends async message to the TIBCO MDM server to restart the specified process. Check elink logs for execution or any errors.
TIBCO® MDM Release Notes 42
Key Summary
CIM-18355 A constraint with the Access action of rulebases was not working for the Mass Update operation.
CIM-18354 When the error link was clicked multiple times in the Basic Mode of the Mass Update screen, the error message was not updated.
CIM-18353 On the migrated version (from 8.2.1 to 8.3.1) of TIBCO MDM, adding related records was not possible.
CIM-18352 While searching records on the Mass Update screen, the previously searched records were not displayed in the search result.
CIM-18351 It was not possible to sort records by clicking the column header on the Mass Update screen. The attribute was specified using the Select action with the enumeration constraint in the rulebase.
CIM-18350 The pagination on the Mass Update screen (Basic Mode) for the Changed Records List did not work correctly when the page size was changed in the Items per page drop-down list. After clicking the next page icon, the first page was displayed.
CIM-18349 The Cipher not initialized exception was thrown in a highly concurrent environment.
CIM-18347 A reverse relationship was specified in the rulebase in many to one direction. Sometimes duplicate relationships were loaded into the bundle. Due to this, the rulebase execution failed.
CIM-18345 The rulebase validation of converting True or False to Yes or No values was not applied to the Category Specific Attributes on the Classifications tab. This issue occurred after navigating to the next page.
CIM-18344 The SaveRecord activity failed with a transaction timeout error when the record bundles included huge records.
CIM-18343 The event status changed from START to INPROGRESS in a workflow with the Async activities.
CIM-18339 The Record Query web service with command qualifier as valid values failed when the record being queried contained a multivalue attribute and one of the values included ampersand (&).
CIM-18335 The SpawnWorkflow activity is enhanced to control the record sequencing at the activity level.
CIM-18282 An error occurred while importing metadata.
CIM-18309 The synchronization event failed with the Java Null Pointer exception in the ConvertRecordToOutput activity.
CIM-18260 The context variable passed in the Record Modify web service request was not available while executing the rulebase.
TIBCO® MDM Release Notes 43
Key Summary
CIM-18248 On the record UI, a Boolean attribute showed TRUE and FALSE values in the drop- down list even though the showoninput property in the rulebase action was set to display YES and NO values.
CIM-18238 The configuration of change notification for records and repositories was modified to support the wildcard character * instead of regular expressions.
CIM-18178 A stale data error occurred if the effective date for the latest relationship was older than the previous version and the repositories were not FED enabled.
CIM-18166 The hyperlink was not displayed properly for the string attribute on the View Record screen.
CIM-18155 The Record Query web service executed with a negative integer value for the RECORD_VERSION key. the latest version of the records was returned instead of displaying an error message.
CIM-18129 When the relationship was configured to display as a tab and newrecord.xml was configured to generate PRODUCTIDs in sequence for a child repository, the PRODUCTID was not generated.
CIM-18122 For the SQL server, the Load Relationship mode of the database loader failed to establish relationships when the RecordIDExtension value was empty.
CIM-18120 For the SQL server, modifying records using Database Loader failed when the RecordIdExtension value was null and it created duplicate PRODUCTKEY entries.
CIM-18118 A performance issue occurred while loading the relationship tree in Record UI.
CIM-18116 For the SQL server, the MatchRecord activity failed intermittently as the related records were not loaded.
CIM-18101 If the repository and relationship names were similar, the Output Map tab was not displayed for the selected relationship.
CIM-18092 The Clear record cache on update configuration property caused caching issues if its default value was changed from false to true.
CIM-18078 On deleting a record using the Delete Record web service, the event log did not display the correct user information.
CIM-18060 An SQL exception was shown if the length of a variable specified in the rulebase exceeded 10 characters if using softlink.
CIM-18000 A null pointer exception was shown when merging a record that contained a file type attribute.
CIM-17980 The Process Comment History column of a work item approval screen did not display the last name of a user.
TIBCO® MDM Release Notes 44
Key Summary
CIM-17973 The size of the customized drop-down field created using the select clause was not similar to the size of other text boxes on the record UI.
CIM-17968 The dynamic web services returned fault messages when an existing PRODUCTID was specified in the request file.
CIM-17941 The Get Event Details web service returned an error message for some event logs.
CIM-17939 A work item was closed. Later, the values were specified for the newly created attributes in a repository. When viewing a closed work item, the new repository attributes' values were not displayed. This issue occurred due to the incorrect updation of the distributed cache.
CIM-17933 TIBCO ActiveSpaces 2.1.2 version support needed to use the security policy files.
CIM-17926 The web service to modify a related record incremented the record version of the parent record even though the parent record was not modified.
CIM-17901 While downloading the .docx file from the File type attribute on the View Record page, the file opened as a .zip file.
CIM-17899 The user was able to modify a record that was currently in a workflow and its latest work item was in the Time-out state.
CIM-17898 Two work items were generated and their links were sent in an email notification. Accessing the first work item from the link and modifying the record was possible. However, when the second work item link was accessed and the Save button was clicked after modifying the record, a Java Nullpointer exception was displayed.
CIM-17897 The OutDocument generated by the GetRecord activity did not contain the RelationshipData section.
CIM-17896 When a rulebase with hide, view, or modify access mode was applied and the user- defined position was specified for attributes, the attribute columns were not displayed in the correct position on the Browse and Search screen.
CIM-17895 When the Record Modify web service request was executed without changing any data, and the repository had one of the attributes of type DATE, the response did not return the Data unchanged, request ignored error message.
CIM-17864 In the Record UI, the warning message was not displayed for parent and related records with or without Relationship as a tab.
CIM-17848 For a record, if a rulebase was invoked with a warning or information message, when you clicked the Save and Process button, the record was not saved.
CIM-17842 A rulebase was defined with the valid values (select action) for multiple boolean attributes. In that case, values of the attributes were not shown correctly on Browse and Search and View Record screens.
TIBCO® MDM Release Notes 45
Key Summary
CIM-17804 While executing the Record Query web service, the rulebase context variable RECORD_ACTION was evaluated as EDIT instead of VIEW.
CIM-17801 A custom link was needed under the Login button of the Login page. The Alerts.txt file based customization for Login UI did not work.
CIM-17785 The certification of JBoss EAP 6.2 version was required with the TIBCO MDM 8.3.2 version. The support of JBoss EAP 6.2 version has been dropped from the release 9.0.0.
CIM-17739 After assigning a separate security permission to each repository for different roles, importing permissions.jar failed with the following exception: ORA-01795: maximum number of expressions in a list is 1000.
CIM-17648 The DataService element specified in the MasterCatalogRecordAction operation missed the namespace definitions in the error response.
CIM-17647 The "code" attribute was defined as a mandatory attribute of ResultType in the Common.xsd file. However, the results returned by a web service did not always contain the "code" attribute. This caused a validation error.
CIM-17646 The special characters, such as hyphen (-), ampersand (&), and dollar ($) defined in regular expressions of a rulebase file did not work. The issue occurred on the combination of the Linux operating system and WebLogic Application server.
CIM-17645 Even though the com.tibco.cim.optimization.recordbundle.load property was set to false, the MergeRecord activity took longer to load and process all related records.
This has been fixed but the fix is not applicable when rulebase is used in the MergeRecord Activity.
CIM-17644 When the record bundle contained a cyclic relationship, clicking the Compare link from a work item caused a server crash with a StackOverflow exception.
CIM-17643 If TIBCO Collaborative Information Manager was running on the Oracle database, a performance issue occurred while loading the relationship UI.
CIM-17641 If the record contained two existing related records and the RecordModify web service was executed without any data change, the records were modified and their versions were incremented. However, the following error message was not displayed: Data unchanged, request ignored.
CIM-17638 After modifying any related record and returning to the root record screen, the relationship hierarchy collapsed. To access the related record, the relationship hierarchy needed to be expanded again. Limitation: After removing the child record of a relationship, the expanded child records pertaining to that relationship collapsed.
CIM-17637 When a record was in the REJECTED state, it was not updated in the Netrics list. This resulted in duplicate detection in the MatchRecord activity.
TIBCO® MDM Release Notes 46
Key Summary
CIM-17636 While creating or modifying records, usability issues occurred with the drop-down fields on Mozilla Firefox.
CIM-17635 While merging records from a work item, the AllowMergeAttributeList or SkipMergeAttributeList parameter specified in the MergeRecord activity was not considered for merging or skipping.
CIM-17634 The SaveRecord activity was specified to save the derived values specified in the Evaluate Rulebase activity and a dummy rulebase was passed. However, the constraint specified in the catalogvalidation.xml file was executed instead from the dummy rulebase. To resolve this issue,
1. The ApplyValidation parameter was added to indicate whether or not to execute the catalogvalidation.xml file. 2. The configuration property - Enable standard validation execution in SaveRecord activity (com.tibco.mdm.optimization.saverecord.rulebaseoptions) was added to apply validation on incoming records.
CIM-17629 On the View Record screen, when the Modify link was clicked, the access mode=view_record constraint of a rulebase did not work.
CIM-17628 A conflict occurred when the same record was modified and viewed by the concurrent users. The event remained in the 'In Progress' state with no event details. To resolve this issue, remove the 'In Progress' events by using Purge in the Event mode. After successful record modification, the 'Record Modify' events are displayed with the detailed steps on the Event Details page.
CIM-17627 After resubmitting an event, the PARENTID column in the Event table was not populated correctly.
CIM-17626 Customization of grid data was not possible using the customInit function. An external link that was added to the Modify Record or View Record screen did not work. To resolve the issue and to manipulate the data retrieved in the grid table, specify customUpdateTable function in the customInit.html file.
CIM-17625 The Record Modify web service was executed for a record whose latest version was rejected. After viewing the Review page on the record's work item, the record's rejected version was displayed instead of the previous confirmed version in the old value column.
CIM-17620 The context variable passed in the Record Modify web service request was not available while executing the rulebase for related records.
CIM-17618 On the Merge Record Details screen, the Add as new check box was disabled for related records because the relevant records were not retrieved correctly. This issue occurred on Microsoft SQL server.
CIM-17617 The context variable passed in the GetWorkitem web service request was not available while executing the validation rulebase for a record in the work item.
TIBCO® MDM Release Notes 47
Key Summary
CIM-17616 The comments provided by the previous user in the work item were not retrieved for the current user's work item using the GetWorkItem web service. This issue occurred when workflow included multiple subflows and the work item closed in subflows.
CIM-17615 The following issue occurred while deploying the Propagate-Rulebase action from TIBCO MDM Studio: The path of a rulebase file in the deployed rulebase XML file pointed to a .rul file instead of an .xml file and to the path in TIBCO MDM Studio instead to the relative path in $MQ_COMMON_DIR.
CIM-17614 The SaveRecord activity did not save the records, whose latest version was in the REJECTED state and if there was no data change from the REJECTED version.
CIM-17613 An error message was displayed after clicking the Configure link on the Mass Update screen.
CIM-17612 The RelationshipData element was intermittently missing from the output document of the GetRecord activity.
CIM-17611 When the parent and child records were deleted and later added through the SaveRecord activity, the relationship was not established between the parent and child records.
CIM-17610 A match and merge work item was created for a three level record hierarchy. In this case, if the Add as New check box was selected for the third level record and attributes of the root record were merged, third level records which were Accepted as new were not merged into the target record hierarchy.
CIM-17609 If multi-level record hierarchy was merged in the work item, the MergeRecord activity did not generate the OutDocument for Target records. To fix this issue, add the MergeTargetInOutdoc parameter in the MergeRecord activity. For example:
CIM-17608 On the Modify Record screen, check constraint-based validation displayed validation errors on all the related records even when only one of the related records contained a validation error.
CIM-17607 When the Record UI was customized for relationship as a tab using the recordui- render.xml file, the relationship Resource Security permissions were not applied to toolbar operations.
CIM-17606 A nullpointer exception was thrown, when the MergeRecordUsingLegacyProcess parameter was set to true, and the source and target record keys were specified in the MergeRecord activity.
CIM-17605 The Record Modify screen was refreshed when the Tab was pressed from a drop- down list attribute and no change was made to the value of the drop-down list attribute.
TIBCO® MDM Release Notes 48
Key Summary
CIM-17604 The recorduirender.xml was configured to display a relationship as a tab and a validation rulebase constraint was set to specify the record ID of the related record as 'view only'. In this case, when the root record was modified and the Relationship tab was browsed, modifying the record ID of the related record was possible even though the constraint was set as 'view only'. To set a default column to be sorted in the customized related record list (relationship as tab), add the following property in Configurator (Tools > Add Configuration Value):
● Configuration value name: Sorting ● Internal name: com.tibco.mdm.
● Version: 8.3 ● Visibility: Advanced ● Description: For sorting columns in relationship as tab, based on attribute name. ● Current Value: PRODUCTID ● Default Value: PRODUCTID ● Category: UI Settings
1. Currently, the default column sort is not supported for the relationship attribute name. 2. Specify any attribute value for the Current Value and Default Value fields.
CIM-17603 The Text Search web service requests did not work when authentication details were provided using jsessionid.
CIM-17602 On the View Record screen, the Modify and Delete links were displayed even for the previous unconfirmed version of a record. This issue occurred on TIBCO Collaborative Information Manager on the 8.2.0 version. Currently, the Delete link has been removed from the View Record screen.
CIM-17474 Using the Role Delegation feature, when a role delegation was set for one of the custom roles (R3) out of the five custom roles (R1 ,R2, R3, R4, and R5); after saving only four custom roles ((R1 ,R2, R3, and R5) were shown in the role delegation list. In this case, if delegation was allowed to the same role (R3), the next child role (R4) was ignored and not displayed in the list.
CIM-17360 Unable to deploy the nested rulebases on the TIBCO MDM server when creating them in a new folder other than the common folder.
CIM-17334 A nullpointer exception was thrown, when the MergeRecordUsingLegacyProcess parameter was set to true in the MergeRecord activity.
CIM-17304 While creating or modifying records, usability issues occurred with the drop-down fields on Mozilla Firefox.
TIBCO® MDM Release Notes 49
Key Summary
CIM-17298 When the work item was closed, the Closed By column displayed the member ID of the person creating the work item rather than the member ID of the person closing the work item.
CIM-17277 Using direct merge, the relationships records were not merged from the source record to the target record in the MergeRecord activity.
CIM-17258 An incomplete rollback script was generated with the database loader for the load relationship mode.
CIM-17220 On the Modify Record screen, check the constraint based validation on related records displayed validation errors on all the related records even when only one of the related records contained a validation error.
CIM-17132 Unable to purge data using the PostgreSQL database.
CIM-17021 The Add as new check box on the Merge Record Details screen did not work for multiple child relationships available at the first level relationship. The source records of one relationship were merged into the target records of another, instead of adding a new relationship.
CIM-16904 The Get User List web service did not return the email address and phone number in the response.
CIM-16874 Web service requests with limited resource security permissions (for example, Support Engineer role) threw a warning instead of an error, and returned a success count.
CIM-16865 On rejecting records from the data quality match-merge work item, the status of the records displayed as Accepted and the record was approved instead of being Rejected.
CIM-16843 Conditional validation rulebase constraints did not work while using the recorduirender.xml file based recordui customizations.
CIM-16705 Documentation was missing for the following limitation to be mentioned in TIBCO MDM Workflow Reference: The EvaluateChildren parameter in the EvaluateRuleBase activity only works if a record list is passed and not when a document is passed.
CIM-16653 If the LDAP users had a password as null, exporting and importing the users metadata resulted in a schema validation error.
CIM-16629 The repository attribute defined as 500 characters restricted the user to enter only 251 characters. This issue occurred in the Mozilla Firefox browser.
CIM-16513 The French and German language packs were required for the TIBCO MDM 8.3.0 version.
TIBCO® MDM Release Notes 50
Key Summary
CIM-16485 During the migration of TIBCO MDM from the version 8.2.1 to 8.3.0, the CacheConfig.xml file of the 8.3.0 version was overwritten by the CacheConfig.xml file of the 8.2.1 version.
CIM-16359 In the relationship tree pane for a parent record, only ID-IDEXT attributes were displayed.
CIM-16351 The Duration column of the Event Log page showed 0 Seconds for all events.
CIM-16349 The database loader import with the loadRelationship mode did not create relationships on the Microsoft SQL server, when records involved did not have PRODUCTIDEXT attribute populated.
CIM-16209 An incremental deployment of the repository metadata deleted resource security constraints on relationships.
CIM-16160 An error occurred during the workflow execution, and records remained in the UNCONFIRMED state.
CIM-15855 The configuration of the Web UI affected the web service API.
CIM-15825 After clicking Save on the Add Record screen, the Record Add event remained in the In Progress state instead of Success.
CIM-15664 While exporting records using synchronization for self relationships, a child record appeared twice in the exported output file.
CIM-15628 An enhancement for the Rollback feature was requested.
CIM-15606 The Search functionality in the TIBCO MDM 8.3.0 documentation Web Help did not work properly.
CIM-15536 An error occurred when a future effective date parent record was created with a future effective date child record from the reverse relationship.
CIM-15434 Chnaging the display name of a reverse relationship in the SharedStringResources.properties file for the self relationship was not possible.
CIM-15411 With large data models, configuring the Browse and Search with certain attributes (record state), led to a severe browser slowdown.
CIM-15342 In Export Records (Synchronization), a relationship attribute file without any data might have been created, even though the relationship was not defined in the synchronization profile.
CIM-15311 The attributes shown in the search results of text search did not match the available or selected attributes of the Attributes section in the Configure window.
TIBCO® MDM Release Notes 51
Key Summary
CIM-15252 During the record duplicate detection process, after clicking Accept As New or Reject on the Merge Record screen, nothing happened. The issue occurred on Internet Explorer due to the "sensitivities" to the html or Javascript code as provided in DQMergeUI.html.
CIM-15159 An exception was thrown when MigrateRules.bat was executed with an option migrateCustomProcesses. The issue occurred while migrating TIBCO MDM from the 8.2.1 to 8.3.0 version.
CIM-14796 When the NOTIFICATION framework sent data on the notification queue for FED records, the action tag was evaluated to null.
CIM-14721 An error occurred while creating an input map with the multivalue attributes. The Fresh Data check box was selected and all attributes were mapped with the respective values in a data source.
CIM-14434 Login did not work for the RETAILER type enterprise, when Site Minder login handler was used with TIBCO Collaborative Information Manager.
CIM-14317 An enhancement was requested for attribute with the data type URL to show the hyperlink when records are viewed.
CIM-14200 The all records export did not export all of the relationship records, and sometimes the latest version of relationship attributes also did not get exported.
CIM-14193 When timed out notification work item was submitted, the status of the work item was set as CLOSED_PENDING and shown as "Close Initiated" instead of "Closed".
CIM-14083 Slow running query with the CheckRecordState activity impacted record add, modify, and delete workflow performance.
CIM-14081 When the LDAP referral context was set to FOLLOW, an error occurred while logging into TIBCO MDM with an LDAP user. An enhancement for the configuration option was requested. The configuration property com.tibco.cim.ldap.contextReferral was provided.
CIM-13999 Queries would run slow when searching records using the Microsoft SQL server, due to usage of the custom function IN_LISTSTR.
CIM-13905 The Classification Scheme UI tree did not maintain the state and moving between pages could collapse the tree.
CIM-13881 Even if the relationship does not have a modify permission, modifying the related record was possible while modifying a parent record.
CIM-13781 Incorrect search results displayed on the Browse and Search screen. This issue occurred intermittently.
CIM-13752 While viewing a list of related records from the Relationships tab of the View Record or Modify Record screen, adjusting the width of a column was not possible.
TIBCO® MDM Release Notes 52
Key Summary
CIM-13736 The response of the ValidValuesInit command qualifier was not validated with MasterCatalogRecord_Action.xsd.
CIM-13711 An enhancement was requested for the EndEffectiveDate attribute. However, an option was available while modifying the future effective date record whether or not to create a new version of the record or change the date of an existing version.
CIM-13571 If the number of records was large, the pagination on the merge work item did not work for bulk import of records.
CIM-13495 The custom TO_DATE function used in the record search query caused a performance issue for the Microsoft SQL server.
CIM-13280 The default value setting for normal and multivalue timestamp attribute was not consistent.
CIM-13036 The merge record using the legacy process was not working as expected.
CIM-13020 When the record modify web service request was executed without changing any data, a work item was created instead of displaying an error message: Data unchanged, request ignored.
CIM-12911 On the Browse and Search screen, when the column header was clicked to sort the records, the record list was not updated even though the page number continued to increment.
CIM-12876 If the novalue="option" condition was defined for the drop-downconstraint in a rulebase, the drop-down list did not show the default value as the first item in the list.
CIM-12683 The EQ comparison operator used in a rulebase did not work properly. While adding a record, the validation did not work if an uppercase
CIM-12522 An enhancement was requested to delete all records of a repository before importing data.
CIM-12421 When using the DropTempTables parameter of the ExtractDataToDelimitedFile activity, the temporary tables were not removed.
CIM-12229 The SQL/where clause did not work in the propagation rulebase.
CIM-12097 The synchronize feature did not detect incrementally added relationships and did not publish the added relationships in the output.
CIM-12079 Explicit dates in a rulebase could have resulted in an error for several date formats.
CIM-11973 In the Record Add web service response, the date was not returned based on the date format selected in the user profile.
TIBCO® MDM Release Notes 53
Key Summary
CIM-11829 An enhancement was requested to generate a single output file for repository and relationship attributes in synchronization.
CIM-11817 The drop-down and view only constraints did not work in a relationship catalog validation.
CIM-11679 For the multivalue attribute field, viewing all values was not possible using the scroll bar.
CIM-11674 The locale date format (DD/MM/YYYY) set for a user was not applied. After selecting a date in the Date field, the date picker displayed the American date format, that is, MM/DD/YYYY.
CIM-11651 While adding a record to the repository, some date formats were not accepted for date data type. Using the UI, the only supported date format was MM/DD/YYYY. For a custom date format from the locale setting of the user profile, for example, DD/MM/YYYY, the same format was available from the UI, but not supported by the web service.
CIM-11449 Importing metadata with the multivalue attribute inserted 'null' as a value in the multivalue field.
CIM-11432 The wrong path was set for thelog4j.jar and jms.jar files in the cpath.sh shell script. This caused an exception after running the datacleanup.sh utility.
CIM-11217 The work item notification email was sent only to the first email address when a user account was configured to have more than one email address.
CIM-11202 The Compare Record Activity did not return the relationship change information.
CIM-11103 If the drop-down lists were configured to display one below the other, the values of the drop-down lists were not shown properly on the Browse and Search page.
CIM-10948 When the record was in a workflow, the Record Query web service returned both the confirmed and unconfirmed versions of a record.
CIM-10901 A rulebase was configured to hide the PRODUCTIDEXT attribute. However, the description of PRODUCTIDEXT was still visible on the Add Record, Modify Record, and View Record pages.
CIM-10760 If a CSV-based data source had line breaks within a field value, the upload did not work correctly.
CIM-10546 The RECORD_ACTION context variable was not evaluated correctly during the import of new records to a repository.
CIM-10447 The Save and Process and Save buttons did not appear on the validation page when only warning or information messages were generated by validation. This has been fixed. The Relationship tab is now visible in a read-only mode if 'Save with errors' permission is denied to the user. For any modifications in the record or relationship the user has to go the back to the Add Record or Modify Record page.
TIBCO® MDM Release Notes 54
Key Summary
CIM-10214 The command-line utility Purge was provided to delete records from the repository and delete metadata, such as, repository, data source, synchronization format, and so on.
CIM-10186 Unless the relationship names were specified in the Evaluate Subset activity, the synchronization workflows did not export related records.
CIM-9993 For the Record Modify web service, the following two issues occurred:
● A new version of the parent record was created even if only the child record was modified. ● A new version of the parent record was created even though neither the parent nor the child record was modified.
CIM-9980 The connection from TIBCO MDM to fault tolerant EMS failed when authorization was set to enabled in the tibemsd.conf file. The connection worked fine when the authorization was set to disabled.
CIM-9974 If the data source contained only a single record, an error occurred at the MatchRecord activity during out-of-the-box split /approval data quality import workflow.
CIM-9956 If drop-down rulebase with spaces in the drop-down options was applied on a repository and if nothing was changed after the Apply operation on the Mass Update page; then an asterisk (*) character was not shown against rows. The issue occurred on GI-based mass update.
CIM-9884 Unable to hide attributes from the record headers.
CIM-9860 A forward relationship was established between two repositories. While viewing a record from a repository using the reverse relationship and while adding a record between the reverse relationship, the latest version of a record from another repository was not available.
CIM-9372 An enhancement was requested to create an output map for the reverse relationship and without mentioning the relationship name in the synchronization workflow.
CIM-9359 When a relationship between a parent and child record was removed from the child record, the following validation error was displayed:
No Record Exists. Please change record ID or Record ID extension.
CIM-9167 Unable to remove all configured relationship attributes in the Search section using the Configure link on the Browse and Search screen.
CIM-8987 An enhancement was requested to have the same display name for multiple attributes even though the attributes belonged to different attribute groups.
CIM-8973 An enhancement was requested to make the attributes conditionally editable and associate with a data source.
TIBCO® MDM Release Notes 55
Key Summary
CIM-8944 A null pointer exception was shown when the UnZipFile command was used with the ExecuteExternalCommand activity to decompress the file in the synchronization workflow.
CIM-8928 The MergeRecord Acitivity did not merge with the latest version of a record as expected, when a record in the matcher work item was modified.
CIM-8920 The UpdateRecordState activity did not work as expected, when a series of evaluate rulebase activities were used along with a work item without the StateTransition activity.
CIM-8645 When records with a relationship were imported without mapping relationship attributes, and a record query web service was executed to return relationship data of an imported record, the relationship attribute section did not appear in the response file.
CIM-6365 A performance issue occurred while loading the Relationship tab on the View Record screen.
CIM-6181 Using the & (ampersand) character on the Browse and Search screen (database search) might have lead to losing the original search results.
CIM-6062 The SaveRecord activity failed if the number of records to be updated were more than RecordPerAsyncCall and AsynProcessIndicator was set to true.
CIM-4806 For a record query web service request, when a custom outputmap was used, a security exception was thrown.
CIM-3471 An enhancement was requested to allow the copied synchronization formats to be edited.
CIM-3321 When the date format DD-MM-YY was specified in the Record Query web service request file, an error message was displayed.
TIBCO® MDM Release Notes 56
Known Issues
The table lists the known issues in version 9.0.0 of TIBCO MDM.
Known Issues
Key Summary
CIM-22757 Summary: The command line utility datacleanup.bat/sh did not clear an enterprise in a single attempt. Workaround: Run the utility multiple times. For example, ./datacleanup.sh -o repository -a
CIM-22711 Summary: After incremental deployment, a null pointer exception occurs on creating a record. Workaround: In the case of incremental deployment of metadata, if the following operations are performed on any repository having perspectives, you must select those perspectives while importing the metadata:
● Deleted related repository and repository attributes ● Updated relationships
CIM-22666 Summary: Exporting output maps is not supported through the export wizard UI. Workaround: Export Meta Data through files.
CIM-22655 Summary: With Data Quality merging, the relationship attributes do not get merged during the direct merge. Workaround: None.
CIM-22633 Summary: For workitem sorting, Postgress database does not support ordering on record attributes. Workaround: None.
CIM-22622 Summary: If the version is not specified in the precedence rulebase, an error is thrown. Workaround: Specify the version.
CIM-22611 Summary: In the Merge UI (Manual Merge and WorkItem Merge) the drop-down lists are not editable. Inline editing is disabled. Workaround: None.
CIM-22584 Summary: On the Event Details page, the event shows Record Modify when this should be shown as Merge Record. Workaround: None.
TIBCO® MDM Release Notes 57
Key Summary
CIM-22573 Summary: The 'S' hint character does not skip the RECORDSYNCLOG table during the purge as expected. As soon as the data is deleted from the PRODUCTKEY table, ON DELETE CASCADE referential action for a foreign key deletes data from the RECORDSYNCLOG child table. Workaround: None.
CIM-22516 Summary: Subset rule with a list option throws an error when the datasource attribute of a type other than string is used in the filter criterion with a non-string attribute repository. Workaround: Use the string attribute in the datasource.
CIM-22494 Summary: Unable to add more than one display attribute for job policy. Workaround: None.
CIM-22478 Summary: With data quality merging, when multiple child records are incoming with the source record, only one of them is added to the target record bundle. Workaround: None.
CIM-22477 Summary: The EvaluateRuleBase activity with SaveFlag=NOSAVE and the rulebase modifying record using the ASSIGN action causes the modified record data to get cached without it being saved into the database. Workaround: Clear the record cache entry to make it consistent with the database entry.
CIM-22436 Summary: Errors are received if Time Format and Timestamp Format in Locale Settings contain the AM/PM format. Workaround: Use formats without AM/PM when selecting time formats. For example, use hh:mm:ss instead of hh:mm:ss AM/PM
CIM-22354 Summary: Related records are not loaded on Internet Explorer 11 after using the globalized data. Workaround: None.
CIM-22345 Summary: Rollback for corrected record version does not rollback manual classification. Workaround: None.
CIM-22333 Summary: Event rollback does not work correctly when future dated records are modified by changing the effective date. Workaround: None.
CIM-22326 Summary: EvaluateRulebaseActivity with CatalogValidation=true used for root catalog validation is applied to all records in a bundle. If the attribute names are the same across repositories, some side effects are seen.
Workaround: When executing CatalogValidation, set EvaluateChildren=true in the EvaluateRulebase activity.
TIBCO® MDM Release Notes 58
Key Summary
CIM- 22252 Summary: Rollback of correction does not work correctly when relationships need to be reverted. Workaround: Manually revert the relationship using database queries.
CIM-22141 Summary: The standard and velosel folders get created in the$MQ_HOME/common folder even though the customized path is given while installing TIBCO MDM. Workaround:
● Update the value for the $MQ_COMMON_DIR environment variable or
● Copy the standard and velosel folders from the $MQ_HOME/common folder to $MQ_COMMON_DIR
CIM-22061 Summary: Synchronization gets a java.lang.StackOverflowError error in the CreateOutputFile activity. The CIM 7x Synchronization output format for exported data representation is no longer supported from TIBCO MDM 9.0.0 release and later. Workaround: None.
CIM-21645 Summary: FILE type attributes are not supported with Precedence Management. Workaround: None.
CIM-21628 Summary: In data quality (manual merge and merge from workitem), rulebase does not work with the child repository attribute and relationship attribute if the child record is not modified. Workaround: None.
CIM-21537 Summary: Propagate action is not supported in Parallel Execution. Workaround: None.
CIM-21522 Summary: When running the ./netricsServer.sh on a Solaris machine, an error is thrown, as ./netricsServer.sh: SCRIPT_MODE=-startServer: is not an identifier on a Solaris machine.
Workaround: Run the same command as bash netricsServer.sh -startServer.
CIM-20900 Summary: The Correction action is available on the View Record page that is navigated from the Import Browse page using the link in the import event or import approval work item. Workaround: None.
CIM-20873 Summary: When a record version is corrected multiple times using the Correction action, the Version History page shows an incorrect name for the member who modified or corrected that version. All rows on the history page for that version shows the name of the member who corrected it last. Workaround: None.
TIBCO® MDM Release Notes 59
Key Summary
CIM-20807 Summary: With data quality match and merge work items, the showoninput tag with validation rulebases does not work correctly. Workaround: None.
CIM-20801 Summary: Instead of browser-based drop-down lists, some pages on the UI display custom drop-down lists for the pagination bar. Workaround: None.
CIM-20578 Summary: In SiteMinder, if the context path is changed in the UI screens, it refers to the absolute path and an error occurs. Workaround: None.
CIM-20426 Summary: Special characters, such as the forward slash (/) and back slash (\), are not permitted as part of the index entity names. Workaround: None.
CIM-20165 Summary: When using the Correction action to remove a relationship and then another item correction request to create the same relationship again, it does not create the relationship. Workaround: None.
CIM-19745 Summary: For text search, when reducing the similarity score to less than 0.4, no records are displayed. Workaround: None.
CIM-19704 Summary: The hot deployment feature does not work as expected in the case of customization of the landing page. Workaround: None.
CIM-19499 Summary: On the record UI, the customized renderer loses selection if the page is refreshed. The customization includes a display drop-down list with the radio button for an attribute and the ShowAsRadio constraint. Workaround: None.
CIM-19298 Summary: Changes made to records on the Mass Update screen are not updated on the View Record screen. Workaround: Use independent navigation to check the records.
CIM-19293 Summary: Merging of two records with a multilevel classification scheme and the category specific attributes does not work in specific cases. Workaround: None.
CIM-19256 Summary: The Detected Old installation window is not displayed when you select the Migration option in Configurator to migrate from the older version to the 8.3.2 version. Workaround: Migrate manually by entering the old version and home directory.
TIBCO® MDM Release Notes 60
Key Summary
CIM-19201 Summary: The record attribute modification is not updated on the record UI, if the record attributes are edited first, followed by the classification scheme. Only the classification scheme modification is updated. Workaround: None.
CIM-19174 Summary: If com.tibco.mdm.clipassword.enable is not specified in the ConfigValues.xml file, the –pwd and -epwd inputs to purge command-line utility ignores the -pwd parameter and purges the record with the remaining criteria. Workaround: None.
CIM-19037 Summary: The UI search with the Check Existence drop-down list does not work correctly, if second level relationships are involved. Workaround: None.
CIM-18893 Summary: The Process Comment History section is not available on the Import Approval work item screen with the corresponding business process rule. Workaround: None.
CIM-18869 Summary: The "ORA-00933: SQL command not properly ended" exception occurs when slice action is used with the datasource and the datasource name has a hyphen (-) character. Workaround: None.
CIM-18222 Summary: The File type attribute with multivalue option displays an error while downloading the record file. Workaround: None. Do not use multivalue file type attributes.
CIM-18221 Summary: The Modify web service with Version_Policy=Correct can correct the UNCONFIRMED record version to make it CONFIRMED. The existing STATE and new STATE are different, and therefore, this is invalid based on the correction version policy. Workaround: None.
CIM-17684 Summary: The special characters are not displayed correctly in the Configure window of the Mass Update screen. Workaround: None.
CIM-17679 Summary: The Update Synchronization Status and Send Response options are not available on the new record UI. Workaround: None.
CIM-17663 Summary: The NOT IN operator only supports string types. The other types are not working correctly. Workaround: None.
TIBCO® MDM Release Notes 61
Key Summary
CIM-17394 Summary: The PARENT keyword does not work correctly in the relationship CatalogValidation.xml when the relationship is displayed as a tab using record-render.xml. Workaround: None.
CIM-17214 Summary: The PARENT rulebase context variable is not evaluated correctly when the related record is added using the reverse relationship. Workaround: None.
CIM-17116 Summary: Purge is not invoked from the command line for the metadata mode using the following options:
● -r repositoryid ● -ds datasourceid ● -m memberid Workaround: IDs are no longer preferred. If you use an ID, specify the enterprise name or an ID as an additional input.
CIM-16963 Summary: MQ_COMMON_DIR is empty when TIBCO MDM is installed using the Silent Installer and even after specifying false for the commonConfig_useDefault key and the correct path for the commonConfig_directory and tibco.cim.common.dir keys. Workaround: None.
CIM-16893 Summary: The uncategorize action based on a number of classification code paths does not work consistently. Workaround: None.
CIM-16844 Summary: The scheduler duplicate detection process does not work correctly if the two indexes share the same repository name as the primary or parent, that is, a single repository with IndexEntity joinTable="false" and a cross-repository with IndexEntity joinTable="true" index. In this case, overlapping indexes, records from matching child records from the cross-repository index are also returned. Workaround: None.
CIM-16651 Summary: An incorrect number is displayed in the Number of Matching Records column for all the records listed in the work item. This occurs if more than one record is being imported during the MatchRecordWorkItemBulk activity within the data quality import workflow. Workaround: None.
CIM-16548 Summary: Controlling the list of relationships displayed in the upper-left relationship window using RELATIONSHIP_LIST is no longer dynamic. Workaround: None.
TIBCO® MDM Release Notes 62
Key Summary
CIM-16530 Summary: The indexed attributes in the IndexerConfig.xml file are not automatically updated when the attribute name is changed, and the repository is incrementally deployed.
Workaround: Edit the attribute definition in the IndexerConfig.xml file.
CIM-16471 Summary: With the data quality match and merge workflow, while having the source record merged with a target record through DirectMerge (the source record has only one target match candidate record), if the source and target records have different related records, the related record for the source record does not get merged to the target record in spite of having the ImplicitRelationshipMerge parameter set as true in the DirectMerge activity. Workaround: None.
CIM-16348 Summary: With LDAP integration in TIBCO MDM, an auto authentication of the user mapping does not work correctly, if a user has multiple external roles mapped to a single internal role in the rolemap.prop properties file. Workaround: None.
CIM-16209 Summary: An incremental deployment of the repository metadata deletes resource security constraints on relationships. Workaround: Redeploy the relationship security after an incremental update.
CIM-16021 Summary: The ManageRecordCollection activity bundles all the records in the workflow as opposed to the records which are part of the InRecordlist passed. Workaround: None.
CIM-15732 Summary: The Record Query web service does not work when using the EFFECTIVEDATE relationship attribute in the Context variable. Workaround: None.
TIBCO® MDM Release Notes 63
Key Summary
CIM-15727 Summary: An exception is thrown while creating a work item for a large number of users in the specified Role. The exception occurs when formatting user names to display them in the Event log screen. Workaround: To avoid the exception and disable the formatting of user names, add the Formatting User Name property in Configurator (Tools > Add Configuration Value). Specifying the False value disables the formatting of user names. Enter the following details in each field:
● Configuration value name: Formatting User Name
● Internal name: com.tibco.cim.workflow.formatUserName
● Version: 8.2 ● Visibility: Advanced ● Description: Formatted user names are displayed in the Event log screen. By default, specify the True value. Setting this property to False disables the formatting of user names.
● Current Value: False
● Default Value: True
● Category: Workflows Limitation: Currently, the database schema supports only 8000 characters for stateparam in the Processstate table. The exception occurs if the combined length of user names and the process state exceeds more than 8000 characters. The fix does not remove this limitation.
CIM-14617 Summary: If the length of a relationship attribute is changed (from default to 512), the column length of the RELATIONSHIPATTRIBUTE (RCT) table is not altered even if the attribute length in the CATALOGATTRIBUTE table is updated. Workaround: Manually adjust the column length.
CIM-13744 Summary: For purge, when a shutdown is initiated while the purge is running in the background, exceptions occur on the application server console and elink.log. Also, the event state remains in progress. Workaround: None.
CIM-13144 Summary: The parameter value is overwritten to null, if you use an internal parameter of the same workflow in one activity having an input from the output parameter of another activity. Workaround: None.
CIM-13128 Summary: Emails sent from timed out work items are sent more times than expected. Workaround: None.
CIM-9701 Summary: Documentation is required to describe a list of mandatory conditions to be imported while customizing or creating a new business rule domain. Workaround: None.
TIBCO® MDM Release Notes 64
Key Summary
CIM-7708 Summary: A repository cannot be created with a name similar to the previously deleted repository name. Workaround: None.
CIM-4175 Summary: For purge, when a shutdown is initiated while purge is running in the background, many exceptions occur on the application server console and elink.log. Also, the event state remains Inprogress. Workaround: None.
CIM-2085 Summary: The Rulebase execution can happen more times than needed for editing a record. Workaround: None.
TIBCO® MDM Release Notes