This hotfix can be downloaded from the SFDC Customer Portal Web User Interface using your username and password for the TIBCO Support Web.
Once logged on you can find the hotfix under the Downloads Menu: "AvailableDownloads/ActiveFuulfilment/4.0.0/Hotfix-1"
TIB_af_4.0.0_HF-001.zip file includes the Readme file inside. Please unzip this file and look for the Readme file for Instruction on how to apply the hotfix.
================================================================================
Closed Issues in 4.0.0_HF-001
AF-7843
A StackOverflow exception would occur after order amendment if two planItems had
intermediate milestones dependencies on each other.
AF-7824
The OPE ValidateOffer web service response would be different with the same
ValidateOffer web service request.
AF-7822
The price model fetch from the database is now done in chunks like the product
model fetch process.
AF-7821
The Plan Item Milestone Release request event would send unexpectedly.
AF-7812
When there was an ORDER_ALREADY_BEING_CANCELLED error, the jdbc pool would
increase and not return connections to the pool.
AF-7805
A product was missing in the execution plan when ProductComprisedOf=false with
an empty LinkID.
AF-7799
You can now apply IncompatibleSegment to a LinkID for the OPE ValidateOffer
web service. To implement this, add a UDF with the name 'SegmentLinkID' under
the seg:Segment element as well as under the orderline UDF where you want to map
LinkID under the validateOffer request.
AF-7798
RequiredByDate was not in the plan in case of affinity.
AF-7797
After canceling an order, the plan remained in EXECUTION state due to an extra
dependency.
AF-7796
Messages obtained from the tibco.aff.orchestrator.planItem.execute.reply queues
were not getting acknowledged, and the application was processing the same
message multiple times.
AF-7795
When sending an order, the fault soap error
"org.apache.cxf.binding.soap.SoapFault: No security action was defined!"
occurred intermittently.
AF-7794
After installing TIBCO Fulfillment Order Management 3.0.2 HF-4, the planfragment
remained in the PENDING state due to an extra dependency in the plan when
submitting an order.
AF-7793
Messages including replies for all TDS operations are persistent. These messages
can be made non-persistent using the provided configurations.
AF-7792
AFter publishing a catalog from TIBCO Fulfillment Catalog to TIBCO Fulfillment
Order Management, the OPE GetOffer response had misisng products.
AF-7790
OPE was incorrectly calculating the number of products while evaluating the
requiredProductgroup characteristics for the GetPrices web service.
AF-7363
When com.tibco.af.oms.enableOfferValidation=true in ConfigValues_OMS.xml and
com.tibco.fom.aopd.deployMode=AOPD_colocated in profiles.properties, canceled
orders were pending in the amendment queue.