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


AF-1140
With certain conditions of dependencies in the Product Model, the Gantt chart was not shown.


AF-1120
Order Amendment was failing when SLAs were set in the orderlines.


AF-1116
A database clean up tool is now available for the OMS component.

Ignore errors, if any, related to constraints while running the purge scripts. These errors are related to inconsistent data in the Audit_Trail table.

With purge scripts, orders with WITHDRAWN status can not be purged.

The Readme.txt file and purge scripts are located in the $AF_HOME/db/oracle/purge directory.


AF-1100
The OMS component threw an error when submitting an order with a non-numeric order line number. For example, string as the order line number (1-LI01).


AF-1096
A new web service interface is now available for the OMS component. This new service allows you to withdraw submitted orders. As an input, this operation accepts the OrderID or OrderRef to withdraw an order and returns the message while sending the order for withdrawal in the Orchestrator component. After receiving an order removal notification from Orchestrator, it removes the requested order from the OMS component. You cannot withdraw an order when it is in the COMPLETE, or CANCELLED states. The only way you can trace withdrawn orders from the OMS component is by OrderRef on the Activity Log page. You can submit an order with the same OrderRef, which is already withdrawn.

Currently, since the system does not keep record of withdrawn orders, the Orders Summary section under the Dashboard tab does not show any statistics for withdrawn orders.

The request and response sample files for withdraw order Web service are located in the $AF_HOME/samples/WebService directory.


AF-1067
UDF value set by a TDS request was not working for shared attributes.


AF-1065
Row lock wait issue was observed during order processing.


AF-1055
Offline product files were not getting picked up in the correct sequence when created with a particular file name.


AF-1050
Incorrect plan was generated for Affinity groups. For example, a BUNDLE is comprised of Service1, Service2, and Service3 without sequencing. Each service included A,B, and C, which were auto-provisioned and sequenced, as A:1,B:2,C:3. C has the Affinity group plan fragments defined. On submitting an order with OL1=BUNDLE, OL2=Service1, OL3=Service2,and OL4=Service3, the affinity group C would only depend on B. The group should depend on all.


AF-1049
Web services exposed by AF_Services (AFS) component were timed out if more than one instance of AFS was deployed.


AF-1045
The property "java.property.tangosol.coherence.distributed.threads" was not available for configuration in any of the TIBCO BusinessEvents engines in TIBCO Administrator. Also, the property "java.property.com.sun.management.jmxremote.port" was conflicting for two service instances running on the same machine.

This issue has been fixed, and the property "java.property.com.sun.management.jmxremote.port" is no longer a part of the deployed engine’s TRA file. However, you may notice this property in the configurator application, which you can ignore.


AF-1041
OutOfMemory error was reported when viewing plan of an order on a specific environment.

TIBCO ActiveFulfillment 1.2.0 Hotfix 01 is now available.

Product: TIBCO ActiveFulfillment Version: 1.2.0 OS: All --------------------