Description:
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/2.1.2/hotfix-03/ to download the hotfix.

Instructions on how to apply the hotfix are provided in the TIB_af_2.1.2_HF-003_readme.txt file.

================================================================================
Closed Issues in 2.1.2_HF-003 (This release)

AF-5969
An error was displayed during distribution of orders if multiple instances of
OMS were opened.

AF-5958
Compensation was missing when a plan item was removed during amendment.

AF-5952
When an amendment was executed the REDO plan item was not getting created and
the issue occurred randomly.

AF-5949
If the following properties:

- com.tibco.fom.orch.submit.order.receiver.count
- com.tibco.fom.orch.submit.order.nullOriginator.receiver.count

were assigned different values, an error was displayed. The error was displayed
only when the values for the two properties were different. If the values were
the same the error was not displayed. A dependency between both the properties
was causing the error. The issue was fixed by removing the dependency and the
two mentioned properties are now independent and no longer display an error
when different values are assigned.

AF-5943
If an error occurred during the execution of a process component (for instance a
database failure during the execution of a GetPlanitem interface), it was noticed
that the header properties "ns" and "nm" were created with empty values.

AF-5909
Order Amendment was not getting completed because the system assumed another
amendment was in progress.

AF-5891
It was not possible to withdraw order that went into dead letter due to error in
its processing. The issue has been fixed by ignoring the batch error in case of
withdrawal of order, and removal of corresponding dead letter entry.

AF-5879
If an order contained two (or more) same plan fragments, the information about
the plan fragment always remained the same for all the corresponding plan
fragments.

AF-5860
The GeneratePlan web service was returning a fault code in SOAP service.

AF-5829
An order, which is in prequalification state could not be withdrawn. The issue
has been fixed by enabling the state machine to recover using the correct
state name.

AF-5827
If two plan items were executed sequentially, and if UDFs were added to the
first plan item that was needed in the second plan item, it was observed that
the second plan item started before receiving response from the first plan
item, and the logs did not have any reference to the response of the first
plan item.

AF-5793
PlanItems were blocked in the suspended status when ShouldFailedPlanItemSuspend
was used. This was happening because the suspend response was sent by the
process component against the activate request, sent by the orchestrator,
for a plan item.

AF-5792
There was a problem in displaying execution plan in GUI, for migrated orders,
which contained a "/" character in the orderRef and planId.

AF-5701
During UDF decomposition, a minor regression occurred on autoprovisioned
products.

================================================================================
Closed Issues in 2.1.2_HF-002

AF-5558
During amendment and cancellation, a temporary plan is generated for the
amended order. The corresponding plan items between the original plan and
temporary plan were being identified based on the productID and lineID
properties in the plan items. These identification checks were insufficient as the
plan items between the original plan and the temporary plan could not be
correlated correctly and caused a NullPointerException.

The issue has been fixed by introducing a new property parentProductID in the aopd
plan item object and checking it while correlating the plan items between the
original plan, and the temporary plan generated during amendments or cancellation.

AF-5324
The maximum number for orderline character size when submitting a request was
set to 10. The maximum number orderline character size has been set to 32.
    
================================================================================
Closed Issues in 2.1.2_HF-001

AF-5424
Performance issue occurred in purge script which deletes orders in COMPLETE
or CANCELLED status. As part of this defect, Purge script performance has been
improved. A separate README.txt file is shipped with the purge script that
includes details and steps required for performance improvements. The
README.txt is located in the $AF_HOME/db/oracle/purge directory.

AF-5405
If an order was submitted and kept in execution for a long time, when jeopardy
was enabled, it was adding many entries for a single order in the
RESOURCEUPDATECK table and the addition of entries was increasing. The issue
has been fixed.

AF-5342
While calling the getexecutionplan web service, an exception occurs in the OMS
log, and the content is corrupted in the orders with XML in UDF's with type
input and output. The issue has been fixed.

AF-5341
Notifications are missing in the JMS header request or schema elements. As per
schema definition, one of the following fields are mandatory:  customerID or
subscriberID. The JMS property called status no longer exists in the order
Notification. These no longer exist in the order Notification. This causes
a parsing exception. The issue has been fixed.

AF-5296
An exception is thrown against the MSGID column in the OMS router table:
Value too large for column. Some of the message IDs are too large to be stored
the routing table. The MSGID column in OMS_ROUTER_TBL is made
VARCHAR2(64 CHAR) to accommodate longer message ids. The issue has been fixed.

AF-5295
When OMS is idle, there is a high CPU consumption. The issue has been fixed.

AF-5255
When canceling an order, an intermediate milestone section exception occurs
while processing the PlanItemSuspendResponse JMS message. The order
cancellation request fails while generating the amendment plan due to the
incorrect assignment of IM dependencies. The issue has been fixed.

AF-5236
When submitting a request using SOAP over JMS, a producer leaks for every
submitted request in temporary queues. In the EMS a producer is created for
each submit order request but not destroyed. The issue has been fixed.

AF-5235
Orders remain in execution state as a deadlock issue is seen in the log file.
The issue has been fixed by altering the notification deletion query to
differentiate between the access parameters and filter conditions. The
issue has been fixed.

AF-5131
While submitting an order, NullPointerException is thrown at different places
during the plan generation when the flag  ABDIncludeCharacteristics=true or
ABDIncludeCharacteristics=false. The issue has been fixed.


AF-4809
If a database query update takes more time in a heartbeat, the cluster logic
fails. The issue has been fixed.
================================================================================

TIBCO FOM 2.1.2 Hotfix03 is available