Description:
TIBCO FOM 3.0.2 Hotfix01 is available        
                                            
The hotfix can be downloaded from the TIBCO Support ftp server, mft.tibco.com. Please use your eSupport username and password to access the server. After connecting, go to /AvailableDownloads/ActiveFulfillment/3.0.2/hotfix-01/ to download the hotfix.

Instructions on how to apply the hotfix are provided in the TIB_af_3.0.2_HF-001_readme.txt file.

================================================================================
Closed Issues in 3.0.2_HF-001 (This Release)

AF-7005
Dead letter processing has been enhanced by introducing the following operations:
"getOrchStatus" - This operation returns the status for a given node ID indicating
if the node is in INIT or STARTED state.
"moveJMSMessage" - This operation can be used to move messages from a source to a
target queue and also change the value of the "originator" header if indicated by
the caller. All operations can now be performed for any node ID from any different
node ID. All time dependency related operations have been removed since they are
no longer relevant after the change in the time dependency functionality.

AF-6999
An enhancement has been made to the ValidateOffer web service for OPE. The error
response for "GROUP_CONSTRAINT_VIOLATION" now lists the products which are part of
the group causing the rule violation.

AF-6996
TDS queue names have been changed to match the TDS queue names.

AF-6986
The UpgradeOMS_FOM3.0.1_to_FOM3.0.2.sql migration script did not support the
Oracle SE (standard edition) database.

AF-6984
NullPointerException in OrchestratorMemoryCache occured when processing orders.

AF-6941
When restarting Orchestrator, sometimes orders would get stuck in an OPD status.

AF-6940
When restarting Orchestrator, sometimes orders would get stuck in a Feasibility
status.

AF-6939
In an orderline, if a ProductComprised of chain was created with multiple
products, it did not work. This issue was not observed if a UDF was used in
an order line.

AF-6938
When doing a backup of nodes, a few nodes remained in the INIT status after a
resource failure. On recovery, the nodes did not start because the BatchProcessor
thread was in an error state.

AF-6937
If you amend or cancel existing orders and if the EMS shuts down automatically,
some errors were displayed because of resource failure. If the EMS was restarted
and if the orders in the dead table were re-injected using the JMX tool an
exception was displayed. 

AF-6936
There was a delay during model loading from the database in the case of a server
restart. After model loading the computations that are done using the data in
the product models are now done simultaneously for multiple products.

AF-6935
Now planItemId is coming in the getPlanItem trace lines at the INFO level when
starting and finishing the TDS call, instead of only planid.

AF-6915
The milestone release request contained the plus character (+) instead of
corresponding spaces.

AF-6894
When the state machine pagination limit has been reached, TIBCO Fulfillment
Order Management performance is affected.

AF-6823
With the 3.0.0 release, OPE replaced and subsumed some of the functionalities
of OCV. The inventory functionality from OCV was not implemented by OPE and the
integration was removed from OMS. This integration has been implemented and the
interface in the application is able to fetch inventory data from any external
engine.

AF-6690
The total price in the GetPrices web service was not truncating the value.

AF-6503
Using decomposition to check an existence of a particular product within the order
was not working.

TIBCO FOM 3.0.2 Hotfix01 is available

FOM 3.0.2