TIBCO MDM 8.3.1 Hotfix 02 is now available.

book

Article ID: KB0104841

calendar_today

Updated On:

Products	Versions
TIBCO MDM	-
Not Applicable	-

Description

Description:

TIBCO MDM 8.3.1 Hotfix 02 is now available.

This hot fix can be downloaded from the TIBCO Support file transfer server- mft.tibco.com.

Server name: mft.tibco.com

Credentials: use your TSC (TIBCO Support Central website) login.

Browser: https://mft.tibco.com

FTP: port 21

SFTP: port 22

FTP using your browser is not supported, please use an FTP client or command-line. TIBCO employees must use a secure protocol.

Once logged on you can find the hot fix under: "AvailableDownloads/MDM/8.3.1/hotfix-02"

This .zip file also has the Readme file inside. Please unzip the file and look for the Readme file for Instruction on how to apply the hotfix.

Closed Issues in 8.3.1_HF-002 (This Release)

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-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-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-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'. 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_lowercase>.

<forwardrelationshipname_lowercase>.recordlist.sortby

- 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

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.

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:

CIM-17524

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

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 property - "Enable standard validation execution in SaveRecord activity" (com.tibco.mdm.optimization.saverecord.rulebaseoptions) is added to apply validation on incoming records.

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

CIM-17365

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

Issue/Introduction

TIBCO MDM 8.3.1 Hotfix 02 is now available.

Environment

Product:TIBCO MDMVersion:MDM 8.3.1hotfix-02OS:ALL

Feedback

thumb_up Yes

thumb_down No

Welcome to "KB Articles"