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/7.2.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 72.0 Hotfix 5 are:

1-9TSA1H       
When the CatalogValidation parameter of the EvaluateRulebase activity was used, the following error was displayed:    SQL-8201: Database error is thrown.This has been fixed.

1-9TOVNY      
If the admin user also had a work supervisor role, the Inbox user dropdown did not work. This has been fixed.

1-9RYWPU    
The Record-Query ValidValues (Init) web service failed to execute rules in a rulebase, if a value for an attribute was specified in the request file. This has been fixed.

1-9U244Z    
An mlXML document created in TIBCO BusinessWorks did not correctly insert data into CIM. This has been fixed.  

1-9RZ45F
Visibility of attributes was not returned correctly while using web services. This has been fixed.

1-9Q1SZ1    
When validating an mlXML document with relationships, a validation error was displayed with the CatalogAction.xsd file. This has been fixed.

1-9UIJHI
If the user date format was set to "YYYY-MM-DD", the following error was displayed While searching for records using the user interface:  Internal Error during conversion of string to date : Unparseable  date: "2008-01-01" : Date is = 2008-01-01 and format is : MM/dd/yyyy
This has been fixed.

1-9VD4WP
When two versions of the same record were compared, incorrect relationship information was displayed on the Compare screen. This has been fixed.

1-9VD4W7    
Relationships between records were not maintained properly when onerecord was a part of two imports happening simultaneously. Also, the
relationship was lost while importing related records in the samedata source. This has been fixed.

1-9VGDWJ
Import was slow as the activity created a productkey and loaded the productkeys and records to the cache. This has been fixed.
Pre-population of productkey and pre-loading can be disabled by adding the following property to the ConfigValues.xml file:
&ltConfValue description="Specifies whether a productkeys should be generated and preloaded done during import. The default is true,
that is, create and preload." isHotDeployable="false" name="Bulk Insert and cache Product Key" propname="tibco.optimization.import.preprocess"
sinceVersion="7.2" visibility="Advanced">&ltConfBool default="true" value="false"/></ConfValue>

1-9VIQ62
For catalog CopyMetaData, when the relationship type was passed as null/empty/-1, the type was not automatically generated as in the
case of the user interface. This has been fixed.