TIBCO Collaborative Information Manager Release Notes · † TIBCO MDM Release Notes: Read the...

Two-Second Adv

TIBCO® MDM

Release NotesSoftware Release 8.3.2October 2014Document Updated: November 2014

antage®

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 TIBCO MDM INSTALLATION AND CONFIGURATION GUIDE) 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, Two-Second Advantage, TIB, TIBCO Adapter, Predictive Business, Information Bus, TIBCO BusinessConnect, TIBCO ActiveMatrix BusinessWorks, TIBCO Enterprise Message Service 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 © 1999-2014 TIBCO Software Inc. ALL RIGHTS RESERVED.TIBCO Software Inc. Confidential Information

| iii

Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v

Related Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viTIBCO MDM Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viOther TIBCO Product Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi

Typographical Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii

Connecting with TIBCO Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xHow to Join TIBCOmmunity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xHow to Access TIBCO Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xHow to Contact TIBCO Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x

Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

New Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2New Configurator UI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Decoupling of Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Purge Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3JMX Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Bundle Processing Lock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Text Search Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Resetting Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Inclusion of New Guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5FileWatcher Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5New Configuration Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Changes in Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Updates for Logo Change. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Updated Workflow Activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Updates New Configurator UI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Deprecated and Removed Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Deprecated Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Removed Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Migration and Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Upgrading to 8.3.2 Service Pack from 8.3.x . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Closed Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Known Issues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

TIBCO MDM Release Notes

iv | Contents


| v

Preface

TIBCO® MDM is a tool to manage the master data of your organization by providing a framework for governance, rules, and processes.

This ensures accuracy and efficiency both inside the enterprise as well as throughout the value chain so that multiple processes are optimally coordinated. TIBCO MDM delivers a multidomain horizontal platform to manage all types of information including products, customers, vendors, reference data, trading partners, and so on.

Topics

• Related Documentation, page vi

• Typographical Conventions, page viii

• Connecting with TIBCO Resources, page x


vi | Related Documentation

Related Documentation

This section lists documentation resources you may find useful.

TIBCO MDM DocumentationThe following documents form the TIBCO MDM documentation set:

• TIBCO MDM Release Notes: Read the release notes for a list of new and changed features. This document also contains lists of known and closed issues for this release.

• TIBCO MDM Installation and Configuration: Read this manual for instructions on site preparation, installation, and configuration.

• TIBCO MDM User’s Guide: Read this manual to learn the TIBCO MDM features. This manuals guides you to use the product. It describes the functionality as well as all the screens.

• TIBCO MDM System Administration: This manual explains features relevant to the system administrator.

• TIBCO MDM Customization: Read this manual to understand how the application can be customized to your enterprise needs.

• TIBCO MDM Workflow Reference: This manual is a reference for the automation of business processes.

• JAVA API Reference: This Help includes a list of workflows that are used in TIBCO MDM.

• TIBCO MDM Web Services: This manual is a reference for using web services.

• TIBCO MDM Best Practices Guide: This manual provides the best practices based on contributions from the users of TIBCO MDM, who develop the software and implement it in a variety of TIBCO MDM projects.

• TIBCO MDM Performance Tuning Guide: This manual provides the performance tuning methodologies to tune your system and to achieve the optimal system performance on all of the layers of TIBCO MDM.

Other TIBCO Product DocumentationYou may find it useful to read the documentation for the following TIBCO products:

• TIBCO MDM Studio Installation Guide: Read this manual for instructions on installation of TIBCO MDM Studio.


Preface | vii

• TIBCO MDM Studio Process Designer User’s Guide: This guide is a reference for designing workflows using the TIBCO MDM Process Designer graphical user interface.

• TIBCO MDM Studio Process Designer Tutorial: This guide is a tutorial for designing workflows using the TIBCO MDM Process Designer graphical user interface.

• TIBCO MDM Studio Repository Designer User’s Guide: This guide is a reference for designing repositories using the TIBCO MDM Repository Designer graphical user interface.

• TIBCO MDM Studio Repository Designer Tutorial: This guide is a tutorial for designing repositories using the TIBCO MDM Repository Designer graphical user interface.

• TIBCO MDM Studio Rulebase Designer User’s Guide: This guide is a reference for designing rulebases using the TIBCO MDM Rulebase Designer graphical user interface.

• TIBCO MDM Studio Rulebase Designer Tutorial: This guide is a tutorial for designing rulebases using the TIBCO MDM Rulebase Designer graphical user interface.

• TIBCO Enterprise Message Service™: This software allows the application to send and receive messages using the Java Message Service (JMS) protocol. It also integrates with TIBCO Rendezvous and TIBCO SmartSockets™ messaging products.

• TIBCO BusinessWorks™: This is a scalable, extensible, and easy-to-use integration platform that allows you to develop and test integration projects. It includes a graphical user interface (GUI) for defining business processes and an engine that executes the process.

• TIBCO BusinessConnect™: This software allows your company to send and receive XML or non-XML business documents over the Internet. Based on a mutually agreed process flow and common document format, you and your trading partners can conduct secure and verifiable business transactions online.


viii | Typographical Conventions

Typographical Conventions

The following typographical conventions are used in this manual.

Table 1 General Typographical Conventions

Convention Use

TIBCO_HOME

ENV_HOME

Many TIBCO products must be installed within the same home directory. This directory is referenced in documentation as TIBCO_HOME. The default value of TIBCO_HOME depends on the operating system. For example, on Windows systems, the default value is C:\tibco.

Other TIBCO products are installed into an installation environment. Incompatible products and multiple instances of the same product are installed into different installation environments. An environment home directory is referenced in documentation as ENV_HOME. The default value of ENV_HOME depends on the operating system. For example, on Windows systems the default value is C:\tibco.

code font Code font identifies commands, code examples, filenames, pathnames, and output displayed in a command window. For example:

Use MyCommand to start the foo process.

bold code

font Bold code font is used in the following ways:

• In procedures, to indicate what a user types. For example: Type admin.

• In large code samples, to indicate the parts of the sample that are of particular interest.

• In command syntax, to indicate the default parameter for a command. For example, if no parameter is specified, MyCommand is enabled: MyCommand [enable | disable]

italic font Italic font is used in the following ways:

• To indicate a document title. For example: See TIBCO ActiveMatrix BusinessWorks Concepts.

• To introduce new terms For example: A portal page may contain several portlets. Portlets are mini-applications that run in a portal.

• To indicate a variable in a command or code syntax that you must replace. For example: MyCommand PathName


Preface | ix

Key combinations

Key name separated by a plus sign indicate keys pressed simultaneously. For example: Ctrl+C.

Key names separated by a comma and space indicate keys pressed one after the other. For example: Esc, Ctrl+Q.

The note icon indicates information that is of special interest or importance, for example, an additional action required only in certain circumstances.

The tip icon indicates an idea that could be useful, for example, a way to apply the information provided in the current section to achieve a specific result.

The warning icon indicates the potential for a damaging situation, for example, data loss or corruption if certain steps are taken or not taken.

Table 1 General Typographical Conventions (Cont’d)

Convention Use


x | Connecting with TIBCO Resources

Connecting with TIBCO Resources

How to Join TIBCOmmunityTIBCOmmunity 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 http://www.tibcommunity.com.

How to Access TIBCO DocumentationYou can access TIBCO documentation here:

https://docs.tibco.com

How to Contact TIBCO SupportFor comments or problems with this manual or the software it addresses, contact TIBCO Support as follows:

• 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.


http://www.tibcommunity.com


http://www.tibco.com/services/support


| 1

Release Notes

This document includes release notes for TIBCO MDM, software release 8.3.2.

Check the TIBCO Product Support web site at https://support.tibco.com for product information that was not available at release time. Entry to this site requires a username and password. If you do not have a username, you can request one. You must have a valid maintenance or support contract to use this site.

Topics

• New Features, page 2

• Changes in Functionality, page 9

• Deprecated and Removed Features, page 12

• Migration and Compatibility, page 14

• Closed Issues, page 16

• Known Issues, page 41



2 | Release Notes

New Features

The following new features have been added to the version 8.3.2 of TIBCO MDM.

New Configurator UIThe Configurator user interface is enhanced with the enhanced browser support for easy access and user friendly behaviour.

Configuring TIBCO MDM

The Configurator URL is changed. The current URL is http://hostname:6080/config/index.html.

For more information, refer to the chapter "Configurator" in TIBCO MDM System Administration.

Inbound and Outbound Queues

With the new Configurator UI, the inbound queue and outbound queue options are separated. For more information, refer to the sections “Working with an Inbound Queue” and “Working with an Outbound Queue” in TIBCO MDM System Administration. For queue references, the following chapters are also updated:

• Integration with TIBCO ActiveMatrix BusinessWorks - Sample 1

• Integration with TIBCO ActiveMatrix BusinessWorks - Sample 2

Migration Wizard

With the new Configurator UI, some fields of the migration wizard are changed or removed. The screens and relevant information are updated. For more information, refer to the chapter “Upgrading TIBCO MDM“ in TIBCO MDM Installation and Configuration Guide.

Database Setup Wizard

With the new Configurator UI, some fields of the database setup wizard are changed or removed. The screens and relevant information are updated. This chapter is also reorganized and restructured. For more information, refer to the chapter “Setting up Database” in TIBCO MDM Installation and Configuration Guide.


http://hostname:6080/config/index.html

New Features | 3

Decoupling of DocumentationIn the release 8.3.2, the documentation is separated from the software. It is no longer bundled with the product installation. Download the TIBCO MDM documentation from https://docs.tibco.com or as a sharable archive from the delivery site http://edelivery.tibco.com. For information, refer to the section “Configuration for Decoupling of Documentation” in TIBCO MDM Installation and Configuration Guide.

Purge Enhancements

Hints and Intervals

To optimize the repository cleanup, the hints and intervals features are introduced.

Purge Using Command Line

The following two inputs are added to the datacleaup utility:

• -h: indicates Hints

• -i: indicates Interval

Purge Using FileWatcher

The Interval parameter is added in the FileWatcher configuration file to identify only the changes records.

Purge Using Job Scheduler

The following two inputs are added in the purge job policy file:

• Interval

• Hints

For information, refer to the chapter “Configuring Purge” in TIBCO MDM System Administration.

Purge Activity

Added the Interval parameter to instruct the purge activity that it should consider only those records which have changed in the specified interval (number of days).



http://edelivery.tibco.com

4 | Release Notes

For more information, refer to the chapter “Activities” in TIBCO MDM Workflow Reference.

JMX Enhancements

Patterns MBean

Patterns MBean is added to JMX to collect the details and monitor the performance of Patterns interface. For information on Patterns statistics and operations, refer to the sections “Patterns Statistics” and “Patterns Operations” in TIBCO MDM System Administration.

Cache Locks MBean

The cache locks MBean is added to collect the information about all the cache locks created by TIBCO MDM. For more information, refer to the sections “Cache Locks Statistics” and “Cache Locks Operations” in TIBCO MDM System Administration.

JMX Statistics Copier

The JMX statistic copier is introduced to maintain history of data reported by JMX. For more information, refer to the section “Managing History of Data” in TIBCO MDM System Administration.

Bundle Processing LockTo deal better with concurrent editing scenarios of the same data, a bundle processing lock is introduced. The lock prevents concurrent processing errors on the same data, at the cost of possibly smaller throughput. For more information, refer to the Enable Save Lock configuration property in New Configuration Properties on page 5.

Text Search Enhancements

Text Search UI

You can perform the following actions on the Text Search UI:

• Search in join entities

• Search as you type


New Features | 5

• View the similarity score and change the value using the Similarity Score slider

• View the inherited attributes in the Category Specific Attributes section

For information, refer to the section “Text Search” of TIBCO MDM User’s Guide.

Resetting PasswordTo reset the forgotten password, the Reset Password functionality is introduced. For information, refer to the section “Resetting Password” in TIBCO MDM User’s Guide.

Inclusion of New GuideThe first version of TIBCO MDM Performance Tuning Guide is released. The guide provides the performance tuning methodologies to tune your system and achieve the optimal performance on all of the various layers of TIBCO MDM. For more information, refer to TIBCO MDM Performance Tuning Guide.

FileWatcher Enhancements

ProcessID

The ProcessID data set parameter is added to specify a workflow name in the FileWatcher.xml file. For more information, refer to section “ProcessID” in TIBCO MDM Customization Guide.

FireWorkflow Activity

The FireWorkflow activity is added. Using this activity, a named workflow can be started. For information, refer to the chapter “Activities” in TIBCO MDM Workflow Reference.

New Configuration PropertiesThe following table lists the configuration properties that are added in the 8.3.2 release of TIBCO MDM:


6 | Release Notes

Table 2 New Configuration Properties

Display Name of Property

Property Name

Location in Configurator Description Default

Default Timing Log Properties

Timing Log Default Category

com.tibco.cim.timinglog.default.categoryName

Cluster Outline > Initial Config > Timing Log

Specifies the value to configure the category of the timing log. This must be defined in the logging configuration.

The default value is timinglogdef

ault.

Timing Log Default Class

com.tibco.cim.timinglog.default.class


This timing log Java class receives the submitted form and processes it. The Java class writes the timing information to a file.

The default value is com.tibco.md

m.infrastruc

ture.logging

.TimingLog.

Timing Log Default Threshold

com.tibco.cim.timinglog.default.threshold


Controls whether or not any time statistics is to be generated. Set the threshold in milliseconds. If you set it to 0, all timings are tracked.

The default value is 0.

Timing Log Default Switch

com.tibco.cim.timinglog.default.enabled


Indicates the timing log for a certain category. The timing logs are generated only when the value is set to true.

The default value is False.

Authentication Property

Forgot Password

com.tibco.mdm.resetpassword.enable

InitialConfig > Authentication > Default/LDAP

Enables you to reset the forgotten password.

The default value is false.

Workflow Settings Property


New Features | 7

Enable standard validation execution in SaveRecord activity

com.tibco.mdm.optimization.saverecord.rulebaseoptions

InitialConfig > Workflow Settings

Indicates that the validation rules from the standard validation are applied on the incoming records in the SaveRecord activity.

The default value is true.

UI Settings Property

Repository View: Attribute group Default Rows

com.tibco.cim.ui.repositoryview.attributegrouplist.defaultrows

InitialConfig > UI Settings

Indicates the default number of rows to be displayed in the attribute list of all attribute group.

The default value is 10.

MDM Help Configuration

com.tibco.cim.help.config


Lists the options for MDM Help configuration.

The default value is online.

Help URL com.tibco.cim.help.url


Refers to the online Help URL to access the TIBCO MDM documentation.

Note: If you change the URL, you cannot access the documentation online.

The default URL for 8.3.2 is https://docs

.tibco.com/p

ub/collabora

tive_informa

tion_manager

/8.3.2/

Miscellaneous Property

Enable Save Lock

com.tibco.cim.record.useSaveLock

InitialConfig > Miscellaneous

Enables locks to avoid concurrent modification of parent and its child record.


Specify Timeout

com.tibco.cim.optimization.recordbundle.modification.timeout

InitialConfig > Miscellaneous

Specifies the time period for which the user has to wait to save the record that is concurrently being modified by another user.

The default value is 300 seconds.

Database Specific Property



Property Name



8 | Release Notes

Enable JDBC thin connection

com.tibco.cim.enable.jdbc.thin.connection

InitialConfig > Database > ORACLE

Indicates whether or not the data source upload should use JDBC thin connection.




Property Name



Changes in Functionality | 9

Changes in Functionality

The following are the changes in functionality in version 8.3.2 of TIBCO MDM.

Updates for Logo ChangeSince the TIBCO branding logo is changed, the screens of TIBCO MDM are updated in the following chapters:

Customization Guide

The Company Logo image file name is changed. For more information, refer to the section “Customizing Company Logo Box”.

The TIBCO MDM UI screens for new TIBCO logo are updated in the following chapters:

• Customizing Roles, Menus, and Access Rights

• Customizing User Interface

User’s Guide

The TIBCO MDM UI screens with the new TIBCO logo are updated in the chapter “Introduction to TIBCO MDM“.

Updated Workflow ActivitiesThe following activities are updated in this release:

• MatchRecord

Added the following parameters:— IndividualMatchScoreForEntity

— ConsiderNonMatchingRecords

— PenaltyForNonMatchingRecords

• Create Work Item

Added the CUSTOMDisplayServlet parameter for customization.


10 | Release Notes

• EvaluateRulebase

— Updated the description of the StaleDataError parameter on how to prevent the stale data error.

— Added the ValidationExclusion parameter to indicate which relationships can be excluded while applying validations on the record bundle.

— Added the OverwriteRelationships parameter to indicate that the relationships of RecordCollection are overwritten.

• InitiateSubFlow

Removed the asynchronous mode information as the Asynchronous mode is not supported.

Added the InRecordList parameter to specify a similar external name for the recordlist in the subflow.

Updated the description of the ProcessID parameter.

• SaveRecord

Added the ApplyValidation parameter to indicate whether or not to run the standard rulebase.

• SpawnWorkflow

Added the following parameters:

— RecordSequencing parameter to control the record sequencing.

— RecordSequeningAttribute parameter to control the record sequencing of specific records if the record bundle is huge.

Updates New Configurator UIThe new Configurator UI is introduced, and so the Configurator screens in the following chapters are updated:

Customization Guide

• Setting up Data Quality Process

• Localizing Text Strings

System Administration

• Search and Matching


Changes in Functionality | 11

Workflow Reference

• In-memory Workflows

• Workflow Optimizations

• Handling Workflow Failovers


12 | Release Notes

Deprecated and Removed Features

The following tables list any features that have been deprecated or removed in the version 8.3.2 of TIBCO MDM.

Deprecated Features

Removed Features

Affected Component Description Deprecated in

Release

ReasonCode tag

The ReasonCode tag from the Work Item Modify Close web service is deprecated. The section “Work Item Modify Close web service” is updated in TIBCO MDM Web Services Guide.

8.3.2


ReleaseRemoved in Release

Data Cleanup Utility

The Data Cleanup (cleanCatalogData.sql) utility is removed from $MQ_HOME\db\oracle\utility, and so the section “Data Cleanup Utility” is removed from TIBCO MDM System Administration.

8.3.1 8.3.2


Deprecated and Removed Features | 13

Timing Log Category

The following timing log categories are removed and replaced by the default timing log configuration:

• Rulebase Timing Log

• UI Servlet Timing Log

• Workflow

• Activity Timing Log

• SQL Timing Log

• Timer Timing Log

• Service Timing Log

For more information, refer to the section “Timing Log” in TIBCO MDM System Administration.

8.3.2 8.3.2


ReleaseRemoved in Release


14 | Release Notes

Migration and Compatibility

There are no migration procedures or compatibility issues in the version 8.3.2 of TIBCO MDM.

Upgrading to 8.3.2 Service Pack from 8.3.xFor upgrading to the minor version releases, migration is not required. To upgrade from TIBCO MDM 8.3.x to the 8.3.2 service pack version, install the new 8.3.2 service pack and deploy it using the existing database. The data migration is not required.

Consider the following points while upgrading to the 8.3.2 service pack version:

New ActiveSpaces Version

TIBCO MDM 8.3.2 release supports the TIBCO ActiveSpaces (R) Enterprise Edition 2.1.3 HF-1 version.

The release of TIBCO ActiveSpaces-Transactions 2.1.3 includes updates to address the heartbleed extension vulnerability referenced in CVE-2014-0160 and US-CERT VU#720951. Specifically, the release includes the OpenSSL 1.0.1g libraries.

Application Server Configuration

• For JBoss Application Server

— Remove jaxrs entries

— Define MDM EJB pool with appropriate pool size

For more information, refer to the section "Installing on JBoss Application Server" in TIBCO MDM Installation and Configuration Guide.

• For WebLogic Application Server

— Enable the Archived Real Path

For more information, refer to the section "Installing on WebLogic Application Server" in TIBCO MDM Installation and Configuration Guide.

New Configuration Properties

• For new configuration properties, refer to New Configuration Properties on page 5.


Migration and Compatibility | 15

• Upgrading to the new version of the ConfigValues.xml file is optional. However, it is recommended to upgrade ConfigValues.xml. To upgrade the previous version of the ConfigValues.xml file to the new version, refer to the sections “Running the Migration utility” and “Configuration Migration” in TIBCO MDM Installation and Configuration Guide.

For more information, refer to the section “Upgrading to 8.3.2 Service Pack from 8.3.x” in TIBCO MDM Installation and Configuration Guide.


16 | Release Notes

Closed Issues

The table lists closed issues in version 8.3.2 of TIBCO MDM.

Key Summary

CIM-19421 While expanding and collapsing the relationship record tree, the node labels were changed during the process of record loading.

CIM-19375 While executing rulebase, the local variables in the usefor tag was not supported for access and check actions.

CIM-19341 The search criteria on the Browse and Search page were reset on clicking the OK button on the View Record page.

CIM-19282 After the successful server start up, the Inbox page did not load work items and showed the SQL exception.

CIM-19214 On View record page, a lengthy text box attribute appeared editable instead of read only.

CIM-19180 A related record, when added did not get displayed under the relationship. However, on immediately selecting another relationship, the earlier related record got added under the selected relationship.

CIM-19116 If the Application Server was deployed in the Daylight Saving Timezone (DST) and the Timestamp values belonged to DST then the Timestamp attribute values got reduced by an hour.

CIM-19086 On Internet Explorer 9 and Chrome, the scroll bar disappeared on clicking the drop-down list in the search criteria of the Browse and Search page. This also happened on the Record UI screens.

CIM-19084 Records were not indexed in TIBCO Patterns while importing records using direct load.

CIM-19082 For SQL Server, on server startup, the SQL exception occurred during indexing records with multivalue attributes.

CIM-18878 On the Browse and Search page, the selected value in the drop-down list showed the correct second column values. However, on Viewing Record and returning to the Browse and Search page, the selected value in the drop-down list showed the first column value, while the rest of the list showed the second column values.


Closed Issues | 17

CIM-18870 The attribute length of a text box was restricted to 250 characters when accessed from Google Chrome.

CIM-18838 The following command-line utility did not purge record versions, which were set older than the cut-off date:./datacleanup.sh -o recordversions -r <repository ID> -d <cut-off days>-v 1

This issue was observed when the number of records to be purged was more than the value set for the com.tibco.cim.optimization.recordsperasynccall property. The default value is 100.

CIM-18825 On modifying a related record, multiple requests were sent for the modification causing slow rendering of UI.

CIM-18806 When the Record UI was customized to display the relationship as a tab using the recordui-render.xml file, the child record was modifiable, even though view only access constraint was defined in rulebase for a child record.

CIM-18802 The Modify button on the View Record page was enabled even though the resource security permission was set to View only.

CIM-18789 The rulebase was not applied for Record View page when it was displayed after modifying a record which was not the latest version.

CIM-18734 For a related record, the relationship attribute values were assigned to a child record attribute if the relationship attribute name was the same as the child record attribute name.

CIM-18722 An SQLSyntaxErrorException occurred on searching for records having rulebase validations. This error occurred if the attribute name had repository name as a substring.

CIM-18647 Java NullPointerException was thrown on executing the rulebase using the duplicate check function.

CIM-18616 After restarting the TIBCO Patterns server, text indexing configuration was not initialized.

CIM-18615 A NullPointer exception was thrown when multiple requests of the Record Modify web service were sent concurrently. As a result of this exception, the index did not get updated for these records. This exception occurred only when the com.tibco.cim.search.UseOnlineSyncIndexing property was set to true in Configurator.

Key Summary


18 | Release Notes

CIM-18598 NullPointerException occurred in the error log file while performing searchon the Mass Update page.

CIM-18597 All related records did not get added with the add record web service. The record ID/extension fields were not populated using the add record web service. However, these fields were populated using the ruleabse.

CIM-18596 While modifying a record using a perspective from the Browse and Search screen, an SQL database error was shown.

CIM-18480 The Compare and Show History buttons were disabled on the View Record screen when any language pack, other than English was applied.

CIM-18471 When importing metadata, the repository IDs were not properly substituted in a rulebase with an Include action.

CIM-18469 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-18429 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-18426 When the record list was shown using the softlink action, the table column width was not adjustable.

CIM-18414 While adding records where value to some of the business keys was assigned in a rulebase and some of them were present in the request file, an AssignIdentiy action was not evaluating record identity correctly.

CIM-18400 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-18393 An SQL error occurred for subset rules when a rulebase was specified to hide records.

CIM-18294 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.

Key Summary


Closed Issues | 19

CIM-18287 The OutDocument generated by the GetRecord activity did not contain the RelationshipData section.

CIM-18286 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-18280 The value of the relationship attribute disappeared after modifying the related record of a child record.

CIM-18278 The stale data error occurred during the modification of records without concurrency.

CIM-18277 The stale data error occurred during execution of the rulebase activity in the spawned workflow.

CIM-18276 A query that was used to validate subset rules by expression was slow.

CIM-18275 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-18274 When the child record was modified through the parent record modify operation, the record was not saved after clicking Save and Process.

CIM-18270 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-18255 Using the recordui-render.xml file, when relationship was configured to display as a tab, the Access constraint did not work to make the related record "read only".

CIM-18234 The Load Relationship mode of the database loader failed to establish relationships when the RecordIDExtension value was empty.

CIM-18220 If the workflow contained multiple CompareRecord activities, the OutDocument generated by the CompareRecord activity failed on validation against the mlXML schema.

CIM-18191 While modifying a record with relationship from the work item, the related records were not shown in the Relationship tab.

Key Summary


20 | Release Notes

CIM-18181 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-18177 If the repository spaces were enabled, the Entry_TTL value of the RECORD space was overwritten by the value of <ReplicationCount>.

CIM-18150 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-18124 The Event Log did not show the complete history if the log spanned multiple pages and the user clicked the Associated Events link, and then clicked the Back button on the Associated Event Log page.

CIM-18123 The event status changed from START to INPROGRESS in a workflow with the Async activities.

CIM-18111 The SaveRecord activity failed with a transaction timeout error when the record bundles included huge records.

CIM-18110 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-18109 The SpawnWorkflow activity is enhanced to control the record sequencing at the activity level.

CIM-18107 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-18105 The synchronization event failed with the Java Null Pointer exception in the ConvertRecordToOutput activity.

CIM-18104 The Cipher not initialized exception was thrown in a highly concurrent environment.

CIM-18098 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.

Key Summary


Closed Issues | 21

CIM-18097 On deleting the parent record, the reverse relationship from child record to parent record was not deleted.

CIM-18091 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-18085 The synchronization event failed with the Java Null Pointer exception in the ConvertRecordToOutput activity.

CIM-18084 While searching records on the Mass Update screen, the previously searched records were not displayed in the search result.

CIM-18079 On the migrated version (from 8.2.1 to 8.3.1) of TIBCO MDM adding related records was not possible.

CIM-18077 When the error link was clicked multiple times in the Basic Mode of the Mass Update screen, the error message was not updated.

CIM-18067 The GetUserList web service did not return the UserID in the response.

CIM-18063 A constraint with the Access action of rulebases was not working for the Mass Update operation.

CIM-18058 The following command-line utility did not purge record versions, which were set older than the cut-off date:

./datacleanup.sh -o recordversions -r <repository ID> -d <cut-off

days>-v 1

This issue was observed when the number of records to be purged was more than the value set for the com.tibco.cim.optimization.recordsperasynccall property. The default value is 100.

CIM-18035 For SQLServer, the Load Relationship mode of the database loader failed to establish relationships when the RecordIDExtension value was empty.

CIM-18032 For SQLServer modifying records using Database Loader failed when the RecordIdExtension value was null and it created duplicate PRODUCTKEY entries.

Key Summary


22 | Release Notes

CIM-17998 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 $MQ_HOME/customEAR/bin/workflowUtility.sh to $MQ_HOME/bin directory.

— Run workflowUtility.sh with the following options: workflowUtility.sh -c <command> -m <member_id> -e <event_id>

-p <process_id>

Options:

c - command, currently only resume is supported.m - member IDe - event IDp - process ID

For example: to restart process 789890, specify the following command: workflowUtility.sh -c resume -m 34254 -e 42500 -p 789890 Note: This utility sends async message to the TIBCO MDM server to restart the specified process. Check elink logs for execution or any errors.

CIM-17997 The Add Record event name appeared in the spawned (associated) events instead of the specified eventDescriptor parameter in the UpdateEvent activity.

CIM-17996 Subflow did not resume after the timed out transitions of work items and closure of all timed out work items.

Key Summary


Closed Issues | 23

CIM-17995 The export of role permission metadata was failing with the following exception: Relationship not found for resourceID<some resource id>.

CIM-17992 The alignment of the data was not in sync with the column headings in the search results of the Browse and Search page.

CIM-17991 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-17990 A performance issue occurred while loading the relationship tree in Record UI.

CIM-17982 While searching for records using Text Search (Attribute Based Search), duplicate values were displayed in the attribute field.

CIM-17970 Subflow did not resume after the timed-out transitions of work items and closure of all timed-out work items.

CIM-17966 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-17964 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.

Usage:

1. Copy $MQ_HOME/customEAR/bin/workflowUtility.sh to the $MQ_HOME/bin directory.

2. Run workflowUtility.sh with the following options: workflowUtility.sh -c <command> -m <member_id> -e <event_id> -p

<process_id>

Options:c - command, currently only resume is supported.m - member IDe - event IDp - process ID

For example, to restart process 789890, specify the following command:workflowUtility.sh -c resume -m 34254 -e 42500 -p 789890

Note: This utility sends async message to the TIBCO MDM server to restart the specified process. Check elink logs for execution or any errors.

Key Summary


24 | Release Notes

CIM-17960 A performance issue occurred while loading the relationship tree.

CIM-17943 Performance issues occurred with the IN_LISTSTR function on MicroSoft SQL Server.

CIM-17942 The Add Record event name appeared in the spawned (associated) events instead of the specified eventDescriptor parameter in the UpdateEvent activity.

CIM-17935 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-17925 In a related record, the web service to modify a child record increments the record version of the parent record even though the parent record was not modified.

CIM-17911 While downloading the .docx file from the File type attribute on the View Record page, the file opened as a ZIP file.

CIM-17910 While importing data if the Merge Data check box was selected and the values were not mapped to multivalue attributes, the multivalue attributes for the record were set to null instead of retaining the previous version's values.

CIM-17909 The user was able to modify a new record that was currently in a workflow and its latest work item was in the Timedout state.

CIM-17908 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-17906 While searching records on the Browse and Search screen, the columns were displayed in an incorrect order on the search result page.

CIM-17905 When the Record Modify web service request was reexecuted without changing any data, and the repository contained one of the attributes of the DATE type, the response did not return the following error message: Data unchanged, request ignored.

Key Summary


Closed Issues | 25

CIM-17871 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:

1. Run the CreateSequences.sql migration script to create sequences.

2. 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

Note: Microsoft SQL Server 2008 does not support sequences. Therefore, rollback to this server is not supported.

CIM-17826 The export of role permission metadata (File based approach) was failing with the following exception: Relationship not found for resourceID<some resource id>.

CIM-17818 A query that was used to validate subset rules by expression was slow.

CIM-17802 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-17794 The drop-down list values on the Mass update screen varied from the values on the Add Record and Modify Record screens.

CIM-17765 On the Browse and Search screen, the column headers were not aligned with the data in the columns. This issue occurred on Internet Explorer version 8.

Key Summary


26 | Release Notes

CIM-17764 The parent record was deleted after modifying the child record details and its effective date value.

CIM-17763 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-17733 When an out-of-the-box workflow was executed and if a repository had multivalue attributes, the shared multivalue attributes were replaced by other shared multivalue attributes in the OutDocument of the GetRecord activity.

CIM-17719 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-17697 For attribute values, numbers codes were shown instead of special characters on the View Record screen.

CIM-17688 While redeploying a relationship along with the deleted relationship attributes in TIBCO MDM Studio, the Java NullPointer exception was shown.

CIM-17687 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-17686 In the record add web service, the Assign and Access actions did not work for the relationship attributes.

CIM-17682 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-17678 When the Record Modify web service request was executed without changing any data, and the repository has one of the attributes of type DATE, the response did not return the Data unchanged, request ignored error message.

CIM-17677 The configuration properties related to message recovery related were not working correctly.

CIM-17676 If index entity name contained a space, the indexer initialization failed.

CIM-17669 For a record, if a rulebase was invoked with a warning or information message, then when you click the Save and Process button, the record was not saved.

CIM-17657 Localization was not applied to attribute names in the Search Results table of the Text Search screen.

Key Summary


Closed Issues | 27

CIM-17655 On the Modify Record screen, the record link was clicked in the related records table and a child record was modified. After modification, another child record was selected from the related records table. However, the modification made to the previous child record was not saved.

CIM-17568 Using recordui-render.xml, when relationship was configured as a tab, the relationship name was not externalized.

CIM-17550 The hide rulebase was applied on the RecordIDExt attribute of the child record. After clicking the new related record in the relationship tree, an error occurred.

CIM-17541 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.

Key Summary


28 | Release Notes

CIM-17530 The recorduirender.xml was configured to display a relationship as a tab and validation rulebase constraint was set to specify the record ID of 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.

1. 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.<enterprise_name_lowercase>.<repositoryname_lowercase>.repository.<repositoryname_lower

case>.

<forwardrelationshipname_lowercase>.recordlist.sortby

— Version: 8.3


— Description: For sorting columns in relationship as tab, based on attribute name.

— Current Value: PRODUCTID

— Default Value: PRODUCTID

— Category: UI Settings

Note:

1. Currently, the default column sort is not supported for the relationship attribute name.

2. Specify any attribute value for the Current and Default Value fields.

CIM-17529 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.

CIM-17528 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-17527 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.

Key Summary


Closed Issues | 29

CIM-17526 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-17525 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:<Parameter direction="in" name="MergeTargetInOutdoc"

type="boolean" eval="constant">TRUE</Parameter>

CIM-17524 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-17523 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-17522 The RelationshipData element was intermittently missing from the output document of the GetRecord activity.

CIM-17521 An error message was displayed after clicking the Configure link on the Mass Update screen.

CIM-17519 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-17518 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 includes multiple subflows and work item closed in subflows.

CIM-17517 The context variable passed in the GetWorkitem web service request was not available while executing validation rulebase for a record in the work item.

Key Summary


30 | Release Notes

CIM-17515 The customized relationship name specified in the CustomSharedStringResources.properties file was not displayed on the Record UI. The relationship tab name specified in the customization did not take higher precedence.

CIM-17514 The context variable passed in the Record Modify web service request was not available while executing rulebase for related records.

CIM-17508 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-17507 After resubmitting an event, the PARENTID column in the Event table was not populated correctly.

CIM-17506 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-17505 On the View Record screen, when the Modify link was clicked, the access mode= view_record constraint of a rulebase did not work.

CIM-17500 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 catalog validation.xml file was executed instead from the dummy rulebase. To resolve this issue,

1. The ApplyValidation parameter is added to indicate whether or not to execute the catalog validation.xml file.

2. The configuration Enable standard validation execution property in the SaveRecord activity (com.tibco.mdm.optimization.saverecord.rulebaseoptions) is added to apply validation on incoming records.

CIM-17499 The security violation exception was displayed for a record, after clicking the OK button on the Record Usage screen.

CIM-17458 When the Record Query web service request was executed to retrieve all versions of a record and the RECORD_STATE was set to All, the CHECKSUM system attribute returned a decimal point followed by the trailing zeroes. This issue occurred on Microsoft SQL Server.

Key Summary


Closed Issues | 31

CIM-17457 Huge number of concurrent add record web service requests involving the MatchRecord activity caused connection leak.


CIM-17435 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 catalog validation.xml file was executed instead from the dummy rulebase. To resolve this issue,

1. The ApplyValidation parameter is added to indicate whether or not to execute the catalog validation.xml file.

2. The configuration property - Enable standard validation execution in SaveRecord activity (com.tibco.mdm.optimization.saverecord.rulebaseoptions) is added to apply validation on incoming records.

CIM-17421 A rulebase created for a relationship child record to validate Effective End Date should be greater than the Effective Date. In this scenario, if the Effective End Date contained the previous year's value, an error message was displayed while adding or modifying a relationship child record.

CIM-17417 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-17414 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-17413 The user was able to modify a record that was currently in a workflow and its latest work item was in the Timedout state.

CIM-17409 While importing data if the Merge Data check box was selected and the values were not mapped to multivalue attributes, the multivalue attributes for the record were set to null instead of retaining the previous version's values.

Key Summary


32 | Release Notes

CIM-17404 TIBCO MDM 8.3.1 was enhanced to support TIBCO MDM Administration Agent.

CIM-17390 On the View Record screen, when the Modify link was clicked, the access mode = view_record constraint of a rulebase did not work.

CIM-17387 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-17382 While downloading the .docx file from the File type attribute on the View Record page, the file opened as a ZIP file.

CIM-17378 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-17377 While creating or modifying records, usability issues occurred with the drop-down fields on Mozilla Firefox.

CIM-17372 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-17369 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-17368 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.

Note: This has been fixed but the fix is not applicable when rulebase is used in the MergeRecord Activity.

CIM-17367 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-17366 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 the validation error.

Key Summary


Closed Issues | 33

CIM-17365 The DataService element specified in the MasterCatalogRecordAction operation missed the namespace definitions in the error response.

CIM-17347 After resubmitting an event, the PARENTID column in the Event table was not populated correctly.

CIM-17323 The JavaScript errors were displayed on the Browse and Search screen on Internet Explorer version 8.

CIM-17311 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-17273 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-17215 Repository model deployment failed with error, if a repository was modified to add a new relationship attribute.

CIM-17183 The DataService element specified in the MasterCatalogRecordAction operation missed the namespace definitions in the error response.

CIM-17182 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 the validation error.

CIM-17172 The context variable passed in the Record Modify web service request was not available while executing rulebase for related records.

CIM-17171 The customized relationship name specified in the CustomSharedStringResources.properties file was not displayed on the Record UI. The tab name specified in the customization took higher precedence and overridden the resource bundle properties.

CIM-17153 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-17151 Empty directories were created under $MQ_COMMON_DIR/Work after executing a web service request using TIBCO ActiveMatrix Businessworks Plugin for MDM.

Key Summary


34 | Release Notes

CIM-17129 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.

Note: Fix is not applicable when rulebase is used in the Merge Activity.

CIM-17114 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-17113 If TIBCO Collaborative Information Manager was running on the Oracle database, a performance issue occurred while loading the relationship UI.

CIM-17084 While synchronizing records with the All option, the following exception was displayed in the CreateOutputFile activity:

JAV-8001: Unexpected error. doCatalogTypePublish. Additional

information: java.lang.NullPointerException

CIM-17082 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-17081 For SQL Server, the MatchRecord activity failed intermittently as the related records were not loaded. For migration, refer to the installation section.

CIM-17080 The context variable passed in the GetWorkitem web service request was not available while executing validation rulebase for a record in the workitem.

CIM-17075 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 includes multiple subflows and workitem closed in subflows.

CIM-17038 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-16986 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-16968 An error message was displayed after clicking the Configure link on the Mass Update screen.

Key Summary


Closed Issues | 35

CIM-16941 The RelationshipData element was intermittently missing from the output document of the GetRecord activity.

CIM-16934 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-16896 While evaluating attribute conflict, the Record Modify workflow failed in the UpdateRecordState activity.

CIM-16877 When the record was modified to add a new related record, the value of PARENT context variable was not evaluated correctly while executing the relationship rulebase.

CIM-16863 A match and merge work item was created for a three level record hierarchy. In this case, if the Add as New checkbox 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-16862 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:<Parameter direction= in name=MergeTargetInOutdoc type=boolean eval= constant>TRUE</Parameter>

CIM-16842 While modifying a record, if the tab was pressed for a drop-down list, the page was refreshed even though refresh="no" was set for a drop-down list in the rulebase file.

CIM-16837 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-16829 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-16827 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.

Key Summary


36 | Release Notes

CIM-16805 The validation rulebase constraint was specified for mandatory repository attributes. In this case, the validation error occurred and the specified values of the mandatory attributes disappeared after the following steps were performed sequentially:

1. Selected the relationship node.

2. Entered the value for the mandatory attributes.

3. Clicked the Validate button

CIM-16770 The refresh flag was set to no in the <select> action for the drop-down constraint. In this case, each time when a new value was selected from the drop-down list, the screen was refreshed.

CIM-16724 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-16706 On the Modify Record screen, the record link was clicked in the related records table and a child record was modified. After modification, another child record was selected from the related records table. However, the modification made to the previous child record was not saved.

CIM-16698 The context variable passed in the Record Query webservice was not evaluated correctly while executing rulebase for access constraint.

CIM-16693 While generating the output file using synchronization, occasionally ConcurrentModificationException was seen in the IdentifyProtocolOperations activity.

CIM-16658 With an incorrect authentication or on session expiry, the Work Item Query web service response returned an incorrect namespace.

CIM-16657 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.

CIM-16654 Even though the record modify web service did not have any change inthe record, the record modification events were initiated.

CIM-16650 The event name intermittently appeared as Unresolved Record Message for the Record Add Notification events.

Key Summary


Closed Issues | 37

CIM-16649 Workflows that generated the huge ProcessState failed with the following error: ORA-01461: can bind a LONG value only for insert into a LONG

column.To resolve the issue, add the Enable Huge process state property in Configurator (Tools > Add Configuration Value):

Enter the following details in each field:

— Configuration value name: Enable Huge process state

— Internal name: com.tibco.mdm.processstate.hugeoverflow

— Version: 8.3


— Description: This property enables huge overflow on PROCESSSTATE.STATEPARAM.

— Current Value: True

— Default Value: False

— Category: Optimization

Also, refer to the Installation section for migration and limitation information.

CIM-16647 The Sticky configuration utility did not work for the clustered environment.

CIM-16627 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.

Key Summary


38 | Release Notes

CIM-16606 The recorduirender.xml was configured to display a relationship as a tab and validation rulebase constraint was set to specify the record ID of 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 ( Add New Property):

— Configuration value name: Sorting

— Internal name: com.tibco.mdm.<enterprise_name_lowercase>.<repositoryname_lowercase>.repository.<repositoryname_lower

case>.

<forwardrelationshipname_lowercase>.recordlist.sortby

— Version: 8.3


— Description: For sorting columns in relationship as tab, based on attribute name.

— Current Value: PRODUCTID

— Default Value: PRODUCTID

— Category: UI Settings

Note:

1. Currently, the default column sort is not supported for the relationship attribute name.

2. Specify any attribute value for the Current and Default Value fields.

CIM-16584 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.

CIM-16546 The Text Search web service requests did not work when authentication details were provided using jsessionid.

CIM-16544 While displaying the related records on the Tab using recordui-render.xml, the leading zero was discarded in the PRODUCTID (GTIN number).

CIM-16536 An exception occurred while executing the EvaluateRulebase activity in the SYNC mode.

Key Summary


Closed Issues | 39

CIM-16528 For record view operation, the RECORD_ACTION context variable was evaluated incorrectly as EDIT.

CIM-16501 Deployment of a workflow from TIBCO MDM studio failed due to TransformerException.

CIM-16496 When a record was added with multiple manual classification code hierarchy, the schema validation failed for OutDocument of the GetRecord Activity with the ClassificationCode error. The OutDocument of the GetRecord activity was not in compliance with the MLXML schema.

CIM-16482 Importing metadata for the role security permissions was not taking effect unless server or cache was restarted.

CIM-16417 On deleting and re-creating repository attributes, the previously added values for the drop-down list attributes were not displayed on record UI.

CIM-16366 The ELSE action in a rulebase was executed irrespective of evaluation of condition.

CIM-16350 During direct merge, the SkipMergeAttributeList or AllowMergeAttributeList did not work correctly.

CIM-16388 The CONFLICT and CatalogObjectNotFound errors were thrown when the purge deleted record versions referred by the last confirmed version of records. The issue occurred when the retention period for the purge action was set too low in the FileWatcher.xml file.

CIM-15782 Even though the related repository did not have an explicit EFFECTIVEDATE attribute, the EFFECTIVEDATE relationship attribute was updated with the MODDATE of the child record.

CIM-15767 Rounding Off for large decimal values defined for a decimal type attribute, was incorrect.

As part of this fix, the rounding of decimal numbers are not supported on the UI. The decimal data are displayed in (precision[,scale]) format. The data gets validated against the maximum values for precision and scale when it is saved into MDM. Refer MDM User Guide for more information on default values for precision and scale.

CIM-15676 When the parent repository was modified from a related repository, the record add/modify request did not work for dynamic web services.

Key Summary


40 | Release Notes

CIM-15320 Using FileWatcher, for List type DataSet, when multiple data sources were uploaded, the same data source file was uploaded for all data sources.

CIM-15204 The date calendar displayed on the Mass Update screen was not consistent with the date calendar displayed on other screens.

CIM-14808 While importing records empty entries were made for multivalue attributes, which did not have any value assigned.

CIM-14506 While creating or modifying records, usability issues occurred with the drop-down fields on Mozilla Firefox.

CIM-12852 Attributes of the decimal data type having a value less than 1, were not displayed with a leading zero before the decimal point.

CIM-12603 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-12381 If a user modified the parent record by adding a child record and another user modified the same child record, the stale data error occurred.

CIM-11683 If the LDAP option was selected as Authentication Type in Configurator, the LDAP based users were not able to authenticate from TIBCO MDM Studio.

CIM-11677 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 MDM the 8.2.0 version.

Note: Currently, the Delete link has been removed from the View Record screen.

CIM-11678 On the Compare Versions screen, the with Version drop-down list rendered incorrectly for a specific browser version.

CIM-11172 While exporting related repository records using the synchronization format was intermittently skipping the parent record data.

CIM-10648 While importing records with relationship, the record relationship was updated incorrectly because of high concurrency during import.

CIM-10456 In the case of cluster setup, hotfix installation using CustomUtil.sh failed if there were multiple Members or Nodes defined in the ConfigValues.xml.

CIM-10081 On the WebSphere Application Server version 7 or later, the soap fault error occurred on invoking the logout web service.

Key Summary


Known Issues | 41

Known Issues

This table lists the known issues in version 8.3.2 of TIBCO MDM.

Key Summary/Workaround

CIM-19719 Summary: Modification of a rejected record from a cancelled event does not work correctly.

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-19629 Summary: Deploying TIBCO MDM 8.3.2 fails on WebLogic Application Server 12.1.3 version.

Workaround: Use WebLogic Application Server 12.1.1 version.

CIM-19605 Summary: The hide record rulebase functionality does not work correctly, if the true and false values are entered in lowercase for the BOOLEAN attribute type.

Workaround: Specify the values in uppercase.

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-19474 Summary: The Record Query web service request containing RelationshipData does not capture relationships between records, if the record is in the DRAFT state and business process rule is set to repository.

Workaround: None


42 | Release Notes

CIM-19433 Summary: Seed data creation fails with the ORA-01843 error during the Oracle database setup. The setup is for the Oracle database client globalization.

Workaround:

1. Set the following environment variables on Oracle and TIBCO MDM server, and then restart the Oracle database and TIBCO MDM server:

— NLS_LANG

— NLS_DATE_FORMAT

2. Add the following JVM arguments in the $MQ_HOME\Configurator\tomcat\bin\setenv.bat file.

— -Duser.country=en — -Duser.language=en

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 does not appear 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.

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



Known Issues | 43

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-18670 Summary: The Hot Deployable field for a new configuration property is not available on the Add New Property window in Configurator.

Workaround: Directly modify the ConfigValues.xml file.

CIM-18423 Summary: The configured attributes are not displayed correctly on the search result page while searching for existing relationships.

Workaround: None

CIM-18248 Summary: On the record UI a boolean attribute shows TRUE and FALSE values in the drop-down list even though the showoninput property in the rulebase action is set to display YES and NO values.

Workaround: None

CIM-18222 Summary: The File type attribute with multivalue option displays an error while downloading the record file.

Workaround: None.

Note: Do not use multivalue file type attributes.

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-17214 Summary: The PARENT rulebase context variable is not evaluated correctly when the related record added using the reverse relationship.

Workaround: None



44 | Release Notes

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-17021 Summary: The Add as new check box on the Merge Record Details screen does not work for multiple children relationships available at the first level relationship. The source records of one relationship are merged into the target records of another relationship instead of adding a new relationship.

Workaround: None

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 do not work consistently.

Workaround: None

CIM-16874 Summary: Web service requests with limited resource security permissions (for example, Support Engineer role) throw a warning instead of an error, and returns a success count.

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



Known Issues | 45

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

CIM-16530 Summary: The indexed attributes in the IndexerConfig.xmlfile 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-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-15855 Summary: The configuration of the Web UI affects the web service API.

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

CIM-15311 Summary: Attributes shown in the search results of text search do not match the available or selected attributes of the Configure window.

Workaround: None



46 | Release Notes

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-14200 Summary: Synchronizing all records may replicate the relationship attributes related to an export operation.

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-12097 Summary: The synchronize feature does not detect incrementally added relationships and does not publish the added relationships in the output.

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

CIM-7708 Summary: A repository cannot be created with a name similar to the previously deleted repository name.

Workaround: None



TIBCO Collaborative Information Manager Release Notes · † TIBCO MDM Release Notes: Read the...

Documents

Transcript of TIBCO Collaborative Information Manager Release Notes · † TIBCO MDM Release Notes: Read the...