This hotfix can be downloaded from the SFDC Customer Portal Web User Interface using your username and password for the TIBCO Support Web.

Once logged on you can find the hotfix under the Downloads Menu: "AvailableDownloads/MDM/MDMStudio/4.1.0/hotfix-02"

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.

Closed Issues in 4.1.0_HF-002 (This Release)

CIMS-4718    
Error occurred on opening SQL based data source, which was imported from MDM metadata xml. 

CIMS-4714
TIBCO MDM Studio does not support importing metadata xml with multiple synchronization formats.

CIMS-4713
In the Custom UI page, unable to assign value to PRODUCTIDEXT attribute through rulebase constraint.

CIMS-4707
The rulebase functions did not work in condition when used with Select action in the Custom UI page.

CIMS-4705
The drop-down widget was editable if a record was opened in View mode in the Custom UI page. 

CIMS-4704
The Tooltip format for attributes on Custom UI page was not same as Out-of-the-box record UI.

CIMS-4703
Sequence could not be added to ID attribute if association map was used in the Custom UI page.

CIMS-4692
Additional column was displayed while trying to display only two columns using rulebase for the attribute on the drop-down list in a datagrid in the 
Custom UI page.

CIMS-4679
Record was editable from Custom UI page even though the record was in the workflow and in unconfirmed state.

CIMS-4652
The Clear rulebase action did not work in the Custom UI page.

CIMS-4651
Columns appeared one below the another instead of two separate columns when values
were selected from the drop-down list in the Custom UI page. 

CIMS-4609
Unable to select values from the drop-down list if the attributes were at the extreme
right hand corner of the Custom UI page.

CIMS-4608
In the Custom UI page, editing the child record in a datagrid while it's grand child
was opened for editing within the subgrid gave record exist error message.

CIMS-4604
When PRODUCTID was used in Propagate action, it was exported or deployed as ID instead of PRODUCTID.