TIBCO(R) Fulfillment Catalog 3.0.2 Hotfix 01 is now available
Article ID: KB0103199
Updated On:
| Products | Versions |
|---|---|
| TIBCO Fulfillment Catalog | - |
| 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/3.0.2/hotfix-01"
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 3.0.2_HF-001 (This Release)
AC-2059
During full import of data, DB deadlock errors were observed when batch of
products, having multiple relationships, were updated.
AC-2058
Publishing a Catalog to a fixed location using bulkmodelpublish workflow was
resulting in an error.
AC-2041
The Partial Import feature did not delete the unwanted records in some cases.
The records were getting rejected in the workflow and this resulted in the
records not getting deleted.
AC-2002
The GetEventDetails web service used to fail, for the Enterprise Data Export
Event, on PostgreSQL.
AC-1976
Empty DBEM_<PROCESSID>_<CatalogId> tables were not getting dropped after
exporting the records.
NOTE: Henceforth, the DBEM tables are dropped automatically. However,
the users have to manually remove the existing DBEM tables.
AC-1956
When using Import, Export, Publish, or Hierarchy Management, the application
was unable to retrieve the right user profile. This caused one of the following
errors to be displayed:
- No User Information available
- WFL-5090: Event does not exist or executed in memory
- Record not found though there is record present in that enterprise
The errors would not be displayed if the workaround was implemented. The
workaround included restarting the application, or using web services
(although the errors were sometimes seen when the web services were used).
The issue has been fixed.
Issue/Introduction
TIBCO(R) Fulfillment Catalog 3.0.2 Hotfix 01 is now available
Environment
ALL
Feedback
Yes
No
Powered by
