TIBCO FOM 2.1.2 Hotfix05 is available

Products	Versions
TIBCO Fulfillment Order Management	-
Not Applicable	-

Description

Description:

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-05/ to download the hotfix.

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

================================================================================

Closed Issues in 2.1.2_HF-005 (This release)

AF-6467

The error message "org.springframework.dao.EmptyResultDataAccessException:

Incorrect result size: expected 1, actual 0" was displayed when new orders

were submitted in the Orchestrator. The issue has been fixed.

AF-6439

After several amendments in intermediate milestones, dependencies were displayed

for cancelelled plan items. The issue has been fixed.

AF-6438

Circular dependencies were displayed after the third amendment between START and

END milestones in REDO-2 planitem. The issue has been fixed.

AF-6431

There was a leak on the tibco.aff.orchestrator.planItem.milestone.release.request

queue, each time an order was submitted and cancelled. The issue has been fixed

by changing the intended event in release state machine to a value different from

what is being sent, to send the release request again after the amendment for

already released milestones, when the new flag

"com.tibco.fom.orch.enableMilestoneReleaseDuringActivation" is unset.

If "com.tibco.fom.orch.enableMilestoneReleaseDuringActivation" is set, the

milestone will be released during amendment provided the related dependencies

don't change during amendment.

If "com.tibco.fom.orch.enableMilestoneReleaseDuringActivation" is not set, the

milestone will not be released during amendment in the activated plan item if

it was already released before amendment.

AF-6393

Orders were executing plan items without the completion of the milestone

dependencies.The issue has been fixed.

AF-6382

Orders created using FOM 2.1.2 HF-001, could not be amended using

FOM 2.1.2 HF-004. The issue has been fixed. This issue occurred due to the

newly introduced Parent_ID UDF, which was not present in the original plan.

A flag "com.tibco.af.aopd.flags.enableparentidudfcheck" has been added in

ConfigValues_AOPD, which can be disabled to ignore this udf during amendments.

The default value of the flag "com.tibco.af.aopd.flags.enableparentidudfcheck"

is TRUE. The user needs to set the value to FALSE for this use case.

AF-6357

PlanItemExecuteResponse of a non-existing order was blocking the processing

of the rest of the planitemexecuteresponse. The issue has been fixed.

AF-6311

Orders were still on execution status even after all the planitems were

completed. The issue has been fixed.

AF-6310

Amendment was not working when the SUSPEND reply was fast. The issue has been

fixed.

AF-6305

Sorting of Plan Item Milestones exception was seen during cancellation of

amendment plan. The issue has been fixed.

AF-6290

Order remained in SUSPENDED status and an exception was displayed during

cancellation of amendment plan. The issue has been fixed.

AF-6270

Orchestrator resource failure was observed, when sending multiple withdraw

for the same order reference, because of NO_RECORD_LIST batch error. The

issue has been fixed.

AF-6268

The FOM 2.1.2 HF-004 ReadMe mentioned that enabling connection pooling logs

as mandatory. The post installation STEP 14 has been updated and it now

mentions that STEP 14 is optional.

AF-6256

The OMS user interface was not showing the time offset at the orderline level.

The issue has been fixed.

AF-6253

When executing a second amendment, a COMP-2 planitem was created even though the

COMP-1 planitem had already been completed after the first amendment. The issue

has been fixed.

AF-6242

When sending non existing planitem in setPlanItem TDS the error

AFF-TDS-9999 Internal Error is displayed instead of AFF-TDS-PLAN-0101

Plan Item not found for planID <planID> and planItemID <planItemID>.

The issue has been fixed.

AF-6136

A high CPU usage was observed, and

"java.lang.OutOfMemoryError: GC overhead limit exceeded error" was displayed

when viewing plan in GUI, after the third amendment. The issue has been fixed.

AF-6099

The error "UNEXPECTED_ERROR" was seen when orders were amended and cancelled

simultaneously. The issue has been fixed.

AF-6091

The OMS_purge_activitylogs script could not be executed after executing

OMS_purge_orders script for the same date/time range. The issue has

been fixed.

Issue/Introduction

TIBCO FOM 2.1.2 Hotfix05 is available

Welcome to "KB Articles"