Description:
TIBCO FOM 2.1.2 Hotfix06 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/2.1.2/hotfix-06/ to download the hotfix.

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

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

AF-6874
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-6841
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-6832
Messages were not forwarded to the dead queue for
tibco.aff.oms.ordersService.amendment.task.

AF-6828
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-6817
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-6800
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-6779
When sending an empty or wrong PlanItemID in the response, the order would end up
in the dead letter table. Complete the following steps to recover from this issue:
1. Stop all Tomcat instances.
2. Delete the entry of this order in the dead letter table.
3. Start Tomcat instances, and send good execute reply.
If this does not work, withdraw the order and submit it again.

AF-6729
The plan would get partially saved, and therefore, it got stuck in execution
and was not visible on the OMS UI during a restart.

AF-6705
Processing from a dead letter of batch that contained SetPlan, sometimes led to
an empty PlanfragmentID saved in the Plan_Item table during a restart.

AF-6702
The "waitAtMilestoneID" value in PlanItemExecuteRequest had milestoneID for
the milestone which was already completed.

AF-6701
The order execution plan contained a non-existing planitemID reference in
dependentID field after an order was amended

AF-6672
Sometimes the AUDIT_TRAIL table would get populated with audit trail records
even though the audit trail flag was disabled in the ConfigValues_OMS.xml file.

AF-6627
During a database resource failure, some amendment and cancel actions were
stopped.

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

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

AF-6472
When the Grid view by product name was configured, the OMS UI would show
only one product even if more than one item was in the execution plan. You can
use a PlanItem display template for Grid View on the OMS UI. The following are
template variables you can use:
- PlanItemID
- PlanFragmentID
- ProductID
- Action
- Description
These template variables are case sensitive and have to be specified within curly
braces ({ }). {PlanItemID} must be included as a mandatory variable in the template.
Different template variables can be combined with any type of delimiter along with
PlanItemID. For example, when setting the value of the flag PlanItem Template for
Grid View to Description or ProductID, set the value of the flag to
{Description}|{PlanItemID} or {ProductID}|{PlanItemID}.

AF-6465
After canceling an order and not replying to the suspend action but executing the
response of the same plan item, the amendment would stay in a SUBMITTED status.

AF-6464
Some setPlantItem UDFs would get lost when creating new UDFs during an amendment.

AF-6441
Indefinite locking occurred on the plan item records during TDS calls when
introducing retries and retry delay, therefore, avoiding possible row lock
contentions.

AF-6378
With more than 15,000 products to load, the execution of orders would stop during
the model loading.

AF-6101
This fix reduces the number of JAXBContext objects that are created for order
processing.

AF-5975
Canceling an order failed with an AMENDMENT_INVALID_ACTION_AND_UDF
exception when using a UDF XML file in the order line.    

TIBCO FOM 2.1.2 Hotfix06 is available