TIBCO MDM 8.3.0 Hotfix 05 is now available.
Article ID: KB0104725
Updated On:
| Products | Versions |
|---|---|
| TIBCO MDM | - |
| Not Applicable | - |
Description
Description:
The hotfix can be downloaded from the TIBCO Support ftp server, support-ftp.tibco.com. Please use your eSupport username and password to access the server. After connecting, go to available_downloads/CollaborativeInformationManager/8.3.0/hotfix-05/ to download the hotfix.
This .tar file also has the Readme file inside. Please untar the file and look for the Readme file for Instruction on how to apply the hotfix.
The defects fixed in CIM 8.3.0 Hotfix 05 are:
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.
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-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-17347
After resubmitting an event, the PARENTID column in the Event table was not populated correctly.
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-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-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-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.
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-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-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.
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-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-16650
The event name intermittently appeared as 'Unresolved Record Message' for the Record Add Notification events.
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
- Visibility: Advanced
- 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-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 (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-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.
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-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-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 Collborative Information Manager on 8.2.0 version.
Note: Currently, the Delete link has been removed from the View Record screen.
The hotfix can be downloaded from the TIBCO Support ftp server, support-ftp.tibco.com. Please use your eSupport username and password to access the server. After connecting, go to available_downloads/CollaborativeInformationManager/8.3.0/hotfix-05/ to download the hotfix.
This .tar file also has the Readme file inside. Please untar the file and look for the Readme file for Instruction on how to apply the hotfix.
The defects fixed in CIM 8.3.0 Hotfix 05 are:
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.
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-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-17347
After resubmitting an event, the PARENTID column in the Event table was not populated correctly.
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-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-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-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.
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-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-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.
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-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-16650
The event name intermittently appeared as 'Unresolved Record Message' for the Record Add Notification events.
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
- Visibility: Advanced
- 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-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 (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-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.
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-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-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 Collborative Information Manager on 8.2.0 version.
Note: Currently, the Delete link has been removed from the View Record screen.
Issue/Introduction
TIBCO MDM 8.3.0 Hotfix 05 is now available.
Environment
Product: TIBCO MDM
Version: 8.3.0
OS:
--------------------
Feedback
Yes
No
Powered by
