| CIM-29309
|
When you exported the repository metadata along with the input maps by using the
Export Metadata (Wizard) option, the exported metadata output file did not contain the
Delete Relationships Only parameter.
As a result, importing the same (exported) metadata into another environment led to metadata corruption.
|
| CIM-29251
|
When you clicked the
Save and Process button on the
Browse and Search page, the validation rules defined in the
catalogvalidation.xml file were not retrieved and the records were saved without displaying the validation errors.
|
| CIM-29242
|
When searching for work items in the Inbox, if a specific repository was selected from the
Repository drop-down list, the search did not return any records in the result. However, when
ALL was selected in the
Repository drop-down list, the records were returned in the search result.
|
| CIM-29227
|
When you tried to save a record (that contained validation errors) from the work item page, the record was not saved and the page was refreshed even after you enabled the
Save with errors resource security permission for the record.
|
| CIM-29224
|
When you added a record using the Record Add web service or using the add record palette of TIBCO ActiveMatrix BusinessWorks Plug-in for MDM, the value was sometimes not assigned to the relationship attribute of integer type.
The issue occurred when the relationship attribute name was defined as
QUANTITY or
quantity.
|
| CIM-29215
|
The Save Record activity failed during workflow execution.
|
| CIM-29204
|
If a user had full permissions on a work item and
ALL was selected in the
Repository and
User drop-down lists, and if the user approved the work item, the following error was displayed after submitting the work item:
GEN-7012: Incorrect number of parameters specified. Usually indicates program error. Additional information: Mismatch in the number of values supplied and no. of OrderBy or Unique Cols defined for the scroller.
However, the work item was processed correctly and the workflow was completed.
|
| CIM-29199
|
In Internet Explorer 11, after clicking the
Show All Errors link on the Record Add or Record Modify page, an error was displayed.
|
| CIM-29189
|
When adding or modifying a record, if the record contained errors, the
USER_ACTION rulebase did not work according to the rules set in the rulebase validation file and the validation errors were not displayed after clicking
Save and Process.
|
| CIM-29188
|
A rulebase was defined for the
Quantity relationship attribute to verify whether the attribute was defined or not. However, after defining the relationship attribute on the
Modify Record page, the
Record has errors message was displayed for related records on the work item page.
|
| CIM-29144
|
When a related record was added to the root record by using the
Create Related Record option, the related record was added outside of the relationship structure.
|
| CIM-29139
|
A record search using reverse relationship criteria did not return any records.
|
| CIM-29079
|
After logging in to TIBCO MDM, the work item list was not refreshed in the Inbox.
|
| CIM-29067
|
After modifying a record from the work item page and clicking
Save, a new version of the record was created instead of redirecting to the
Record Modify page.
|
| CIM-29060
|
When modifying a record from the work item page, if you clicked the
Review link, the
Modify Record page opened instead of the
Record Review and Rejection page.
This issue occurred only when you used a custom UI page.
|
| CIM-29053
|
By using the Retrieve Records by ID and IDEXT REST service, you could not retrieve the CONFIRMED parent record with the CONFIRMED child record.
To resolve the issue, a new
goldenBundle boolean type query parameter has been added.
- If you set the value of
goldenBundle to
true, the response contains details of the parent and child records whose record state was CONFIRMED.
- If you set the value of
goldenBundle to
false, the response contains the CONFIRMED parent record, and the child records according to their latest record state.
|
| CIM-28810
|
When the record UI tree had a large number of immediate child records with a large rulebase, it took unusually long time to be displayed.
The following enhancements have been made to improve the record UI tree rendering:
1. Tree records are displayed in a paginated way, you can change the pagination size by using the existing
com.tibco.cim.ui.relatedrecordlist.defaultrows configuration property. By default, 20 related records are loaded. Click
Show more to load more related records.
2. To avoid rulebase execution when rendering the record-relationship tree, add the following property in the Configurator:
- Configuration value name: Enable rulebase execution on tree
- Internal name: com.tibco.mdm.recordui.enable.rbOnTreeNodes
- Version: 9.1
- Visibility: Advanced
- Description: This property enables rulebase execution on each node in the record UI tree. Rulebase is executed for multiple rulebase functionalities, including filtered relationship, access permission, assign action, and display values. Disabling this property loads the UI faster losing the rulebase functionality
- Value Type: Boolean
- Current Value: false
- Default Value: true
- Visibility: All
- Category: Miscellaneous
3. Additionally, in the pop-up menu for a relationship node, the
Search option is added to support search for related records. Only the Exact and the Contains search operators are supported.
|
| CIM-28763
|
When TIBCO MDM was installed in a cluster environment, the confirmed records were not indexed even if the deferred indexing mode was set to TRUE.
|
| CIM-28742
|
When reassigning work items to another user (with a custom role) by using the Work Item Reassign web service, the response returned an error.
|
| CIM-28502
|
When deploying metadata, an incorrect key value was cached in the Apache Ignite cache.
|
| CIM-28382
|
On the
custom UI page, the drop-down list options were not populated correctly when the attribute name was in camel case.
|
| CIM-28345
|
An error occurred when you tried to incrementally deploy related input maps from TIBCO MDM Studio.
|
| CIM-28257
|
On the
Merge Record page of a work item, attributes with the "view" access mode were editable.
|
| CIM-28246
|
A record rejected in TIBCO MDM was not deleted or updated on the TIBCO Patterns server.
|
| CIM-28244
|
When related record search criteria were specified, the Search record operation took a long time to return results.
|
| CIM-28243
|
Linking to work items directly in TIBCO MDM from an external custom UI caused an error.
|
| CIM-28179
|
Attribute name was not specified when retrieving value from the Apache Ignite cache.
|
| CIM-28152
|
When importing data using database loader with an SQL type data source, the following error occurred during the import event:
CAT-1368: One or more of specified column names invalid or reserved database keyword. Consult database documentation for complete list of reserved keywords and valid column names.
Note: If you have installed Oracle 12.2, use the
ojdbc7.jar file to create an SQL type data source.
|
| CIM-28002
|
After exporting metadata by using the
Export Metadata (Wizard) option for business process, an incorrect directory structure was created in the export ZIP file.
The issue occurred only on the migration environment.
|
| CIM-27904
|
When setting up TIBCO MDM 9.1.0 on Windows SQL Express 2016, errors occurred during seed data creation for the
PURGEDDOCUMENT and
PURGEDRECORDCOLLECTION tables.
|
| CIM-27834
|
When importing records, the
UpdateRecordState activity remained in the InProgress state constantly and the import event failed. The issue occurred when the following actions were performed:
- The value of
VersionPolicy parameter was specified as CORRECT or OPTIMIZE
- Multiple edits were made to the workflow
|
| CIM-27688
|
After running the Get Event Info web service, the status and state showed the response in all uppercase letters in the version 9.1.0 of TIBCO MDM, whereas in version 8.3.2 only the first letter was in uppercase. To enable the backward compatibility, change the value of the
Enable Backward Compatibility For Event Info property to
true in the Configurator and restart the TIBCO MDM server.
|
| CIM-27677
|
The Query Record activity of ActiveMatrix BusinessWorks Plug-in for MDM did not return the full file path for a file type attribute.
|
| CIM-27609
|
A rulebase could be configured to display the text in the Description column of a work item on the
Inbox page. However, an incorrect value was displayed in the description for the value of "$PrimaryRecord$" record link.
|
| CIM-27563
|
In the Record Modify web service request, the file path was validated even when no changes were made to file type attributes and no files were attached in the request.
|
| CIM-27535
|
When multiple relationship information was included in the Record Modify web service request, the relationship marked for deletion was validated.
|
| CIM-27528
|
A performance issue was observed with the database. The database indexes were missing in the create_indexes.sql file for version 9.1.0 of TIBCO MDM.
|
| CIM-27467
|
The Record Query web services were running slower compared with the web services in version 8.3.2 of TIBCO MDM because of the enhanced functionality of retrieving TotalCount, which was useful for the pagination purpose only.
To resolve the issue, add the following property in the Configurator:
- Configuration value name: Enable total count for query web service
- Internal name: com.tibco.mdm.webservice.evalTotalCount
- Version: 9.1.0
- Visibility: Advanced
- Description: This property enables total count for record query web service
- Value Type: Boolean
- Current Value: false
- Default Value: true
- Visibility- All
- Category - Miscellaneous
This property disables the count query from all Record Query web services and since the count query is eliminated, the web service response contains TotalCount=0.
Note: If you still need the correct TotalCount in response, add "EVAL_TOTALCOUNT" Boolean context variable to override the "Enable total count for query web service" property. Example: <Variable name="EVAL_TOTALCOUNT" type="boolean">true</Variable>.
|
| CIM-27261
|
When retrieving the complete hierarchy of the record (parent and child) by using the Text Search REST service, an error was displayed for one of the child records.
To resolve the issue, add the
findRootRecord query parameter in the Text Search REST service.
- If you specify findRootRecord = true, the response contains only parent record
- If you specify findRootRecord = false, the response contains parent and child records
|
| CIM-27247
|
On the
My Company Profile page, security vulnerability issues were observed.
|
| CIM-27230
|
SQL queries used for loading relationships ran slowly as it used the IN_LISTSTR user-defined function.
|
| CIM-27227
|
In a multinode MDM environment, clicking the
Profile tab resulted in a null pointer exception.
|
| CIM-27051
|
You could not search for records based on the "MODDATE" attribute in the Record Query REST service. After the fix, you can provide the MODDATE filter through the RECORD_MODDATE predefined key.
|
| CIM-27029
|
Clicking the
Show All Errors link on the record UI displayed a blank page instead of showing the validation errors.
|
| CIM-27022
|
On the
Repositories page, the names of the repositories were incorrectly displayed. For example, a space in the name was displayed as a plus sign (+) and parentheses () was displayed as a percentage sign (%).
|
| CIM-26954
|
When viewing records for a classification scheme, the PostgreSQL query ran endlessly.
|
|
CIM-26944
CIM-26875
|
The
Quick Export functionality was not supported in the custom search UI.
|
| CIM-26936
|
The selected last value in the filter drop-down list on the custom search UI was not retained for the future search operation.
|
| CIM-26935
|
Sorting columns in the custom search UI did not work.
|
| CIM-26927
|
On the
Event Details page, when you clicked the
Records link, a null pointer exception was displayed.
|
| CIM-26916
|
When searching records using the Text Search web service, the weight of attributes was not considered. Also, earlier the symmetric search operation was not supported using the Text Search web service.
|
| CIM-26910
|
The "Allow record saved as unconfirmed without workflow" permission was denied for a user or role. In this case, the
Save button was not available on the
Modify Record page from the work item.
|
| CIM-26908
|
When you ran the Record Query web service immediately after the Record Modify web service, the response contained an incorrect record version. This issue occurred on the Microsoft SQL Server database.
|
| CIM-26907
|
When the
AssignIdentity rulebase was used with some keys having null values; other values matching the duplicates were not detected.
Note: This issue occurred when the RECORD ALIAS cache was not sufficient.
|
| CIM-26902
|
For the "File Type" attribute, attaching a file more than once caused an error. This issue occurred when adding a record in a repository with the self-relationship through ActiveMatrix BusinessWorksTM Plug-in for MDM.
|
| CIM-26893
|
When multiple searchable attributes were added to a repository and you imported records in bulk, the data quality workflow event was stuck in the "CreateWorkItem" activity.
To include searchable attributes in work item, add the following property in the Configurator:
- Configuration value name: Searchable Attributes in Work item
- Internal name: com.tibco.mdm.workitem.search.attributes.include
- Version: 9.1
- Visibility: Advanced
- Description: Searchable attributes in work item
- Value Type: Boolean
- Current Value: true
- Default Value: false
- Visibility- All
|
| CIM-26876
|
If a multivalue attribute was marked as quick viewable and contained the percentage (%) in its value, the work item failed to open and displayed an error message.
|
| CIM-26865
|
In the
UI Builder custom page, you could not view the width and alignment of the multivalue drop-down list.
|
| CIM-26861
|
If more than one source records contained a child record that matched with the same target record, a null pointer exception was displayed when opening the data quality work item.
|
| CIM-26838
|
If the value of a record attribute contained a pipe (|) character, when viewing the record, the XML equivalent value for pipe (|) was displayed instead of the pipe (|) character.
|
| CIM-26790
|
An OutOfMemoryError exception occurred during bulk import when the huge number of records were rejected due to validation failure.
|
| CIM-26774
|
The Select action used for multivalue attributes in a rulebase did not work as expected in the
UI Builder custom page. To support the rulebase on the
custom UI page, define the following condition for the constraint 'capabilitySecondary':
<condition>
<defined>
<var>capabilityPrimary</var>
</defined>
</condition>
|
| CIM-26766
|
The drop-down list attributes defined in the rulebase were not displayed on the
UI Builder custom page.
|
| CIM-26763
|
When you modified a record that contained a work item in the Timed out state, a new work item was generated for the same record.
|
| CIM-26754
|
An error occurred when you ran the login REST services from soap UI for the user that hold LDAP credentials. LDAP authorization is now supported in REST services.
|
| CIM-26750
|
When importing 8.3.x version metadata, a null pointer exception occurred for the AttributeHistory and PrecedenceManagement attribute properties.
|
| CIM-26741
|
When using a customized database sequence to generate PRODUCTID, the sequenced values assigned to records were skipped.
|
| CIM-26721
|
Record Add or
Record Modify operations were stuck when the "com.tibco.cim.record.useSaveLock" property was set to true.
|
| CIM-26701
|
When uploading data for repository with classification scheme, if the custom PRODUCTID was used as the column name, an error occurred in the event during the ManualClassification activity.
|
| CIM-26698
|
When adding, modifying, and importing a record, the Translate activity failed to translate the document from XML to PDF.
|
| CIM-26608
|
If you created a record with an attribute value that contained a plus (+) sign and viewed the same record on the
Browse and
Search page, the attribute value was converted into its HTML code.
|
| CIM-26529
|
The value of the related record attributes were shown blank when the relationship was rendered as a tab using the
recordui-render.xml file.
|
| CIM-26497
|
Merging of child records with the existing matching records was not working using the custom matcher in data quality import workflow.
Note: To compile the Java source files, merge the classes from the hotfix JAR with
ECMClasses.jar and
AllECMClasses.jar and copy it in the build path to avoid compilation errors.
|
| CIM-26488
|
Unable to create custom inbound integration queues from the Configurator. The default value of the
maxPostSize parameter was previously set to zero (0) because of which the post request failed. To resolve the issue, remove the
maxPostSize parameter from the
conf/server.xml file.
|
| CIM-26476
|
On the data quality merge work item page, all matching records were not displayed. This issue occurred when the SQL Server database was used with TIBCO MDM.
|
| CIM-26462
|
An error occurred in PrepareforImport activity during importing records when the data source tables were in another schema. The issue occurred when the Oracle database was used with TIBCO MDM.
|
| CIM-26313
|
Weightage-based precedence rule did not return the correct result.
|
| CIM-26234
|
When the repository contained more than 10, 000 records and you ran the record query web service request, a schema validation error occurred.
|
| CIM-26182
|
The bulk indexing of records in Patterns-Search did not work correctly. Individual indexing updates were done instead of batch updates.
|
| CIM-26178
|
In a workflow, when you modified a record multiple times in the Item Correction mode, the workflow stopped working at the UpdateRecordState activity. This issue occurred when the total number of records processed exceeded RecordPerAsyncCall.
|
| CIM-26142
|
When searching for records from the web service or the UI, if the search criteria included an underscore character (_), list of incorrect records was displayed.
|
| CIM-25472
|
By using the Record Query web service, you could not run a query on work items with the following filters: STATE, EVENTREFERENCE, RECORDATTRIBUTE, WORKITEMTYPE, and DOCUMENTTYPE.
|