TIBCO(R) Fulfillment Catalog 2.1.0 Hotfix 02 is now available.

Products	Versions
Not Applicable	-

Description

Description:

This hot fix can be downloaded from the TIBCO Support file transfer server- mft.tibco.com.

Server name: mft.tibco.com

Credentials: use your TSC (TIBCO Support Central website) login.

Browser: https://mft.tibco.com

FTP: port 21

SFTP: port 22

FTP using your browser is not supported, please use an FTP client or command-line. TIBCO employees must use a secure protocol. Once logged on you can find the hot fix under: "AvailableDownloads/ActiveCatalog/2.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 2.1.0_HF-002 (This Release)

AC-1482

The import process failed because the attribute ProjectTagName, of data type String, had a size limit of 256 characters. This was not sufficient because the attribute contained all the tags of its relationships, as new projects were generated frequently, the size of the ProjectTagName exceeded the limit quickly. The issue has been resolved and the size of the ProjectTagName attribute has been increased.

AC-1469

During partial import, if a project tag is requested to be completely removed, the tag should be removed from all repositories, including PROJECTTAG as well.

AC-1467

During partial import, records were getting modified which were not related to the tags of the TagNames.csv file. The issue has been fixed and the records no longer gets updated if they are not related with the tags of TagNames.csv file, even if they exist in the enterprise repository and the CSV file.

AC-1466

Records without tags were not being removed after the partial import. The issue has been fixed and records without tags are now removed from the catalog.

AC-1464

During partial import, new tag or tags were added to the PROJECTTAG repository even though TagNames.csv file did not have that tag or tags. The issue has been fixed and the new tag or tags are no longer added to the PROJECTTAG repository if that tag or tags is not present in the TagNames.csv file.

AC-1459

If a value was entered for the OWNER field in the Plan Fragment repositoryusing the FC UI, the value was not appearing in the generated XML file for the Plan Fragment repository. The issue has been fixed and the value for the OWNER field is appearing in the generated XML file for the Plan Fragment repository.

AC-1443

The amount of information written on the base document was affecting the performance of the Publish Model. Sometimes, it resulted in an OutOfMemory exception, if the catalog models in the enterprise exceeded an unknown limit, and if an attempt was made to publish the catalog. The issue has been fixed and the performance has been improved by selectively writing the information to the base document. The selection is based on the workflow configuration and can be modified to suit one's need. Additionally, the OutOfMemory exception is no longer being displayed.

AC-1439

During partial export the PROJECTTAG repository was not including the project tags on which the partial export was performed. The issue has been fixed and the PROJECTTAG repository now follows the same principle that is followed by the other repositories.

AC-1432

Fulfillment Catalog was allowing the creation of multiple instances of the same project tag that were added manually. The issue has been fixed and the error message that appears is a generic error message.

AC-1431

After installing FC 2.1.0_HF-001 the version information was no longer available on the About page. This issue has been fixed and the version information is visible on the About page.

AC-1308

The import of FC_DUMMY_XXX was mandatory before performing an import or export in FC, despite having valid and relevant data present in the enterprise. The issue has been fixed and the import of FC_DUMMY_XXX is no longer mandatory.

Issue/Introduction

TIBCO(R) Fulfillment Catalog 2.1.0 Hotfix 02 is now available.

Welcome to "KB Articles"