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

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

================================================================================
Closed Issues in 2.1.0_HF-001 (This Release)

AF-3978
If two instances of a product had the same linkID of a particular order, then any
value assigned to the UDF field "Version" in Fulfillment Order Management got
grouped and the AffinityCondition="true()" was automatically configured. The issue
was fixed.

AF-3975
The 'originator' property was not available in the AF_Orchestrator.projlib and
AF_Orchestrator_ForDesigner.projlib project libraries. The issue was fixed and the
'originator' property has been added to all the required events that were
exposed through the AF_Orchestrator.projlib so that it can readily be referred to,
in the studio projects for BE process components. The 'originator' property has
also been added to a new 'JMS Application Properties' palette,
aff/orchestrator/sharedResources/applicationProperties/orchestratorInterfaceProperties.sharedjmsapp,
that was exposed through AF_Orchestrator_ForDesigner.projlib, which can develop
the process components in BW using the TIBCO Designer projects.

AF-3889
The Error Code TIBCO-AFF-OMS-100003 was not displayed if the order with same
order reference was submitted twice. The issue was fixed and the Error Code
TIBCO-AFF-OMS-100003 was displayed when the property
"com.tibco.af.oms.webservice.idempotency" was set to FALSE. The Error Code
TIBCO-AFF-OMS-100004 was not displayed if the amendment was submitted for a
nonexistent order reference. The issue was fixed.

AF-3888
The execute request for the REDO-2 plan item in the second amendment, which is
dependent on the already completed REDO-1 plan item from the first amendment, was
not sent out by Orchestrator. The issue was fixed.

AF-3886
If an execution plan was amended multiple times, the execution plan did not
retain the correct plan item IDs in the evaluationPriority for the shared UDFs.
The issue was fixed and the evaluationPriority now stores the appropriate plan
item ID even after multiple amendment of the execution plan.

While managing the dependencies related to the REDO plan items in an amendment,
a simpler behavior has been implemented from 2.1.0 HF1 onwards.
The behavior is as follows:

Whenever a REDO plan item is created against an existing plan item during an
amendment,
a. The REDO plan item will have a dependency, on either of the scenarios:
   i. On the existing plan item in case of EPMR action as RESTART,
      only if the original plan item was in the EXECUTION state before the
      amendment. If the original plan item was COMPLETE before the amendment,
      the REDO plan item will not have the dependency on the original plan item
      because that would be an implicitly satisfied dependency.
  ii. On the COMP plan item created against the existing plan item in case of
      EPMR action as COMPENSATE_RESTART. This dependency always exists in case
      of COMPENSATE_RESTART action, regardless of the status of the existing
      plan item before the amendment, that is EXECUTION or COMPLETE.    
b. The dependencies in all the parent plan items on the existing plan item would
   be deleted regardless of the status of the existing plan item.
c. The corresponding dependencies in all the parent plan items would be added on
   the newly created REDO plan item to keep the plan structure as earlier.
d. The plan item ID of the original plan item in the evaluation priority is
   replaced with the ID of the newly created REDO plan item.

AF-3883
If an order was amended multiple times, an exception was raised and the order was
removed. The exception occurred because the limit of the column size of
"PLANITEM_UDF_DATA.EVALUATIONPRIORITY" was set to 125, and each amendment
added a "REDO-" prefix, thus increasing the column size. The issue was fixed and
the limit of the column size was increased.

AF-3873
The shared UDFs or shared attributes did not work when the planItem generated was
of type Affinity. The issue was fixed.

AF-3836
The random order of line numbers were causing the evaluationPriority to receive
incorrect information. The evaluationPriority for the UDF of the product was  
receiving the product name instead of receiving the plan item ID. The issue was
fixed and the evaluationPriority can now receive the plan item ID.

AF-3809
Some of the milestone dependencies were disappearing, during the order amendment
plan for a PlanItem, when the RESTART action was performed. The issue was fixed,
and the PlanItem now contains all the milestone dependencies that were present
in the order amendment plan.

AF-3808
The evaluationPriority element, for the 'Shared' type of UDFs, in the plan items
contained the IDs of the plan items that were not present in the order amendment
plan. The issue has been fixed and the evaluationPriority string now contains
the IDs of the appropriate plan items that were present in the order amendment
plan.

If the evaluationPriority in the original plan contained the IDs of plan items
which had REDO plan items in the amendment plan, then the evaluationPriority
contained the IDs of the corresponding REDO plan items instead of the original
plan items. This is logical because the original plan items were activated and
canceled after the amendment plan was activated. However, the REDO plan items
were executed to perform the tasks that were supposed to be done by the original
plan item before the amendment.

AF-3805
The syntax for the plan item with Affinity UDF was incorrect when the FOM was
upgraded to 2.1.0 from 2.0.1. The issue has been fixed and the syntax for the
plan item with the Affinity UDF remains the same after the upgrade.

AF-3781
The OMSServer was not able to connect to the secondary EMS server, when the
primary EMS Server went down. The issue has been fixed and the OMSServer was
able to connect to the secondary EMS server in the fault tolerance EMS
setup without any warnings or errors. During the switch in the EMS servers if
any warnings come up in the EMS logs, then the warnings can be ignored, if
no errors are present in the OMSServer logs, and no impact on business
functionality.

AF-3780
The format of the plan item ID changed, from including the planfragment name in
FOM 2.0.1, to including an alphanumeric string in FOM 2.1.0. The issue has been
fixed. In the OMS UI, the planItem has been templatized for the Grid, Gantt, and
Dependency views. The Grid, Gantt, and Dependency view templates can be
configured through Configurator.

1. Click User Interface -> PlanItem Display Template.
2. Configure the value propname="com.tibco.af.omsui.planItemExpression.gridView"
   for Grid View.
3. Configure the value propname="com.tibco.af.omsui.planItemExpression.ganttView"
   for Gantt View.
4. Configure the value propname="com.tibco.af.omsui.planItemExpression.dependencyView"
   for Dependency View.

The following template variables can be used: PlanItemID, PlanFragmentID,
ProductID, Action, and Description.

The template variables are case-sensitive and have to be specified within
braces.
Example: {PlanItemID}

Different template variables can be combined with a delimiter. A blank space
cannot be used as a delimiter. Additionally, delimiters cannot be preceded or
succeeded by a blank space.
Example: {PlanFragmentID}|{PlanItemID}. Here "|" is the delimiter.

AF-3772
The value of the shared attributes was lost during an amendment request for
products that used the RESTART EPMR characteristics. The issue was fixed and
the values of shared attributes were retained during an amendment request
that used the RESTART characteristics.

AF-3771
The intermediate milestone in the plan items were lost during the order
amendment request for products that used the RESTART EPMR characteristics.
The issue was fixed.

AF-3770
Fulfillment Order Management gets blocked if the first plan item of an
execution plan was NON_EXECUTING. The issue was fixed.

AF-3765
PRF products were missing due to the incorrect creation of the plan fragment
model. The issue was fixed.

AF-3258
If multiple LinkID and PDO relationships were established between the same
products, the EvaluationPriority could not establish a connection with the
right LinkID. The issue was fixed and the the EvaluationPriority now
establishes a connection with the right LinkID.

AF-3202
Reserved characteristics like LinkID and LinkedParentID were not hierarchically
propagated down to the children. The issue was fixed and the reserved
characteristics, such as LinkID and LinkedParentID, are hierarchically  
propagated down to the children.