Description:
The hotfix can be downloaded from the TIBCO Support ftp server, support-ftp.tibco.com. Please use your eSupport username and password to access the server. After connecting, go to /available_downloads/ActiveFulfillmentFramework/ActiveFulfillment/1.2.0/hotfix-10/  to download the hotfix.

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.


The defects fixed in AF 1.2.0 Hotfix 10 are:

AF-3838
The OCV was throwing BatchUpdateException, when attempting to load products into
the ActiveCatalog, and was getting disabled. The issue has been fixed by assigning
a value of memory only to the ProductParentIDStringHolder concept, because the
ProductParentIDStringHolder concept did not require to be saved in the cache or
database.

AF-3834
The dependencies in the execution plan were unexpectedly broken when the orderline
sequence changed. The issue has been fixed.

AF-3183
When an order was cancelled, the compensate plan item started execution along with
the activation of the original plan item, which was cancelled. This caused issues in  
orchestration. The issue has been fixed by assigning dependency to the compensate
plan item on the original plan item, which was cancelled. The compensate plan item
now starts execution only after the original plan item is cancelled.

AF-3182
BW client was inconsistent in sending security credentials in SOAP/JMS calls. There was
an intermittent failure in sending the credentials in some of the messages which resulted
in the OMS server throwing "org.springframework.security.authentication.
BadCredentialsException: Bad credentials" exception, and returning as a SOAP fault to the
BW client. The issue occurred due to a defect in BW (BW-15780) and was fixed in 5.9.2
HF18 version. The BW version should be upgraded to avoid the issue.
  
AF-3140
If the product names of various products had a similar beginning and dependent product
characteristics, it led to circular dependency during the generation of the plan, as
the comparison was made using CONTAINS on the DependentProduct name, instead of
performing a complete product name similarity check. The issue has been fixed.
  
AF-2649
Sometimes Orchestrator/TDS BE engines failed in loading the order instance from the
working memory, during the plan development, and returned empty GetOrder response for
the corresponding GetOrder request call from the BW process in AFI. The issue has been
fixed in the BE engines and the order instance was first fetched from the working memory
using "Instance.getByExtIdByUri" calls as it was done earlier. If the order instance was
NULL and not found in the working memory, then it was fetched from the cache using the
"Coherence.C_CacheLoadConceptByExtIdByUri" call so as to map correctly to the GetOrder
response.

AF-2637
The plan generated using HF-009 was different than the one generated using the HF-008
version. The issue has been fixed.

TIBCO ActiveFulfillment 1.2.0 Hotfix 10 is now available

Product: TIBCO ActiveFulfillment Version: OS: --------------------