TIBCO ActiveFulfillment 1.2.0 Hotfix 09 is now available.
Article ID: KB0104113
Updated On:
| Products | Versions |
|---|---|
| TIBCO ActiveFulfillment | - |
| Not Applicable | - |
Description
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-09/ 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 09 are:
AF-2512
Order Summary query was run every 5 minutes.
AF-2501
OMS processed orders slowly and showed OutOfMemory exceptions.
AF-2500
Executing SyncSubmitOrder over JMS returned a wrong error message.
AF-2473
MilestoneDependsOn did not take the LinkID into consideration.
AF-2448
Product decomposition did not work correctly for the ProductDependsOn or ProductRequiredFor relationships.
This fix handles product decomposition for the ProductDependsOn and ProductRequiredFor relationships. You can define XPath for RelationshipValue attributes for the DECOMPOSITION_REQUIRED_FOR or DECOMPOSITION_DEPENDS_ON characteristics against plan data along with an existing order data.
If an XPath is required to be defined against plan data, the format must be <Actual XPath> containing the $var/PlanItem string.
If an XPath is required to be defined against order data, the format must be <Actual XPath> containing the $var/Order string.
Note: XPath evaluation must be boolean.
Sample:
exists($var/PlanItem[LinkID=#CURRENT_LINKID# and productID='B']/udfs[name='MSISDN' and value='123'])
exists($var/Order/orderlines[LinkID=#CURRENT_LINKID# and productID='B']/OrderlinesUDF[name='MSISDN' and value='123'])
While processing, #CURRENT_LINKID# is replaced with the actual link ID of a plan item.
AF-2413
Insufficient LINKID UDF information to define order line parenting for multi-level hierarchy of multi-instantiable optional child products.
The fix has been implemented to reuse the common products having Autoprovision=false using LinkParentID and LinkedParentID UDFs in the orderline.
The LinkParentID-LinkedParentID and LinkID UDFs are used to define PCO-tree, although the LinkParentID-LinkedParentID UDF has the higher priority.
a)Link child to parent based on LinkParentID-LinkedParentID if present. Else,
b)Link child to parent based on LinkID if present. Else,
c)Link child to parent randomly.
For example, consider the following product model:
T-COM Wireline --> (PCO) Additional Voice Service(autoproivision=false)
T-COM Wireline --> (PCO) Tarrif1(autoproivision=false)
Additional Voice Service --> (PCO) Tarrif1(autoproivision=false)
Therefore, the order can be:
---------------------------------------------------------------------------------
Orderline |Product |LinkParentID |LinkedParentID
Number | | |
---------------------------------------------------------------------------------
1 |T-COM Wireline |T-COM Wireline |
---------------------------------------------------------------------------------
2 |Additional Voice |Additional Voice |T-Com Wireline
|Service |Service |
---------------------------------------------------------------------------------
3 |Tarrif1 |Tarrif1 |Additional Voice
| | |Service
---------------------------------------------------------------------------------
4 |Tarrif1 |Tarrif1_1 |T-Com Wireline
---------------------------------------------------------------------------------
The LinkParentID-LinkedParentID UDFs are added for orderline number 2 in the following format to add dependency between OrderLine 2 and OrderLine 3:
<ord1:udf>
<ord1:name>LinkParentID</ord1:name>
<ord1:value>Tarrif1</ord1:value>
</ord1:udf>
<ord1:udf>
<ord1:name>LinkedParentID</ord1:name>
<ord1:value>Additional Voice Service</ord1:value>
</ord1:udf>
NOTE: This change is backward-compatible. To use the LinkID functionality, do not add the LinkParentID-LinkedParentID UDFs in the orderline.
AF-2407
Disabling the log writing to the AUDIT_TRAIL database table without disabling the OMS notification was not possible.
Refer to step 9(C) under the 'Installation' section to add the 'Enable Audit Trail Entries' property. The default value is 'true', indicating OMS enables the entries in the audit trail log. If the value is set to 'false', the audit trail log gets disabled.
AF-2356
Data could not be purged from OMS and Orchestrator based on order status, start date and end date.
A Purge utility has been introduced to fix this.
NOTE: To use this utility, refer to the
$AF_HOME/db/oracle/purge/purgeservice/ReadMe.txt file.
AF-1979
Conditional affinity: PlanFragment was set incorrectly when different planItems having different actions were grouped together.
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-09/ 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 09 are:
AF-2512
Order Summary query was run every 5 minutes.
AF-2501
OMS processed orders slowly and showed OutOfMemory exceptions.
AF-2500
Executing SyncSubmitOrder over JMS returned a wrong error message.
AF-2473
MilestoneDependsOn did not take the LinkID into consideration.
AF-2448
Product decomposition did not work correctly for the ProductDependsOn or ProductRequiredFor relationships.
This fix handles product decomposition for the ProductDependsOn and ProductRequiredFor relationships. You can define XPath for RelationshipValue attributes for the DECOMPOSITION_REQUIRED_FOR or DECOMPOSITION_DEPENDS_ON characteristics against plan data along with an existing order data.
If an XPath is required to be defined against plan data, the format must be <Actual XPath> containing the $var/PlanItem string.
If an XPath is required to be defined against order data, the format must be <Actual XPath> containing the $var/Order string.
Note: XPath evaluation must be boolean.
Sample:
exists($var/PlanItem[LinkID=#CURRENT_LINKID# and productID='B']/udfs[name='MSISDN' and value='123'])
exists($var/Order/orderlines[LinkID=#CURRENT_LINKID# and productID='B']/OrderlinesUDF[name='MSISDN' and value='123'])
While processing, #CURRENT_LINKID# is replaced with the actual link ID of a plan item.
AF-2413
Insufficient LINKID UDF information to define order line parenting for multi-level hierarchy of multi-instantiable optional child products.
The fix has been implemented to reuse the common products having Autoprovision=false using LinkParentID and LinkedParentID UDFs in the orderline.
The LinkParentID-LinkedParentID and LinkID UDFs are used to define PCO-tree, although the LinkParentID-LinkedParentID UDF has the higher priority.
a)Link child to parent based on LinkParentID-LinkedParentID if present. Else,
b)Link child to parent based on LinkID if present. Else,
c)Link child to parent randomly.
For example, consider the following product model:
T-COM Wireline --> (PCO) Additional Voice Service(autoproivision=false)
T-COM Wireline --> (PCO) Tarrif1(autoproivision=false)
Additional Voice Service --> (PCO) Tarrif1(autoproivision=false)
Therefore, the order can be:
---------------------------------------------------------------------------------
Orderline |Product |LinkParentID |LinkedParentID
Number | | |
---------------------------------------------------------------------------------
1 |T-COM Wireline |T-COM Wireline |
---------------------------------------------------------------------------------
2 |Additional Voice |Additional Voice |T-Com Wireline
|Service |Service |
---------------------------------------------------------------------------------
3 |Tarrif1 |Tarrif1 |Additional Voice
| | |Service
---------------------------------------------------------------------------------
4 |Tarrif1 |Tarrif1_1 |T-Com Wireline
---------------------------------------------------------------------------------
The LinkParentID-LinkedParentID UDFs are added for orderline number 2 in the following format to add dependency between OrderLine 2 and OrderLine 3:
<ord1:udf>
<ord1:name>LinkParentID</ord1:name>
<ord1:value>Tarrif1</ord1:value>
</ord1:udf>
<ord1:udf>
<ord1:name>LinkedParentID</ord1:name>
<ord1:value>Additional Voice Service</ord1:value>
</ord1:udf>
NOTE: This change is backward-compatible. To use the LinkID functionality, do not add the LinkParentID-LinkedParentID UDFs in the orderline.
AF-2407
Disabling the log writing to the AUDIT_TRAIL database table without disabling the OMS notification was not possible.
Refer to step 9(C) under the 'Installation' section to add the 'Enable Audit Trail Entries' property. The default value is 'true', indicating OMS enables the entries in the audit trail log. If the value is set to 'false', the audit trail log gets disabled.
AF-2356
Data could not be purged from OMS and Orchestrator based on order status, start date and end date.
A Purge utility has been introduced to fix this.
NOTE: To use this utility, refer to the
$AF_HOME/db/oracle/purge/purgeservice/ReadMe.txt file.
AF-1979
Conditional affinity: PlanFragment was set incorrectly when different planItems having different actions were grouped together.
Issue/Introduction
TIBCO ActiveFulfillment 1.2.0 Hotfix 09 is now available.
Environment
Product: TIBCO ActiveFulfillment
Version: 1.2.0
OS: All
--------------------
Feedback
Yes
No
Powered by
