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-06/  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 06 are:


AF-1754

Orchestrator was not consuming some of the plan item execution responses from the EMS queue.


AF-1673

Several incoming ActiveFulfillment Orchestrator destinations were not suspended and hence the Orchestrator engine failed to process the messages on these enabled destinations due to the unavailability of process component model.


AF-1610

AOPD crashed due to high CPU usage and the 'Out of Memory' error in case of the Crosslink Affinity.


AF-1599

Common characteristics of the auto-provisioned products were not identified.


AF-1574

Run periodic cleanup of only Activity Log with date and order status as parameters.


AF-1572

ConditionalAffinity feature is now available which contains additional configuration fields and rules that combine the capabilities of InLink and CrossLink affinities in
a single affinity type.

ConditionalAffinity provides flexibility and allows plan items to be grouped together under different conditions for the two different affinity types.
To implement this, the following changes have been done:
i) To determine the logic of the affinity grouping, configuration fields and xpath    expressions have been added.
ii) The Product repository is modified and ActiveFulfillment AOPD logic is enhanced  to interpret the affinity rules.


AF-1571

ProductDependsOn (PDO) feature is now available which creates more flexible product decomposition.

The ProductDependsOn relationship has been added that allows flexible Product decomposition and links a Product to another Product. This is evaluated during the
process of ActiveFulfillment decomposition and it is different from the ProductComprisedOf (PCO) relationship. Also, the ProductRequiredFor (PRF) relationship has been modified to include the attributes for PDO.


AF-1554

AFI Request Reply always used PERSISTENT delivery mode.


AF-1553

AF-AffinityGroup CrossLink was not working with only one level in the product hierarchy.


AF-1549

AF- Reuse of Common Products during Plan generation in AOPD.
Consider the following product model with the PCO relationship:
PARENT --> (PCO) CHILD_1 (Autprovision=false)
PARENT --> (PCO) CHILD_2 (Autprovision=false)
In the above product model, consider the LinkIDs are assigned to the child products and not to the parent product. For example:
1) Product PARENT (no LinkID specified for the parent product)
2) Product CHILD_1 {LinkID=ADD-1}
3) Product CHILD_2 {LinkID=ADD-2}
A parent product depends on the child products even if it is not assigned a LinkID in the orderline.


AF-1502

OMS configurations are now improved to configure fault tolerant JMS servers.