TIBCO(R) Fulfillment Order Management 4.0.1 - HF-001 is now available

TIBCO(R) Fulfillment Order Management 4.0.1 - HF-001 is now available

book

Article ID: KB0102103

calendar_today

Updated On:

Products Versions
TIBCO Fulfillment Order Management 4.0.1

Description

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/ActiveFulfillment/4.0.1/Hotfix-1"
TIB_af_4.0.1_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.1_HF-001 (This Release)

AF-8143 
OPE java customization makes lot of database calls.

AF-8146 
Concurrent modification issues in GetPrices API on load testing

AF-8148    
OPE API GetOffer doesn't Decompose children when AutoProvision=false

AF-8159    
An SQL query sent on OMS_ROUTER_TBL took 60 seconds to be executed.

AF-8160    
No security action when sending order not working with AF-7514 fix

AF-8161
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.

AF-8163    
OPE was incorrectly calculating the number of products while evaluating the
requiredProductgroup characteristics for the GetPrices web service.

AF-8165    
Messages including replies for all TDS operations are persistent. These messages 
can be made non-persistent using the provided configurations.

AF-8166    
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-8167    
When sending an order, the fault soap error 
"org.apache.cxf.binding.soap.SoapFault: No security action was defined!" 
occurred intermittently.

AF-8168    
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-8169    
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-8170    
A product was missing in the execution plan when ProductComprisedOf=false with 
an empty LinkID.

AF-8172    
Plan Item Milestone Release Request event would send unexpectedly

AF-8174    
The OPE ValidateOffer web service response would be different with the same 
ValidateOffer web service request.

AF-8177    
A StackOverflow exception would occur after order amendment if two planItems had 
intermediate milestones dependencies on each other.

AF-8179    
The price model fetch from the database is now done in chunks like the product 
model fetch process.

AF-8185    
When there was an ORDER_ALREADY_BEING_CANCELLED error, the jdbc pool would 
increase and not return connections to the pool.

AF-8202    
Readme of 400 hotfix1 had some missing information.

AF-8203    
User can choose appropriate action for the plan item in ERROR state from a web 
service when using "internal error handler" as a plan item error handler type.
A new webservice HandlePlanItemInError has been introduced under orderService 
wsdl

AF-8204
Error encountered when configuring OMSUI to use SSL

AF-8205
When using a dash (-) in a Segment Name or type under Getprice request, the segment 
must be mapped into 2 different elements, Name and Type.

AF-8207    
After canceling an order, the plan remained in EXECUTION state due to an extra 
dependency.

AF-8208    
RequiredByDate was not in the plan in case of affinity.

AF-8209    
AFter publishing a catalog from TIBCO Fulfillment Catalog to TIBCO Fulfillment 
Order Management, the OPE GetOffer response had misisng products.

AF-8213    
Lock exception returned when processing SetPlan Request

AF-8214    
Unexpected error is seen on OMSUI and TenantNotAvailableException is seen 
under logs while changing default tenant from TIBCO to any other value.
        
AF-8216    
OMS server doesn't start when EMS isAuthorizationEnabled set to true

AF-8249
Choosing error handler resolution via OMS UI is not working after installation 
of "engineering-build-for-Safaricom-on-400hf1-23May2018.zip"

AF-8266
"ERROR StatusLogger No log4j2 configuration file found" is seen on omsServer 
startup

Issue/Introduction

TIBCO(R) Fulfillment Order Management 4.0.1 - HF-001 is now available