TIBCO(R) Fulfillment Order Management 4.0.2 - HF-10 is now available

TIBCO(R) Fulfillment Order Management 4.0.2 - HF-10 is now available

book

Article ID: KB0101058

calendar_today

Updated On:

Products Versions
TIBCO Fulfillment Order Management 4.0.2

Description

TIBCO(R) Fulfillment Order Management 4.0.2 - HF-10 is now available

Issue/Introduction

TIBCO(R) Fulfillment Order Management 4.0.2 - HF-10 is now available

Environment

ALL

Resolution

This hotfix can be downloaded from the TIBCO Support Web User Interface using your username and password for the TIBCO Support Web. Once logged in, you can find the hotfix under the Downloads Menu: "AvailableDownloads/ActiveFulfillment/4.0.2/Hotfix-10"

Files available for download: 

- TIB_fom_4.0.2_HF-10_readme.txt
- TIB_fom_4.0.2.md5
- TIB_fom_4.0.2-HF-10.zip

Please take a look at the Readme file for the instructions on how to apply the hotfix.

================================================================================
Closed Issues in 4.0.2_HF-10 (This Release)

AF-12695
The Data-Comparison tool gives incorrect responses for some use cases.

AF-12665
The model loading messages now have separate statuses as "Failed" and "Success" 
in two distinct topics.

AF‐12386
The performance of the Data‐Comparison tool has improved by changing the 
following configurations:
All the records from the two tables are merged, and then the records are compared.

AF-12318
The server_cache table issue in the Data-Comparison tool has been fixed.

AF-11966
Logging has been added to the Data-Comparison tool.

AF-11779
The server_cache refresh delay is now configurable when you load models by 
using TIBCO EMS.

AF-11778
The Swing-Message tool listens for the OMS Model loading notification and it 
enables a switch between two OPE clusters.

AF‐11767
When OPE starts refreshing the in-memory models, the OPE Health Endpoint 
generates a false (unhealthy) response. 
A flag is introduced to handle a scenario wherein the load-balancer uses a 
polling mechanism to check if the node is down, and the OPE node stops 
responding before the polling comes in.

AF-11694
After the fourth amendment, plan items and dependency are missing from the order.

AF-11580
The issue related to high CPU queries from Fulfillment Order Management to PostgreSQL 
has been fixed.

AF-11398
After the amendment, the plan calculation in COMP planItem does not display correctly.

AF-11108
Order Lock is not released after an opd failure in the amendment.

AF‐9888
When you migrate the orders from Fulfillment Order Management_3.0.2 to 
Fulfillment Order Management_4.0.2, the expected responses are not generated.

AF-8917
Fulfillment Order Management fails to load the tenantid_OfferIdMappings.xml file.

AF‐6040
Order Submission TimeOut occurs when the members are down for a long duration 
in Fulfillment Order Management.