| CIM-29217
|
Summary: Mass update does not work on the migrated environment from 8.3.2 to 9.2.0 version for the Microsoft SQL Server database.
Workaround: None
|
| CIM-29214
|
Summary: When purging records from a repository with the
Clear Data option, the
ORA-00060: deadlock error is displayed. The issue occurred on TIBCO MDM container in a cluster environment.
Workaround: None
|
| CIM-29195
|
Summary: The following REST services and parameters are used for internal purposes. Using these REST services and parameters might lead to undesired results.
REST Services
- addModifyRecord
- addModifyRecordWithAttachment
Parameters
- relationshipsToExclude of the
Get Record by ID REST service
- isFromReload and
productKeyId of the
Ge Related Record by ID REST service
Workaround: Avoid using the REST services and the parameters that are marked for internal use.
|
| CIM-29176
|
Summary: The query parameters as map are not supported in the Swagger UI. However, the queryMap request parameter is shown as a mandatory parameter for the REST service to retrieve valid values with classification for the specified repository.
Workaround: Provide a dummy value in queryMap field on the Swagger UI.
|
| CIM-29142
|
Summary: On the
User Accounts page, you cannot create a user if the user name that contains multibyte characters.
Workaround: None
|
| CIM-29138
|
Summary: File upload for the multivalue attribute does not work.
Workaround: None
|
| CIM-29134
|
Summary: When performing the scheduler duplicate detection operations on the Oracle database, the following driver related exception occurs:
java.sql.SQLSyntaxErrorException: ORA-00907: missing right parenthesis
Workaround: None
|
| CIM-29121
|
Summary: In Mozilla Firefox and Internet Explorer, the administrator REST services do not work if you access them using the cross-origin resource sharing (CORS) although the CORS are enabled.
Workaround: None
|
| CIM-29120
|
Summary: The
Matching Records section displays the source records instead of matching records.
Workaround: None
|
| CIM-29064
|
Summary: The
NoFSPurgeSchedule job does not work using the Configurator and using the (CronSchedules.xml) file.
Workaround: None
|
| CIM-29032
|
Summary: (For containerization) After running the Index Entity Checkpoint scheduler job, an error occurs.
Workaround: None
|
| CIM-29016
|
Summary: In the response attribute history of the RelatedRepositoryList and RepositoryListWithDependentArtifacts REST services, the default value of the precedence management parameter always remains false.
Workaround: None
|
| CIM-29009
|
Summary: The File type attribute does not work for the Download and Import data transfer REST services.
Workaround: None
|
| CIM-29006
|
Summary: The cross-origin resource sharing (CORS) for Swagger UI is not supported in Google Chrome and Microsoft Edge browsers.
Workaround: Use Mozilla Firefox and Internet Explorer browsers and enable the CORS support. For information, see the Enable Cross-Origin Support for Swagger UI section in
TIBCO MDM System Administration.
|
| CIM-28999
|
Summary: In the latest version of Google Chrome, the
Try it out option does not work for the POST method related REST services.
Workaround:
- Use Mozilla Firefox or Internet Explorer browsers.
- Use the CURL command available in the Swagger UI.
- Use any other REST client, for example, SOAP UI.
Note: If you come across the following error on any one of the browsers, pass the blank value for the
Content-Type parameter:
{
"errorCode": "",
"errorType": "Error",
"errorMessage": "Invalid mime type \"application/json, application/json\": Invalid token character ',' in token \"json, application/json\"",
"errorDetails": ""
}
|
| CIM-28970
|
Summary: Pagination does not work for the hierarchy management UI when used with Oracle 11g.
Workaround: Use Oracle 12.
|
| CIM-28938
|
Summary: From the
Event Log page, the following event actions are not supported for hierarchy (Create, Edit, and Delete) events:
Cancel,
Resubmit,
Restart, and
Rollback.
Workaround: None
|
| CIM-28903
|
Summary: A new duplicate import event is triggered if you refresh the
Import Status page.
Workaround: Avoid refreshing the
Import Status page.
|
| CIM-28893
|
Summary: Swagger UI does not support multiple uploads for adding or modifying a record.
Workaround: None
|
| CIM-28864
|
Summary: When any hierarchy work item is rejected, a dummy version is created for auditing or tracking purpose. This dummy version does not have any hierarchy node or structure details. In this case, only a root node is displayed.
Workaround: None
|
| CIM-28846
|
Summary: In Microsoft Edge, the left and right navigation options in the hierarchy management UI do not work.
Workaround: Use Google Chrome version 75.x or later.
|
| CIM-28844
|
Summary: The hierarchy management UI might look distorted in the Safari browser.
Workaround: Use Google Chrome version 75.x or later.
|
| CIM-28838
|
Summary: In Microsoft Edge, the
Back button does not work when browsing links from the
Hierarchy Modify page.
Workaround: Use Google Chrome version 75.x or later.
|
| CIM-28836
|
Summary: In Microsoft Edge, the hierarchy tree moves to the left and is truncated when a third level hierarchy is added.
Workaround: Use Google Chrome version 75.x or later.
|
| CIM-28807
|
Summary: You cannot schedule the hierarchy lock expiry and hierarchy linkage cleanup jobs from the Configurator.
Workaround: Manually edit the scheduler job (CronSchedules.xml) file.
|
| CIM-28797
|
Summary: For the closed link approval work item, no entries for leaf node-record ID links are displayed under the
Link and
Unlink fields on the
Browse linkages for hierarchy page.
Workaround: None
|
| CIM-28713
|
Summary: For a data steward user, the work item summary pie chart does not filter the work items correctly after clicking
Closed or
Open sections.
Workaround: None
|
| CIM-28707
|
Summary: For the Classification Extraction method, records are imported but not classified under the defined classifications.
Workaround: None
|
| CIM-28401
|
Summary: Opening a record from the
Create Subset Rule page displays the following error message:
Subset name and catalog name must be supplied:(Undefined).
Workaround: None
|
| CIM-28178
|
Summary: Rejecting a delete hierarchy work item result into a dummy version and this version is displayed on the
Version History page as Rejected.
Workaround: None
|
| CIM-28125
|
Summary: The hierarchy details such as
Name,
Node,
Details are not displayed for the simplified inbox. These details can be viewed from the classic inbox.
Workaround: None
|
| CIM-28029
|
Summary: The Simplified and Extended Inbox pages do not respond to a large number of work items. The issue occurs on the PostgreSQL database.
Workaround: None
|
| CIM-27962
|
Summary: The custom pages that are deployed for the metadata operations (such as view record or modify record) are not displayed on the
Mass Update work item page.
Workaround: None
|
| CIM-27942
|
Summary: When node deletions are rejected, the deleted nodes are not automatically restored for hierarchy correction.
Workaround: Manually create the node with the help of the information already present on the hierarchy page.
|
| CIM-27736
|
Summary: In Internet Explorer 11, the hierarchy management feature does not work.
Workaround: Use one of the supported browsers.
|
| CIM-27478
|
Summary: The purge functionality does not support hierarchy or hierarchy version purging.
Workaround: None
|
| CIM-27400
|
Summary: Purge using the commandline option generates an error when the
ALL option is used as an enterprise name (-an ALL) along with the member name (-mn) parameter.
Workaround: Use the member ID (-m) parameter instead of member name (-mn).
|
| CIM-27304
|
Summary: The purge
ALL option does not delete records from all the repositories.
Workaround: None
|
| CIM-27280
|
Summary: Importing reused metadata with the custom table names fails. You cannot use the same custom table names for the TIBCO MDM entities, such as repository, relationship repository, and multivalue or category-specific attributes because the database is shared for all enterprises or projects in the environment.
Workaround: Remove or change the custom table name before reusing metadata.
|
| CIM-27279
|
Summary: If you delete a record by using the RightToForget scheduler job and then create a new record by using the record ID and EXTENSION of the deleted record, an error is returned.
Workaround: Clear the cache for the RECORD category or restart the TIBCO MDM server from the Overview pane.
|
| CIM-27264
|
Summary: After setting the
com.tibco.mdm.indexing.indexOnStartuprestarting property to
true and restarting the TIBCO MDM node, checkpoint data is lost.
TIBCO MDM rebuilds the index entities. You must reinitiate the checkpoint of TIBCO Patterns.
Workaround: None
|
| CIM-26298
|
Summary: When you add duplicate multiple child records by using the Add or Modify Record REST service, an error is not returned. Instead, a single related record is added and the duplicate records are ignored.
Workaround: None
|
| CIM-26085
|
Summary: The ActiveSpaces security for golden record cache does not work.
Workaround: None
|
| CIM-26082
|
Summary: Add record UI page with relationships shows the red indicator in the relationship tree when user does not enter any data or does not select the validate action.
Workaround: None
|
| CIM-26037
|
Summary: The Record web service or REST service does not work with
RECORD_STATE having multiple options in it.
Workaround: Execute the service with a single option.
|
| CIM-26030
|
Summary: Rollback event up to the selected step does not work for in-memory workflow event.
Workaround: None
|
| CIM-26021
|
Summary: After migrating from version 8.3.2 to version 9.1.0, an error message is displayed when you add records for the Link to Metadata type custom UI page. However, the records are added successfully.
Workaround: Use TIBCO MDM Studio 5.1.0 release to migrate the studio project and then redeploy the custom pages to link to the metadata operations.
|
| CIM-26013
|
Summary: TIBCO MDM server fails to index records when indexing the relationship attributes in the normalized index entities.
Workaround: None
|
| CIM-25982
|
Summary: Record merge event shows as "In-Memory" on the Show History page.
Workaround: None
|
| CIM-25868
|
Summary: The AM and PM timestamp type is displayed in the specific native locale instead of AM/PM. This issue occurs because the TIBCO MDM server does not use the user profile's locale for the formatting timestamp that is displayed to the user. The TIBCO MDM server picks the default server locale.
Workaround: None.
|
| CIM-25792
|
Summary: Bundle cache does not work as expected when Apache Ignite is used as the Cache type.
Workaround: None.
|
| CIM-25643
|
Summary: The TIBCO MDM Server does not start with Apache Ignite and golden record cache when too many enterprises are configured.
Workaround: None.
|
| CIM-25606
|
Summary: When you run
pgAdmin4.exe from
$MQ_HOME\bin\pgsql\pgAdmin4\bin, a black screen is displayed. The issue occurs if you have installed PostgreSQL on a Windows 2008 Server.
Workaround: None.
|
| CIM-25587
|
Summary: Copying a repository with the manual classification scheme does not copy over the classification scheme and the classification level to the copied repository.
Workaround: None
|
| CIM-25519
|
Summary: The Compare Record REST service does not support comparison of relationship records and relationship attributes.
Workaround: None
|
| CIM-25327
|
Summary: Attribute group name with multibyte characters is not accessible on the Browse and Search page. The issue occurs only on the Mozilla Firefox browser.
Workaround: None
|
| CIM-25006
|
Summary: Generating Record ID through rulebase constraint for child records during Record Copy Action is not supported.
Workaround: None
|
| CIM-24785
|
Summary: Geo analytics configuration does not allow you to define address cleansing as enterprise specific.
Workaround: None
|
| CIM-24226
|
Summary: After clicking
GEO Tab on the Record UI page, a pop-up with a list of addresses based on the location is displayed even though the
Lookup button has not been clicked.
Workaround: Close the pop-up.
|
| CIM-24202
|
Summary: The scale for decimal type values cannot exceed seven for adding records.
Workaround: None
|
| CIM-24144
|
Summary: The data transfer feature has problems with the custom decimal type on a Microsoft SQL server.
Workaround: None.
|
| CIM-24007
|
Summary: The View record page of the Data Quality work item UI only shows the
Quick Export option for child records.
Workaround: None
|
| CIM-23971
|
Summary: If a parent record has three relationships with the same grand-child, it is not indexed in the Netrics table.
Workaround: Break the record bundle.
|
| CIM-23965
|
Summary: The use of child attributes in a matching-attribute list for scheduler duplicate detection throws an error in the logs.
Workaround: None
|
| CIM-23872
|
Summary: The synchronization profile fails at the ConvertRecordToOutput activity because the CatalogReference details are not populated as a part of the GetItem activity.
Workaround: None.
|
| CIM-23832
|
Summary: When executing web services and REST GET records by repository name requests with the work item ID and record state parameters, the web services response contains the records in the draft state but the REST response is empty.
Workaround: None
|
| CIM-23808
|
Summary: With Text Search on the UI, the value of 'search in' changes after the record operation.
Workaround: None
|
| CIM-23801
|
Summary: With the all-in-one installer, the Process Definition Selection contains the same action twice: "Wfin26dqcatsourcev1.xml-Process for data source update and import with DQ".
Workaround: None
|
| CIM-23772
|
Summary: Search requests with supported operators with supported data types give an invalid result.
Workaround: None
|
| CIM-23755
|
Summary: When importing duplicate records, merging each record from the first page of the work item details, and then when clicking an already merged record, the application throws a null pointer exception.
Workaround: None
|
| CIM-23712
|
Summary: Direct merge after modifying a record deletes the source record from the netrics table.
Workaround: None
|
| CIM-23709
|
Summary: For POST add records with invalid values for relationship attributes of different data type, the response contains an invalid error message and the record is added on the UI without relationship attribute values.
Workaround: None
|
| CIM-23705
|
Summary: When executing a POST add record request with a different timestamp format, the relationship attribute of the different timestamp type is not added on the UI and the response contains an invalid error message.
Workaround: None
|
| CIM-23681
|
Summary: Data Quality does not show the correct order of matching child records.
Workaround: None
|
| CIM-23651
|
Summary: The "Data Service Update" event succeeds even though there is no metadata present in the target enterprise.
Workaround: None
|
| CIM-23641
|
Summary: Only the child record is shown on the Browse page of Event Details when a self-related output map is used with different sync format for synchronization.
Workaround: None
|
| CIM-23633
|
Summary: When searching for an attribute in the
Configure window, no attribute is shown even if the exact attribute name is searched.
Workaround: None
|
| CIM-23624
|
Summary: Users are not able to search record details if the milliseconds "S" value is 030 or 30 on the record.
Workaround: None
|
| CIM-23612
|
Summary: There is a pagination mismatch on the
Synchronization Profile page and other UI pages.
Workaround: None
|
| CIM-23600
|
Summary: The multi value file type attribute is not supported through UIBuilder.
Workaround: None.
|
| CIM-23593
|
Summary: A GET request with a repository name and record count and record index value as 1 gives an empty response.
Workaround: None.
|
| CIM-23501
|
Summary: When specifying the "Record Count" and "Start Index" value from the query parameter, the Search Post request does not work correctly.
Workaround: None
|
| CIM-23485
|
Summary: When using the rest service delete operation, and in the case of using the reverse self relationship, the operation may also delete the parent record.
Workaround: Use the delete REST service to delete the parent record.
|
| CIM-23453
|
Summary: When selecting
Check Existence for more than one relationship on the UI, a parallel line after the
Check Existence check box and the
Count check box after the second relationship is shown.
Workaround: None
|
| CIM-23450
|
Summary: When adding a duplicate child record from the source to the target, validation does not throw an error.
Workaround: None.
|
| CIM-23442
|
Summary: In text search, when the child record is matched for the searched string, the same matching score is shown to all the remaining child records.
Workaround: None
|
| CIM-23419
|
Summary: The
Is defined and the
Not defined operators are not working with the REST services.
Workaround: None
|
| CIM-23411
|
Summary: In text search, users are not able to search for a timestamp attribute value along with one searchable text string.
Workaround: None
|
| CIM-23401
|
Summary: All the input/output parameters for the "Show more Details" section on the View Event Details page for Data Transfer event (Load Data Source and Import Records) are not enhanced.
Workaround: More information regarding this event can be found in the Additional Data section on the View Event Details page and in the Event Log file.
|
| CIM-23393
|
Summary: A mandatory defined rule does not work for relationship attributes with REST web services.
Workaround: None
|
| CIM-23326
|
Summary: The
Show Different Values option is not available on the Merge Record Details page in the 9.0.1 version of TIBCO MDM. This functionality was available in the 8.3.2 version. Due to the redesign of the merge work item, this functionality is hard to display and therefore requested to add back.
Workaround: None.
|
| CIM-23256
|
Summary: The work item summary filter does not work correctly if the attribute value starts with a space.
Workaround: None.
|
| CIM-23239
|
Summary: Multi value attributes are not supported for the work item summary filters. The ordering and depth cannot be easily predicted.
Workaround: None
|
| CIM-23166
|
Summary: Join entity is not indexed after direct load.
Workaround: Reindex the join entity.
|
| CIM-23100
|
Summary: A record post request with an invalid syntax for multi value attributes gives a record add success message in the JSON response.
Workaround: None
|
| CIM-22817
|
Summary: A boolean attribute is rendered in lower case letters on the UI if the record renderer customization is used.
Workaround: None
|
| CIM-22711
|
Summary: After incremental deployment, a null pointer exception occurs on creating a record.
Workaround: In the case of incremental deployment of metadata, if the following operations are performed on any repository having perspectives, you must select those perspectives while importing the metadata:
- deleted related repository and repository attributes
- updated relationships
|
| CIM-22666
|
Summary: Exporting relationship output map through the export wizard UI is not supported.
Workaround: Export metadata using XML file.
|
| CIM-22655
|
Summary: With data quality merge, the relationship attributes are not merged during the direct merge.
Workaround: None
|
| CIM-22611
|
Summary: In the Merge UI (Manual Merge and Work Item Merge) the drop-down lists are not editable. Inline editing is disabled.
Workaround: None
|
| CIM-22516
|
Summary: Subset rule with a list option throws an error when the data source attribute of a type other than string is used in the filter criterion with a non-string attribute repository.
Workaround: Use the string attribute in the data source.
|
| CIM-22436
|
Summary: Related records are not loaded on Internet Explorer 11 after using globalized data.
Workaround: None.
|
| CIM-22347
|
Summary: Roll back for item corrected record version does not rollback manual classification.
Workaround: None.
|
| CIM-22345
|
Summary: Rollback for corrected record version does not rollback manual classification.
Workaround: None.
|
| CIM-22333
|
Summary: Event rollback does not work correctly when future dated records are modified by changing the effective date.
Workaround: None
|
| CIM-22252
|
Summary: Rollback of correction does not work correctly when relationships need to be reverted.
Workaround: Manually revert the relationship using database queries.
|
| CIM-22141
|
Summary: The standard and velosel folders are created in the$MQ_HOME/common folder even though the customized path is provided while installing TIBCO MDM.
Workaround:
- Update the value for the
$MQ_COMMON_DIR environment variable
or
- Copy the standard and velosel folders from the
$MQ_HOME/common folder to
$MQ_COMMON_DIR
|
| CIM-22128
|
Summary: The back button on the error popup window triggered through the inbox with access restriction is not working.
Workaround: Close the error window.
|
| CIM-21884
|
Summary: Running purge in the repository or enterprise mode might not purge everything due to deadlocks.
Workaround: Purge records and metadata separately.
|
| CIM-21701
|
Summary: The Patterns configuration setting are not listed in the TIBCO MDM silent installer file. The issue is observed on for the Linux and Windows platforms with WebLogic or WebSphere application servers.
Workaround: Add the following Patterns settings after the Configurator Settings in the TIBCO MDM silent installer file:
<!-Patterns Settings->
<entry key="patterns.ui.port">9080</entry>
<entry key="patterns.server.port">5051</entry>
<entry key="patterns.windows.service">false</entry>
|
| CIM-21661
|
Summary: When a record is in workflow and the work item is not locked, a different user can browse and search the record, and then modify it.
Workaround: None
|
| CIM-21645
|
Summary: The FILE type attributes are not supported with Precedence Management.
Workaround: None
|
| CIM-20873
|
Summary: When a record version is corrected multiple times using the Correction action, the Version History page shows an incorrect name for the member who modified or corrected that version. All rows on the history page for that version shows the name of the member who corrected it last.
Workaround: None
|
| CIM-20871
|
Summary: Sometimes using an output map to filter the result of a record query service call on a SQL Server can cause an error.
Workaround: None
|
| CIM-20801
|
Summary: Instead of browser-based drop-down lists, some pages on the UI display custom drop-down lists for the pagination bar.
Workaround: None
|
| CIM-20426
|
Summary: Special characters, such as the forward slash (/) and back slash (\), are not permitted as part of the index entity names.
Workaround: None
|
| CIM-20212
|
Summary: Special characters (such as the ASCII control characters) are not handled correctly when writing attributes containing them are written out to the HTML page or are included in the URL. This includes PRODUCTID and PRODUCTIDEXT.
Workaround: None
|
| CIM-20165
|
Summary: When using the Correction action to remove a relationship and then another item correction request to create the same relationship again, it does not create the relationship.
Workaround: None
|
| CIM-20073
|
Summary: If a record contained non-Japanese double-byte character sets (DBCS) characters, the Connect action fails. The issue occurs on the SQL Server database.
Workaround: None
|
| CIM-19752
|
Summary: The Custom Decimal data type considers the minus (-) or the plus (+) symbol as a digit in the precision.
Workaround: Plan the custom decimal one digit larger than what the actual size requires.
|
| CIM-19745
|
Summary: For text search, when reducing the similarity score to less than 0.4, no records are displayed.
Workaround: None
|
| CIM-19704
|
Summary: The hot deployment feature does not work as expected if the landing page is customized.
Workaround: None.
|
| CIM-19532
|
Summary: For certain customized workflows, the parent records version gets increased without any modifications done to it's attributes.
Workaround: None
|
| CIM-19499
|
Summary: On the record UI, the customized renderer loses selection if the page is refreshed. The customization includes a display drop-down list with the radio button for an attribute and the ShowAsRadio constraint.
Workaround: None
|
| CIM-19445
|
Summary: The Moddate value is not updated correctly in the
MEMBER and
MEMBERHISTORY tables when the user is changed or deleted.
Workaround: None
|
| CIM-19293
|
Summary: Merging of two records with a multilevel classification scheme and the category specific attributes does not work in specific cases.
Workaround: None
|
| CIM-19256
|
Summary: The
Detected Old Installation window is not displayed when you select the Migration option in the Configurator to migrate from an earlier version to version 8.3.2.
Workaround: Manually migrate 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-19128
|
Summary: Importing repository metadata with the synchronization format fails with the following error:
CAT-1027: Stale data; data modified by another user or process. The issue occurs on the PostgreSQL database.
Workaround: Import synchronization format first and then the repository metadata.
|
| 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 page with the corresponding business process rule.
Workaround: None
|
| CIM-18869
|
Summary: The
ORA-00933: SQL command not properly ended exception occurs when slice action is used with the datasource and the datasource name has a hyphen (-) character.
Workaround: None.
|
| CIM-18614
|
Summary: When using the Add or Modify SOAP web service with a grandchild is present in the request, the version sometimes increases for the sibling child without any changes saved.
Workaround: None
|
| CIM-18221
|
Summary: The Record Modify web service with
Version_Policy=Correct can correct the UNCONFIRMED record version to make it CONFIRMED. The existing STATE and new STATE are different, and therefore, this is invalid based on the correction version policy.
Workaround: None
|
| CIM-17833
|
Summary: While exporting the permissions from the TIBCO MDM UI, the following error occurs:
Relationship Not Found for the resourceID <resource ID>.
Workaround: None
|
| CIM-17825
|
Summary: Add role based permissions to custom menu items does not work in all scenarios.
Workaround: None
|
| CIM-17214
|
Summary: The PARENT rulebase context variable is not evaluated correctly when the related record is added using the reverse relationship.
Workaround: None
|
| CIM-16963
|
Summary:
MQ_COMMON_DIR is empty when TIBCO MDM is installed using the Silent Installer, even after you specify the
commonConfig_useDefault key as
false and provide the correct path for the
commonConfig_directory and tibco.cim.common.dir keys.
Workaround: None
|
| CIM-16943
|
Summary: When using the Metadata Export GUI wizard, it is possible to select the predefined TIBCO synchronization format, has missing column names, which is causing a schema validation error for imports being attempted on exports containing this predefined format.
Workaround: None
|
| CIM-16893
|
Summary: The uncategorized action based on a number of classification code paths does not work consistently.
Workaround: None
|
| CIM-16844
|
Summary: The scheduler duplicate detection process does not work correctly if the two indexes share the same repository name as the primary or parent, that is, a single repository withIndexEntity joinTable="false" and a cross-repository with
IndexEntity joinTable="true" index. In this case, overlapping indexes, records from matching child records from the cross-repository index are also returned.
Workaround: None
|
| CIM-16530
|
Summary: The indexed attributes in the IndexerConfig.xml file are not automatically updated when the attribute name is changed, and the repository is incrementally deployed.
Workaround: Edit the attribute definition in the
IndexerConfig.xml file.
|
| CIM-16471
|
Summary: With the data quality match and merge workflow, while having the source record merged with a target record through DirectMerge (the source record has only one target match candidate record), if the source and target records have different related records, the related record for the source record does not get merged to the target record in spite of having the
ImplicitRelationshipMerge parameter set as
true in the DirectMerge activity.
Workaround: None
|
| CIM-16274
|
Summary: Inconsistent behavior in the user interface when using repository names starting with a number.
Workaround: Avoid using number leading repository names.
|
| 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-15873
|
Summary: The response of the GetImportEventDetails web service does not return valid counters after the server restarts.
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-15727
|
Summary: An exception is thrown while creating a work item for a large number of users in the specified role. The exception occurs when formatting user names to display them in the Event log page.
Workaround: To avoid the exception and disable the formatting of user names, add the
Formatting User Name property in Configuration ( Tools > Add Configuration Value). Specifying the
False value disables the formatting of user names. Enter the following details in each field:
- Configuration value name: Formatting User Name
- Internal name:
com.tibco.cim.workflow.formatUserName
- Version: 8.2
- Visibility: Advanced
- Description: Formatted user names are displayed in the Event log page. By default, specify the
True value. Setting this property to
False disables the formatting of user names.
- Current Value:
False
- Default Value:
True
- Category: Workflows
Limitation: Currently, the database schema supports only 8000 characters for
stateparam in the
Processstate table. The exception occurs if the combined length of user names and the process state exceeds more than 8000 characters. The fix does not remove this limitation.
|
| CIM-15307
|
Summary: Import of the MassUpdate rulebase fails if another rulebase is deployed with the same name.
Workaround: None.
|
| CIM-15306
|
Summary: Export of the MassUpdate rulebase fails if another rulebase is deployed with the same name.
Workaround: None.
|
| CIM-15305
|
Summary: Export of included rulebases defined for a decision table fails.
Workaround: None
|
| CIM-15187
|
Summary: Classification Scheme was not displayed on the "Record Review and Rejection" page.
Workaround: None
|
| CIM-15085
|
Summary: An SQL statement contains multibyte characters when you start import with the input map. This causes the
Oracle error ORA-936 error.
Workaround: None.
|
| CIM-15033
|
Summary: Modifying a record that contains a Checkpoint activity in the workflow and an REA business process rule results in NullPointerException. If the workflow is suspended, the workflow details might not be persisted correctly, causing problems in opening the work item.
Workaround: None.
|
| CIM-15032
|
Summary: Deleting a record that contains a Checkpoint activity in the workflow and an RDA business process rule results in NullPointerException. If the workflow is suspended, the workflow details might not be persisted correctly, causing problems in opening the work item.
Workaround: None.
|
| CIM-15028
|
Summary: Adding a record that contains a Checkpoint activity in the workflow and a NRIE business process rule results in NullPointerException. If the workflow is suspended, the workflow details might not be persisted correctly, causing problems in opening the work item.
Workaround: None.
|
| CIM-14972
|
Summary: The timestamp based classification tree entries use a uniform format, which is not the same as that of user-selected preferences.
Workaround: None
|
| CIM-14847
|
Summary: A web service request with a timestamp format different from that selected by its user results in a response with an unclear error message.
Workaround: None
|
| CIM-14730
|
Summary: Adding only relationship without merging a parent record does not work as expected.
Workaround: None
|
| 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-14338
|
Summary: If the record is in the latest version, the record cannot be modified through the Record UI.
Workaround: None
|
| CIM-13882
|
Summary: Comparing two dates with <gt> in the rulebase does not always work correctly.
Workaround: None
|
| CIM-13744
|
Summary: For purge, when a shutdown is initiated while the purge is running in the background, exceptions occur on the application server console and
elink.log. Also, the event state remains in progress.
Workaround: None.
|
| CIM-13680
|
Summary: For the download link to appear, the Export Metadata Profile page needs a page refresh (F5) after exporting a previously created profile.
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 multiple times than expected.
Workaround: None.
|
| CIM-12067
|
Summary: With Rulebase, an exception is thrown when using a variable within a concat clause that is used within a like expression.
Workaround: None
|
| CIM-11529
|
Summary: When a large number of single record concurrent modification requests are sent, some records show as UNCONFIRMED on the UI. When the cache is restarted, the state of the record is correct.
Workaround: None
|
| CIM-11517
|
Summary: If a data source contains many duplicate records and relationships, database loader can fail with a duplicate key error while processing the explicit relationships.
Workaround: Choose a slower update interval.
|
| CIM-11143
|
Summary: When records are validated through 'ValidValues', the behavior is not consistent using the user interface and the web service. The UI reports an error but the web service does not.
Workaround: None
|
| CIM-10892
|
Summary: Even when a repository is deleted, the related index entities are still searchable.
Workaround: None
|
| CIM-10614
|
Summary: When manually editing the indexing configuration file (IndexerConfig.xml), you have to specify the attribute names in uppercase.
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-8659
|
Summary: The SQL data source for the date type may have problems when it is imported.
Workaround: None
|
| CIM-7708
|
Summary: A repository cannot be created with a name similar to the previously deleted repository name.
Workaround: None
|
| CIM-5943
|
Summary: Import of data source with images (FILE attribute) can be problematic in certain situations, as the upload happens after the input mappings have already been created.
Workaround: Upload the data source file before creating the input mappings or before redeploying the input maps.
|
| CIM-4220
|
Summary: Setting up permissions for modifying, viewing, and synchronizing a record in case a cross catalog relationship fails with an error message.
Workaround: None
|
| CIM-2085
|
Summary: The Rulebase execution can happen multiple times than needed for editing a record.
Workaround: None
|
