TIBCO® Fulfillment Order Management Release …2013/03/01 · TIBCO Fulfillment Order Management...

Two-Second

TIBCO® Fulfillment Order Management

Release NotesSoftware Release 2.0.1March 2013

Advantage®

Important Information

SOME TIBCO SOFTWARE EMBEDS OR BUNDLES OTHER TIBCO SOFTWARE. USE OF SUCH EMBEDDED OR BUNDLED TIBCO SOFTWARE IS SOLELY TO ENABLE THE FUNCTIONALITY (OR PROVIDE LIMITED ADD-ON FUNCTIONALITY) OF THE LICENSED TIBCO SOFTWARE. THE EMBEDDED OR BUNDLED SOFTWARE IS NOT LICENSED TO BE USED OR ACCESSED BY ANY OTHER TIBCO SOFTWARE OR FOR ANY OTHER PURPOSE.USE OF TIBCO SOFTWARE AND THIS DOCUMENT IS SUBJECT TO THE TERMS AND CONDITIONS OF A LICENSE AGREEMENT FOUND IN EITHER A SEPARATELY EXECUTED SOFTWARE LICENSE AGREEMENT, OR, IF THERE IS NO SUCH SEPARATE AGREEMENT, THE CLICKWRAP END USER LICENSE AGREEMENT WHICH IS DISPLAYED DURING DOWNLOAD OR INSTALLATION OF THE SOFTWARE (AND WHICH IS DUPLICATED IN LICENSE.PDF) OR IF THERE IS NO SUCH SOFTWARE LICENSE AGREEMENT OR CLICKWRAP END USER LICENSE AGREEMENT, THE LICENSE(S) LOCATED IN THE “LICENSE” FILE(S) OF THE SOFTWARE. USE OF THIS DOCUMENT IS SUBJECT TO THOSE TERMS AND CONDITIONS, AND YOUR USE HEREOF SHALL CONSTITUTE ACCEPTANCE OF AND AN AGREEMENT TO BE BOUND BY THE SAME.This document contains confidential information that is subject to U.S. and international copyright laws and treaties. No part of this document may be reproduced in any form without the written authorization of TIBCO Software Inc.TIBCO, TIBCO Adapter, Predictive Business, Information Bus, Two-Second Advantage, TIBCO ActiveMatrix BusinessWorks, TIBCO Runtime Agent, TIBCO Administrator, TIBCO Enterprise Message Service, and TIBCO BusinessEvents, are either registered trademarks or trademarks of TIBCO Software Inc. in the United States and/or other countries.EJB, Java EE, J2EE, and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and other countries.All other product and company names and marks mentioned in this document are the property of their respective owners and are mentioned for identification purposes only.THIS SOFTWARE MAY BE AVAILABLE ON MULTIPLE OPERATING SYSTEMS. HOWEVER, NOT ALL OPERATING SYSTEM PLATFORMS FOR A SPECIFIC SOFTWARE VERSION ARE RELEASED AT THE SAME TIME. SEE THE README.TXT FILE FOR THE AVAILABILITY OF THIS SOFTWARE VERSION ON A SPECIFIC OPERATING SYSTEM PLATFORM.THIS DOCUMENT IS PROVIDED “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT.THIS DOCUMENT COULD INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS. CHANGES ARE PERIODICALLY ADDED TO THE INFORMATION HEREIN; THESE CHANGES WILL BE INCORPORATED IN NEW EDITIONS OF THIS DOCUMENT. TIBCO SOFTWARE INC. MAY MAKE IMPROVEMENTS AND/OR CHANGES IN THE PRODUCT(S) AND/OR THE PROGRAM(S) DESCRIBED IN THIS DOCUMENT AT ANY TIME.THE CONTENTS OF THIS DOCUMENT MAY BE MODIFIED AND/OR QUALIFIED, DIRECTLY OR INDIRECTLY, BY OTHER DOCUMENTATION WHICH ACCOMPANIES THIS SOFTWARE, INCLUDING BUT NOT LIMITED TO ANY RELEASE NOTES AND "READ ME" FILES.Copyright © 2010-2013 TIBCO Software Inc. ALL RIGHTS RESERVED.TIBCO Software Inc. Confidential Information

| iii

Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .v

Typographical Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi

Connecting with TIBCO Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .viiiHow to Join TIBCOmmunity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .viiiHow to Access All TIBCO Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .viiiHow to Contact TIBCO Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .viii

Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1

New Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Release 2.0.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Release 2.0.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Release 1.2.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Release 1.1.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Release 1.0.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Changes in Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Release 2.0.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Release 2.0.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Release 1.2.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Release 1.1.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Release 1.0.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Deprecated and Removed Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Release 2.0.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Release 2.0.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Release 1.2.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Release 1.1.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Migration and Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Release 2.0.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Release 1.2.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Release 1.1.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Release 1.0.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Closed Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Known Issues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

TIBCO Fulfillment Order Management Release Notes

iv | Contents


| v

Preface

TIBCO Fulfillment Order Management is an order management and fulfillment system, which allows development of fulfillment plans based on the meta-data specified in catalogs.

Topics

• Typographical Conventions, page vi

• Connecting with TIBCO Resources, page viii


vi | Typographical Conventions

Typographical Conventions

The following typographical conventions are used in this manual.

Table 1 General Typographical Conventions

Convention Use

TIBCO_HOME

ENV_HOME

AF_HOME

Many TIBCO products are installed within the same home directory. This directory is referenced in documentation as TIBCO_HOME. The value of TIBCO_HOME depends on the operating system. For example, on UNIX systems the default value is $HOME/tibco.

TIBCO Fulfillment Order Management installs into a directory inside TIBCO_HOME. This directory is referenced in documentation as AF_HOME. The value of AF_HOME depends on the operating system. For example, on UNIX systems the default value is $TIBCO_HOME/af/2.0.

code font Code font identifies commands, code examples, filenames, pathnames, and output displayed in a command window. For example:

Use MyCommand to start the foo process.

bold code

font Bold code font is used in the following ways:

• In procedures, to indicate what a user types. For example: Type admin.

• In large code samples, to indicate the parts of the sample that are of particular interest.

• In command syntax, to indicate the default parameter for a command. For example, if no parameter is specified, MyCommand is enabled: MyCommand [enable | disable]

italic font Italic font is used in the following ways:

• To indicate a document title. For example: See TIBCO ActiveMatrix BusinessWorks Concepts.

• To introduce new terms For example: A portal page may contain several portlets. Portlets are mini-applications that run in a portal.

• To indicate a variable in a command or code syntax that you must replace. For example: MyCommand PathName


Preface | vii

Key combinations

Key name separated by a plus sign indicate keys pressed simultaneously. For example: Ctrl+C.

Key names separated by a comma and space indicate keys pressed one after the other. For example: Esc, Ctrl+Q.

The note icon indicates information that is of special interest or importance, for example, an additional action required only in certain circumstances.

The tip icon indicates an idea that could be useful, for example, a way to apply the information provided in the current section to achieve a specific result.

The warning icon indicates the potential for a damaging situation, for example, data loss or corruption if certain steps are taken or not taken.

Table 1 General Typographical Conventions (Cont’d)

Convention Use


viii | Connecting with TIBCO Resources

Connecting with TIBCO Resources

How to Join TIBCOmmunityTIBCOmmunity is an online destination for TIBCO customers, partners, and resident experts, a place to share and access the collective experience of the TIBCO community. TIBCOmmunity offers forums, blogs, and access to a variety of resources. To register, go to http://www.tibcommunity.com.

How to Access All TIBCO DocumentationYou can access TIBCO documentation here:

http://docs.tibco.com

How to Contact TIBCO SupportFor comments or problems with this manual or the software it addresses, contact TIBCO Support as follows.

• For an overview of TIBCO Support, and information about getting started with TIBCO Support, visit this site:

http://www.tibco.com/services/support

• If you already have a valid maintenance or support contract, visit this site:

https://support.tibco.com

Entry to this site requires a user name and password. If you do not have a user name, you can request one.


http://www.tibco.com/services/support


http://docs.tibco.com

http://www.tibcommunity.com

| 1

Release Notes

Check the TIBCO Product Support web site at https://support.tibco.com for product information that was not available at release time. Entry to this site requires a username and password. If you do not have a username, you can request one. You must have a valid maintenance or support contract to use this site.

Topics

• New Features, page 2

• Changes in Functionality, page 6

• Deprecated and Removed Features, page 15

• Migration and Compatibility, page 17

• Closed Issues, page 19

• Known Issues, page 30



2 | Release Notes

New Features

This section lists features added in this major release of this product.

Release 2.0.1There are no new features in this release.

Release 2.0.0The following are new features in this release:

• Jeopardy Management System This new feature allows you to manage the risks associated with the plan tasks falling behind schedule, and to prevent them from jeopardizing the timely fulfillment of an order. The GANTT chart is also enhanced for the Jeopardy indications.

• Jeopardy Dashboard This new feature allows you to view all the orders in jeopardy and the jeopardy alerts. You can also view the recorded alerts from the Jeopardy Manager.

• Rule Configuration This new feature allows you to configure jeopardy rules to send notification or invoke web services to perform consequential actions.

• Order Prioritization This new feature allows you to set priority while submitting orders. This information is used by the JMS broker to deliver the high priority orders to downstream components on priority.

• Bulk Order Actions This new feature allows you to apply actions to the group of orders simultaneously. The following operations can be performed on the group of orders:

— CANCEL

— SUSPEND

— RESUME

— WITHDRAW

• Integration Fulfillment Order Management (FOM), Fulfillment Catalog (FC), and Fulfillment Provisioning (FP) are now part of the Fulfillment Orchestration Suite (FOS) and can be seamlessly integrated together to work collaboratively.

• Service Orders View This new feature allows you to view FP Service orders in the plan tab of the OMS UI.


New Features | 3

• Data Modeling Changes

— ProductDependsOn and ProductRequiredFor Relationships: The ProductDependsOn (PDO) relationship is created in the PRODUCT repository. This relationship creates a flexible product decomposition and allows you model product without sequencing. The ProductRequiredFor (PRF) is a product prerequisite relationship to add the missing target plan item.

— Conditional Affinity: Conditional Affinity contains additional configuration fields and rules that combine the capabilities of InLink and CrossLink affinities in a single affinity type. It provides flexibility and allows plan items to be grouped together under different conditions for the two different affinity types.

— CustomAction: The Custom Action allows to define the set of actions to provide a way to define any number of unique fulfillment actions.

• Withdraw Orders from the OMS UI This new feature allows you to withdraw orders from the OMS UI.

• Custom Plan Description This new feature allows you to pass a static custom order description, while submitting an order, that will set the corresponding plan description which appears in the OMS UI Plan Browser.

• Search UDF in the OMS UI This new feature allows you to search the User Defined Fields (UDFs) from the plan.


• Intermediate Milestone This new feature is an important scheduling point within the process components of an execution plan. Intermediate dependencies can be defined FROM and TO Milestones. Due to this feature, more complex types of dependencies can be supported between executing process components.

• Orders in Execution Gadget This new Order Management System Dashboard component allows you to view orders in the execution state.

• Web Services Validation of SOAP over JMS Web services validation for JMS can be enabled with configuration changes.

• Configurable Listener Queues This new feature allows you to configure Listener Queues for Notifications through Fulfillment Order Management Configurator.

• Synchronous Order Submission This new feature allows you to synchronously submit the order and receive response on completion of order fulfillment. This feature is useful when order fulfillment is a short-running process.


4 | Release Notes


• ActiveFulfillment Configurator Graphical User Interface (GUI) This new feature allows you to configure various settings for TIBCO ActiveFulfillment using a GUI mode.

• Order Management Server This new feature allows you to manage orders using a web-based graphical user interface.

• ActiveFulfillment Orchestrator This new high-volume orchestration engine allows you to optimize order fulfillment processing.

• Transient Data Store (TDS) This new component allows you to optimize data usage and sharing while fulfilling orders.

• Dependent and Sibling Product This new feature allows you to group products on requests thereby allowing for sibling products and their children products to be sent to a dependent product. The ability is built in the Product Model to indicate that a product is dependent on its peer or peer’s hierarchy.

• Attribute-based Decomposition This new feature allows you to filter execution plan depending on orderline attributes of the products ordered.

• Affinity This new feature allows different plan fragment types to be grouped together on the same order.

• Order Amendments Order Amendment is now handled via new Order Management Server and AF Orchestration engine.

• Offline Catalog This new feature allows TIBCO ActiveFulfillment to fulfill orders and reduces the dependency on TIBCO ActiveCatalog to be online.

• Centralized Logging This new feature provides logging and reporting capability for analyzing data and generating meaningful reports.

• Inventory Integration This new feature in ActiveFulfillment Service allows you to retrieve inventory details.

• Shared Attributes This new feature is used when two Products (parent to child and sibling) share the same attribute and its corresponding value, and an update in the value of one needs to be reflected in the other.


• Order Validation and Order Fulfillment Engine This new feature is provided to read complete Offer, Product, Service, and Rule definitions from the Product Catalog system, such as TIBCO ActiveCatalog, as well as relevant Customer


New Features | 5

and Inventory information, and automate the back-end processes for order management. These functionalities have been provided as web services that can be invoked over HTTP or JMS.

• Audit Utility This new feature is provided to get the total number of orders that are submitted for processing.

• ActiveFulfillment Configurator This new feature is provided to configure various settings for ActiveFulfillment.


6 | Release Notes

Changes in Functionality

Release 2.0.1• File Name Change With the release of 2.0.1,

AF_Orchestrator_ForDesigner.projlib is the new name for the AF_Integration.projlib file. For details, refer to the Orchestrator Interfaces section in the TIBCO® Fulfillment Order Management Administration document.

• New Project Library With the release of 2.0.1, a new AF_Orchestrator.projlib library file has been added. For details, refer to the Orchestrator Interfaces section in the TIBCO® Fulfillment Order Management Administration document.

Release 2.0.0• Purge - In ActiveFulfillment 1.2.0, a stored procedure was used to purge the

orders from OMS while a global variable GLB_CleanupObjectsAtEndOfOrder was used to auto purge the orders from Orchestrator post their completion. The stored procedure has been replaced by a multithreaded java application as the way to purge orders from FOM components - OMS and Orchestrator. The purge process can be initiated by configuring the associated property file followed by invocation of a command line utility. The purge progress can be tracked using the same command line utility with different configuration in the property file. There is an option to archive the purged order in an identical database as is present for OMS.

• GANTT Chart - GANTT chart has been rewritten using a JavaScript-based library. Some of the key highlights of the Gantt chart are:

Show Execution Plan View in different timescale starting from weeks till milliseconds.

Different color coding to show the state of plan & plan items.

Show critical path for the execution plan.

Show plan, plan item & milestone level details.

• ActiveFulfillmentInterface (AFI) BW component rewrite - All the functionalities and the interfaces of ActiveFulfillmentInterface BW component have been rewritten in Java and merged as an integral part of omsServer component. The JMS interfaces are unchanged in terms of destinations. The notable changes are listed below:


Changes in Functionality | 7

All the necessary global variables from AFI BW deployment ear have been added as configuration properties under OMS AFI Configuration category under OMS configurations. These properties can be configured using Fulfillment Order Management Configurator. Refer the section Global Variables and Configurations in Fulfillment Order Management Administration guide.

The root level element SetSegmentsRequest in the Segment model schema is made namespace qualified. Please refer the segment model schema $AF_HOME/schemas/schema/afi/SharedResources/Schemas/Classes/Segment.xsd.

The capability to handle the ACTION model in online and offline catalog modes has been added.

The endpoint of offline catalog invocation SOAP/HTTP service is changed to http://<Host>:<Port>/omsServer/api/offlineCatalogueWS. Where: Host and Port are the machine and the port on which Apache Tomcat deployed with omsServer component is running. Refer to the Offline Catalog section the in Fulfillment Order Management Administration guide.

• Transient Data Store [TDS] BE component rewrite - The JMS event interfaces exposed by the Transient Data Store BE component that are required for process component integration have been rewritten in Java as JMS interfaces and merged as an integral part of omsServer component. These interfaces are unchanged in terms of JMS destinations. The interfaces are driven by the order and plan data in the OMS database. The notable changes are as follows:

All the necessary global variables from TDS BE deployment ear have been added as configuration properties under OMS TDS Configuration category under OMS configurations. These properties can be configured using FOM Configurator. Refer to the section Global Variables and Configurations in the Fulfillment Order Management Administration guide.

The following interfaces that were exposed in the earlier version through AF_TransientDataStore.projlib project library and the XML schema are continued and supported. There are minor necessary schema changes. Refer to the Data Access Interfaces section in the Fulfillment Order Management Administration guide.

Interface Schema changes, if any

Justification for schema changes

GetOrderRequest NO NA

GetOrderReply NO NA


8 | Release Notes

The following interfaces that were exposed in the earlier version through AF_TransientDataStore.projlib project library and the XML schema have been discontinued and not supported now:

GetPlanRequest NO NA

GetPlanReply NO NA

GetPlanItemsRequest NO NA

GetPlanItemsReply NO NA

SetPlanItemRequest Removed the elements - parentID, chilldID, dependentID, and siblingID from the planItemSetType element in the XSD.

The elements parentID, childID, dependentID, and siblingID are set in the generated execution plan and represent the relationships between the plan items. They are not allowed to be modified by the process components.

SetPlanItemReply NO NA

SetPlanRequest Removed the elements - parentID, chilldID, dependentID, and siblingID from the planItemSetType element in the XSD.

The elements parentID, childID, dependentID, and siblingID are set in the generated execution plan and represent the relationships between the plan items. They are not allowed to be modified by the process components.

SetPlanReply NO NA

Interface Schema changes, if any

Justification for schema changes



Interface Functionality in BE TDS

Justification for Discontinuation

DeleteOrderRequest

DeleteOrderReply

Deletes the order from TDS completely and responds accordingly.

Order is not allowed to be deleted from OMS database through a JMS interface.

SetOrderRequest

SetOrderReply

Accepts the request from Orchestrator only to set the order in TDS backing store and responds back accordingly.

Order data is already available in OMS database. There is no need for Orchestrator to do that again.

SetOrderStatus

Request

SetOrderStatusReply

Accepts the request from Orchestrator only to set the final status of order, for example, COMPLETE/CANCELLED in TDS and responds back accordingly.

The order status is already being updated in OMS database using the order notifications published by Orchestrator.

DeletePlanRequest

DeletePlanReply

Deletes the Plan from TDS completely and responds accordingly.

Plan is not allowed to be deleted from OMS database through a JMS interface.

SetPlanStatus

Request

SetPlanStatusReply

Accepts the request from Orchestrator only to set the final status of plan, for example, COMPLETE/CANCELLED in TDS and responds back accordingly.

The plan status is already being updated in OMS database using the plan notifications published by Orchestrator.

GetKeyMapping

Request

GetKeyMapping

Reply

Accepts the request from process components to return the set of orderRef, orderID and planID based on any one of these passed as a parameter in the request.

The PlanItemExecuteRequest sent by Orchestrator to the process component contains all these fields i.e. orderRef, orderID, planID, planItemID, and so on.


10 | Release Notes

• ActiveFulfillmentServices (AFS) rewrite - The SOAP/HTTP and SOAP/JMS web services exposed by ActiveFulfillmentServices BW component have been rewritten in Java and merged as an integral part of omsServer component. All the JMS interfaces are unchanged in terms of destinations. The following are the notable changes:

— All the necessary global variables from AFS BW deployment ear have been added as configuration properties under AFS Properties and OMS AFS Configuration categories under OMS configurations. These properties can be configured using the Configurator.

— The endpoints of the SOAP over HTTP services are changed. For details, see TIBCO Fulfillment Order Management Web Services. For example, the following is the changed end-point for the inventort service: http://<Host>:<Port>/omsServer/api/InventoryServiceHTTP.

— The SOAP over JMS WSDL for all the AFS services has been configured to use http://schemas.xmlsoap.org/ws/2004/09/policy, http://schemas.xmlsoap.org/ws/2005/07/securitypolicy namespace to enforce webservice security.

• Offline Model Loading Changes - In ActiveFulfillment 1.2.0, a single directory set was used for each type of data model in the offline mode. All the offline model publish requests including web service, polling, and BE engine startup requests were served using the single directory set. Two separate directory sets are now maintained for offline data models as follows:

Master directory set:

For serving the offline catalog publish request received from the BE engines (AOPD, OCV, and Orchestrator) on their startup.

New configurable master directory set is introduced for each data model.

On receiving the engine startup request JMS message from the BE engines, OMS-AFI component reads the specific model files from the master directories to publish the models to the respective BE engines.

Once read, the model files are NOT moved from the master directory and are maintained as -is. A copy of the file is created into the corresponding master success or failure directories based on whether the 'read and publish' operation is successful or failed.



Non-Master directory set:

For serving the offline catalog publish SOAP web service request and for incremental polling.

Different directory set, henceforth called non-master directory set, is maintained for each data model.

The polling mechanism would poll the non-master model directories at a configured time interval. If any new file is found in a non-master model directory, the OMS-AFI component reads the model file and publish the models to the respective BE engines.

The offline model publish SOAP web service request can be used to publish the modified models from the non-master directories 'on demand' without waiting for the polling interval to complete for reading and publishing the models.

Once read, the model files are REMOVED from the non-master directory. A copy of the file is created into the corresponding non-master success or failure directory based on whether the 'read and publish' operation is successful or failed.

• Database Schema Changes - There are changes in the database schema for the following components:

— OMS

— Orchestrator

— OCV

• XML/WSDL Changes - There are changes in some of the schema and WSDL as follows:

— When submitting orders, the user can specify the priority of an order. The order schema has been changed and the

If a new file is added in a non-master directory for loading the models on demand, the same must be synched up in the corresponding master directory. This is to ensure that the updated models are published to the BE engines on their next restart.

TDS UDF data is being merged into OMS as part of the migration process.

Refer to the Database Schema Changes section in the TIBCO Fulfillment Order Management Administration document.


12 | Release Notes

http://www.tibco.com/aff/order:orderHeader element of submit order has new element orderPriority.

— The element InventoryId is present under the element Item in the following responses: http://www.tibco.com/AFF/OCV/services:ReassignInventoryItemsReply http://www.tibco.com/AFF/OCV/services:RemoveInventoryItemsReply http://www.tibco.com/AFF/OCV/services:UpdateInventoryItemsReply

— The enumerationrestriction on action element is now removed from http://www.tibco.com/aff/order:lineRequestype.

— Replaced planFragmentType element with owner element, and added recordType from http://www.tibco.com/aff/planfragments:planFragment.

• Date Format Configuration - This finctionality allows you to select the specified date format in the Configurator. Accordingly, all the dates are shown in the OMS UI application.

• Logging Date and Time Format - This allows you to see the log timings in milliseconds for the BusinessEvents components.

• Password Encryption - Passwords in all the configuration files are now encypted in place of plain text format in the previous release.

• Visualizing Dependencies and UDFs in the GANTT Chart - This functionality allows you to see the dependent products and their UDFs for each plan item.

• Grid View now displays the plan items in the same order as in the GANTT Chart View.

• Color-coded/Visual Plan Status Progress - GANTT Chart View and Grid View now display the color-coded visualization icon against each plan item. Thus, the user can identify the plan or plan items progress easily using them.

• OrderID as New Column - On the Browse Orders and Plan page of the OMS UI, the OrderId is added and the user can select OrderID columns to be shown in the list.

• Easy Order Line Identification - The order lines are now identified by a label composed of the line number, the product and the action, providing a meaningful information about the order line. For example, <Orderline Number>:<Ordered Product>:<OrderLine Action>

• O the Order Explorer, when the user switches an order line, the selected tab on the right side used to switch back to the General tab. This is now enhanced to display the same tab even if the user changes the order line. With this enhancement, the user can see the same tab across the order lines without hassle.



• Adjustable Column Width - The user can now drag and adjust column width according to the requirement in the OMS UI.

• Change in the OrderID and PlanID Generation - Now Orchestrator creates the PlanID using the 'globally unique UUID' generator.

Release 1.2.0• Schema Validation Constraints - SubmitOrderResponse, CancelOrderResponse,

and AmendOrderResponse have an additional attribute BusinessTransactionID.

• The ConfigValues_OMS.xml file now has a property com.tibco.af.oms.webservice.useExternalBusinessTransactionId. The default value is false. If the value of the property is set to true, then the value of ExternalBusinessTransactioID is used as BusinessTransactionID as long as ExternalBusinessTransactioID value provided is unique.

• GetOrderExecutionPlan web service, and GetPlanRequestEvent, GetPlanItemRequestEvent interfaces in TDS return the originally set value of a UDF in the originalValue element along with all the existing elements.

• Order Summary - If there is large difference in the number of orders in the various statuses, for instance, 10 orders in the Cancelled state, and 20000 in the Complete state, then the default scale may not render all statuses properly. You can change the default scale to logarithmic scale through the Edit Preferences User Interface.

• GetEligibleProducts service checks for the segment compatibility before returning eligible products. GetEligibleProducts service returns the matching products based on customerId and segment (name and type).

Release 1.1.0• GetOrderTask web service has been renamed as GetOrderExecutionPlan.

• The Audit Utility was used to get the total number of processed orders . The Audit Utility has been replaced with the Order Management System Dashboard.


14 | Release Notes

• The Configurator now has two options:

— Configurator GUI: This GUI allows you to configure various ActiveFulfillment components. In addition, it also provides the ability to do the EMS and database setup for the components.

— Deployment Tool: This command-line tool allows you to deploy or undeploy the ActiveFulfillment components in Custom and Batch modes.

Release 1.0.0There are no changes in functionality in this release.


Deprecated and Removed Features | 15

Deprecated and Removed Features

This section describes deprecated features (if any), and lists features, if relevant, that may be useful alternatives to the deprecated features. Any use of a deprecated feature should be discontinued as it may be removed in a future release. You should avoid becoming dependent on deprecated features and become familiar with the suggested alternative features.

This section also lists features that are removed (if any).

Release 2.0.1

Removed Features

No features are removed in this release.

Deprecated Features

No features are deprecated in this release..

Release 2.0.0

Removed Features

• iPCAdapter and iPEAdapter sample projects are not supported.

• The Silverlight technology used for the GANTT chart is now removed.

Release 1.2.0

Removed Features

• Cancelled Order Management System Dashboard component has been removed.


16 | Release Notes

Release 1.1.0

Deprecated Features

TIBCO ActiveFulfillment does not support jeopardy management out of the box. If you require Jeopardy management, use iProcess Conductor in conjunction with ActiveFulfillment 1.1.0.

Removed Features

No features are removed in this release.


Migration and Compatibility | 17

Migration and Compatibility

Release 2.0.1• TIBCO Fulfillment Order Management 2.0.1 is compatible with TIBCO

Fulfillment Catalog 2.0.0.

• The migration process supports 1.2.0 HF-009 to 2.0.1. For details, refer to the Fulfillment Order Management Migration section in the TIBCO® Fulfillment Order Management Installation and Configuration document.

Release 1.2.0• The OMS database schema has been updated for TIBCO ActiveFulfillment

1.2.0, and the upgrade script Upgrade_1.1_to_1.2.sql is available at the $AF_HOME/db/oracle/oms location.

• Some of the queues and bridges have been replaced by the new queues and bridges. The migration script OMS_EMS_Upgrade_1.1_to_1.2.txt for upgrade to TIBCO ActiveFulfillment 1.2.0 is available at the $AF_HOME/ems location.

• The script migrateProperties.sh to migrate properties for all ActiveFulfillment components is available at the $AF_HOME/bin location.

• ActiveFulfillment 1.2.0 is compatible with ActiveCatalog 1.2.0.

Release 1.1.0The underlying software components of TIBCO ActiveFulfillment 1.1 differ from that of release 1.0. Specifically, the responsibilities of iProcess Conductor and iProcess Engine components in TIBCO ActiveFulfillment 1.0 are replaced with Order Management Server, AF Orchestrator, and TIBCO BusinessWorks (for developing process plan fragments) in TIBCO ActiveFulfillment 1.1. You must manually port any existing iProcess Engine process flows to BusinessWorks. Alternatively, you can use the included iPEAdapter sample project to configure existing iProcess Engine process flows for TIBCO ActiveFulfillment 1.1 use. The sample project is provided as a starting point only; you need to build your own integration from TIBCO ActiveFulfillment 1.1 to iProcess Engine.

Release 1.0.0There are no migration procedures or compatibility issues in this release.


18 | Release Notes


Closed Issues | 19

Closed Issues

The table in this section lists issues that were closed in the named releases.

Closed in Release Key Summary

2.0.1 AF-2579 The ProductComprisedOf relationship did not accept the same product twice for different Actions.

Provide comma-separated values for defining multiple actions.For example, CREATE, MODIFY, HOMEMOVE.

2.0.1 AF-2571 AF Configuration did not support oracle RAC service name.

2.0.1 AF-2570 The MilestoneDependsOn and ProductDependsOn relationships ending to or starting from a plan item (with a LINKID) were not preserved. This was observed when this plan item was affinity-grouped (without any condition) with another plan item having a different LINKID UDF value from the plan item being merged.

2.0.1 AF-2540 There was no projlib library to be used in Business Studio with BE events.

2.0.1 AF-2531 The Characteristic relationship could not be configured/defined to a product twice with different actions on the relationship.

Provide comma-separated values for defining multiple actions. For example, CREATE, MODIFY, HOMEMOVE.

2.0.1 AF-2519 Order Summary query was run every 5 minutes.

2.0.1 AF-2516 Executing SyncSubmitOrder over JMS returned a wrong error message.

2.0.1 AF-2496/AF-1979 PlanFragment is set incorrectly when different plan Item grouped together having different action. With different combinations of actions, the action is always set correctly, but the PlanFragment is not chosen correctly. This is because the PlanFragment is being chosen based on an order line action rather than the overall PlanItem action which is what it should be.


20 | Release Notes

2.0.1 AF-2494 Disabling the log writing to the AUDIT_TRAIL database table without disabling the OMS notification was not possible.

2.0.1 AF-2493 Insufficient LINKID UDF information to define order line parenting for multi-level hierarchy of multi-instantiable optional child products.

2.0.1 AF-2492 Product decomposition did not work correctly for the ProductDependsOn or ProductRequiredFor relationships.

2.0.1 AF-2491 MilestoneDependsOn did not take the LinkID into consideration.

2..0.1 AF-2470 Memory leak was discovered in the Orchestrator agent.

The SetPlanOMSEvent references in the Orchestrator agent did not clean up as per heap dump analysis. This led to the Orchestrator agent going Out of Memory after sometime, depending on the order load.

2.0.1 AF-2468 The ProductDependsOn relationships were missing sequencing direction indication.

2.0.1 AF-2467 GetOrderDetails SOAP operation, when used against the OMS server, did not deserialize the SOAP envelope for some Orders.

2.0.1 AF-2466 The requiredByDate element specified only at the order header level, was ignored in AOPD while generating the execution plan.

2.0.1 AF-2465 OMS Withdraw Order service did not work for orders with amendments in the incomplete state.

2.0.1 AF-2464 While generating the AOPD plan, the java.lang.OutOfMemoryError: Java heap space error was reported on invoking the same order again.

2.0.1 AF-2463 If the line1 or locality or country or postcode element is not passed, then validation error showed up, However, for empty elements no validation error was displayed.



Closed Issues | 21

2.0.1 AF-2460 Singleuse defined product was coming in successive plan when the same product was ordered again. In case of PDO/PRF relationship, Inventory SingleUse use case was not working as specified.

2.0.1 AF-2458 Milestone implementation was incorrect. The status of the plan item changed from PENDING to EXECUTION immediately after fulfilling the dependency for an intermediate milestone.

2.0.1 AF-2451 Using ActiveSpaces as Operational Data Store for the Jeopardy Management System resulted in NullPointerException while retrieving objects from cache.

2.0.1 AF-2424 For cancelled orders, Gantt chart did not show actual release time for the milestones when user selected the actual plan view.

2.0.1 AF-2352 The migration from AF 1.2 to FOM 2.0 is not certified with this release because of a known issue, BE-17616 in BE 5.1.0. The migration will be certified post BE-17616 fix which is tentative in BE 5.1.0 HF 003.

2.0.1 AF-2205 The throughput of the FOM 2.0 system is degraded by 50% compared to AF 1.2 if TIBCO ActiveSpaces 2.0.1 is used as cache in TIBCO BusinessEvents 5.1.0.

2.0.0 AF-2342 The dependencies were not being set as expected in case of non-autoprovisioned products (autoprovision=false) with LinkID defined for certain type of product models and sequence of order lines.

2.0.0 AF-2341 Sequencing for non-autoprovisioned products (autoprovision=false) was not working as expected for certain product models.

2.0.0 AF-2301 AffinityCorrelation for Conditional Affinity did not work as per specifications.

2.0.0 AF-2057 OMS failed to process SetPlanItemRequest and did not update UDF for some planItems.



22 | Release Notes

2.0.0 AF-2054 On the OMS UI, the plan GANTT chart was not getting displayed for some plans due to the duplicate entries corresponding to a plan fragment section (for example, START-END) in the SECTION table.

2.0.0 AF-2052 UDF name syntax was not backward compatible.

To fix this, a new global variable 'AFF/OfferConfigurationValidation/Flags/AOPD/EnableAffinityUDFParent' has been added. To use the new syntax, set this variable to 'true'. The default value is 'false', that is, the old syntax is used.

If you require syntax addressed in AF-1736, you must change this flag to ‘true’.

2.0.0 AF-1853 Cyclic Dependency was observed for certain product models during crosslink affinity.

2.0.0 AF-1852 DEPENDENT_PRODUCT functionality was not working for comma-separated productIDs and working incorrectly with LinkID.

2.0.0 AF-1755 Orchestrator was not consuming some of the plan item execution responses from the EMS queue.

2.0.0 AF-1741 OMS configurations are now improved to configure fault tolerant JMS servers.

2.0.0 AF-1740 Reuse of Common Products during Plan generation in AOPD.

2.0.0 AF-1739 AffinityGroup CrossLink was not working with only one level in the product hierarchy.

2.0.0 AF-1737 Run periodic cleanup of only Activity Log with date and order status as parameters.

2.0.0 AF-1736 Common characteristics of the auto-provisioned products were not identified.

2.0.0 AF-1735 AOPD crashed due to high CPU usage and the 'Out of Memory' error in case of the Crosslink Affinity.



Closed Issues | 23

2.0.0 AF-1734 Several incoming ActiveFulfillment Orchestrator destinations were not suspended and hence the Orchestrator engine failed to process the messages on these enabled destinations due to the unavailability of process component model.

2.0.0 AF-1543 OMS GetOrderExecutionPlan returned a marshalling error if a UDF with an empty value was in the plan.

2.0.0 AF-1542 SingleUse worked only on one level of a product hierarchy.

2.0.0 AF-1541 Longer PlanItem name or description in Orchestrator & TDS lead to backing store database constraints violation.

2.0.0 AF-1521 AOPD sent a wrong AOPD request when the order was cancelled.

2.0.0 AF-1515 Single order on a pre-production environment was taking more than a minute to complete.

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

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

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

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

2.0.0 AF-1399 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).

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

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



24 | Release Notes

2.0.0 AF-1396 OMS did not allow configuring ORACLE RAC connection URL.

2.0.0 AF-1394 Indexes were added to OMS tables and expiration period was set on the notification topics.

2.0.0 AF-1393 CrossLink Affinity issue.

2.0.0 AF-1392 A "PlanMap not found for PlanID PLAN XXXX" error was displayed when auto purge was set in the ORCH Agent.

2.0.0 AF-1391 For a planItem, multiple UDFs with the same name and a different value could not be set.

2.0.0 AF-1390 For the OMS server, Factory names could not be configured in the configuration file, ConfigValues_OMS.xml.

2.0.0 AF-1389 OMS did not support all the Delivery Modes that EMS supported.

2.0.0 AF-1387 Column length was not enough for MILESTONE_DEPENDENCY.PLANITEMID.

2.0.0 AF-1386 The getProductInformation interface of AFS was performing slowly.

2.0.0 AF-1385 Not all product models were loaded by ActiveFulfillment.

2.0.0 AF-1384 Loading Offline product models with more than 10,000 files into ActiveFulfillment was very slow.

2.0.0 AF-1383 SLA notifications being sent after order/plan removed from orchestrator.

2.0.0 AF-1382 Plan Items were displayed as NULL when Autoprovision is used.

2.0.0 AF-1381 Offline Catalog republishing was not working.

2.0.0 AF-1379 Purge script performance was slow.

2.0.0 AF-1378 The 'redeliveryPolicy' parameters were not externalized for message redelivery policy in the OMS server.



Closed Issues | 25

2.0.0 AF-1291 In the OMS UI, the Grid view did not show more details for Point and Time Dependencies.

2.0.0 AF-1285 Product eligibility is giving incorrect result

2.0.0 AF-1199 Created date is not updated correctly for plan UDFs.

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

2.0.0 AF-1009 OMS consumed high memory when the user was trying to access the Plan information with high data volume.

2.0.0 AF-1005 The migration utility did not display the new properties in the FOM Configurator User Interface.

2.0.0 AF-976 Wrong plans were generated for the Affinity groups. For example, BUNDLE comprises Service1,Service2, and Service3 without sequencing. Each service includes A,B, and C, which are auto provisioned and sequenced: A:1,B:2,C:3. C had Affinity group plan fragments defined. When an order was submitted with OL1=BUNDLE, OL2=Service1, OL3=Service2, and OL4=Service3, the affinity grouped Cs only depended on one B only.

2.0.0 AF-946 OMS returned an error when the order was submitted with a non-numeric order line number. For instance, string as the order line number (1-LI01).

2.0.0 AF-868 On the OMS UI, under the Orders tab, the Plan View would display the pending status of intermediate milestones for completed orders. The same error was also returned when web services would execute for the getOrderExecutionPlan.

2.0.0 AF-787 For some special cases of Autoprovisioning, AOPD creates incorrect dependencies as the dynamic dependency of the product is associated with the product mentioned in the orderline, rather that the products decomposed from the orderline through the product model.



26 | Release Notes

2.0.0 AF-767 The GetOrderExecutionPlanRequest web service would return the marshalling error, ’The content of element 'ns5:udf' is not complete’ for decomposition-related orders.

2.0.0 AF-764 On the OMS UI, under the Orders tab, the order search on the Browse Orders page did not show the correct results. For instance, searching for the order TC_01 would return TC_01 and TC001_<ABCD> as a search result.

2.0.0 AF-558 The OPD request schema had an orderRef length limit of the 100 characters, causing failure for orderRefs with length greater than 100 characters. The maximum orderRef field length is 125 characters.

2.0.0 AF-519 AF orchestrator did not behave consistently if GLB_CleanupObjectsAtEndOfOrder is set to true.

2.0.0 AF-514 GANTT chart shows the 12 Hr (A.M./P.M.) time format.

2.0.0 AF-403 The installer didnot update SSL Port accepted from the user interface.

2.0.0 AF-355 OCV did not return validation error if the submitted order did not have any orderlines.

1.2.0 AF-949 TopicConnectionFactory and QueueConnectionFactory variables of Active Fulfillment Services could not be set using TIBCO administrator.

1.2.0 AF-945 If an order was submitted when OMS was not running and later when OMS was restarted, an error was thrown.

1.2.0 AF-869 The UDF field OriginalValue is not being set. This should be set with the same value as Value when setPlan is first called by Orchestrator after AOPD. This value should NEVER be changed in the order lifecyle by either setPlanItem or SetPlanItem. The only time OriginalValue should ever be changed is directly by Orchestrator after the Plan Development.



Closed Issues | 27

1.2.0 AF-844 The OCV engine did not allow to enter a JDBC URL while configuring the BE Backing store. You can configure the JDBC URL in TIBCO Administrator. For example, Oracle RAC JDBC URL.

1.2.0 AF-839 The SubmitOrder web service did not return AF generated businessTransactionID as a part of the response.

1.2.0 AF-834 Making a call to the GetOrdersRequest Web service fails to return a meaningful result. This occurred particularly when the order is submitted with any invoiceAddress or deliveryAddress.

1.2.0 AF-830 On the OMS UI, under the Plans tab, the Plan status is displayed as EXECUTION for a withdrawn order.

1.2.0 AF-819 OMS UI is not allowing to Log in.

1.2.0 AF-812 Null pointer exception was displayed in OCV for GetOfferPrice web service.

1.2.0 AF-805 Incorrect Dependencies were generated in AOPD in certain case of Autoprovision as false.

1.2.0 AF-804 If plan item failed, an unconsumed message was displayed on plan item reply queue.

1.2.0 AF-799 When productID was not passed or an invalid productID (record, which was not loaded into AOPD or OCV engine) was submitted in the order, errors were noticed. This issue has been addressed by adding validations in the OrderService WSDL and configure so that exception will be suppressed.

1.2.0 AF-774 userNameTokenBased Error on submitting the order when Enable user name token based security is set to false.

1.2.0 AF-745 Segment based eligibility did not work correctly.

1.2.0 AF-741 OCV threw an error for incorrect product count in the group even when a valid list of products was submitted in the order. OCV did not throw an error when mandatory UDFs were missing in the order.



28 | Release Notes

1.2.0 AF-740 User was able to add only one customer in the AOPD and OCV.

1.2.0 AF-739 For a particular type of a product model, there was a Circular Dependency issue during plan generation between plan items.

1.2.0 AF-738 AOPD was setting incorrect dependencies. For a particular type of a product model, some additional dependencies were introduced in the plan which caused the plan to sequence incorrectly.

1.2.0 AF-737 If Child products (having ProductComprisedOf relationship with parent) with "AutoProvision" set to FALSE were ordered along with the parent product, then dependency on the child product was not generated in the plan.

1.2.0 AF-736 Affinity Group was not working correctly. Affinity Plan fragment names are not considered and only affinity plan type is used to group plan items.

1.2.0 AF-735 Process component override (retryoverride) was not set correctly in Orchestrator due to incorrect mapping in ActiveFulfillment Interface.

1.2.0 AF-734 For a particular type of a product model, the plan was missing some dependencies, while some additional dependencies were introduced for a single use.

1.2.0 AF-718 A typo was found in OMS property name. onStatusChange was spelled as onsStatusChange.

1.2.0 AF-698 The documentation for creating the bridges between ActiveCatalog and ActiveFulfilment was included in the ActiveFulfilment Admin guide rather than the Installation guide.

Updated the ActiveFulfillment 'Installation and Configuration' document in the ActiveFulfilment post-install tasks.



Closed Issues | 29

1.2.0 AF-621 Start and End TimeStamps in Grid View and Gantt View were different.

1.2.0 AF-424 Search for orders fail if an orderRef contains special characters.

1.2.0 AF-214 ActiveCatalog published Product and Customer models based on records present in PRODUCT and PARTY repositories. AOPD and OCV started order processing requests only after receiving Product and Customer models. If there was no record in PARTY repository, Customer model was not published.

This issue has been addressed provided PRODUCTID and PRODUCTIDEXT have Modify permission.

1.2.0 AF-145 When the plan fragments of a child Product Model were modified and received by ActiveFulfillment, the modified child Product Model was not updated in the working copy of the Product Model of the AOPD engine.



30 | Release Notes

Known Issues

The table in this section lists known issues in this release.

Key Summary/Workaround

AF-2632 Summary Purge does not work with migrated orders having extension data associated with them.

Workaround None.

AF-2612 Summary Risk region is getting updated for migrated orders in the execution state.

Workaround None.

AF-2578 Summary Actual release time is shown '0' for completed orders.

Workaround If plan and plan item are in the COMPLETE/CANCELLED state, then use the STATUSCHANGED value of planItem (if milestonestatus is not COMPLETE).

AF-2577 Summary Order Amendment: While viewing enriched plan, getting the com.tibco.aff.jeoms.processor.PlanProcessingException error.

Workaround None.

AF-2576 Summary Order Amendment: Typical and Maximum duration is showing '0' in the enriched plan in case of migrated order.

Workaround None.

AF-2575 Summary Order Amendment: End time stamp of PlanItem execute request received before migration is not correct after migration.Workaround If plan and plan item are in the COMPLETE/CANCELLED state and there is no data available for ENDTIMESTAMP of planItem, then use STATUSCHANGED as ENDTIMESTAMP of the planItem.

AF-2564 Summary All in One Migration Utility: While creating topics, an error is shown indicating topic already exists. This error is shown for only few topics and can be ignored.

Workaround None.


Known Issues | 31

AF-2543 Summary The Dependency Check failed error is shown while uninstalling TIBCO Fulfillment Order Management 2.0.1.

Workaround Remove or comment-out the following line from the businessevents-hf_5.1.1.001_prodInfo.xml file:<dependency description="TIBCO BusinessEvents Server" mustBeInstalled="false" type="feature" uid="Server_businessevents-standard" version="5.1.1.0" vpduid="">

AF-2443 Summary Date filter is not working.

Workaround Another implementation layer can be added to retreive the offer within specified date range.

AF-2442 Summary If the orderSummary flag is set to true, only the orderHeader information should be sent out. All other details should be dropped off.

Workaround Another implementation layer can be added to retreive the orderHeader informaiton.

AF-2433 Summary The UDFs assignment is not working for AssignInventoryItems request, though wokring for AssignInventoryItem.

Workaround Use AssignInventoryItem to assign inventory to customer and UDF.

AF-2430 Summary Accessing Gantt chart of an execution plan immediately after amendment will give error momentarily and Gantt chart may not accurately show the execution plan status and jeopardy related information.

Workaround Access the Gantt chart of the amended order's execution plan after few minutes.

AF-2427 Summary ’Predicted’ view of the Gantt chart may may not show proper status for the plan item of an execution plan.

Workaround Grid view of the execution plan will show accurate status of the plan item of an execution plan.

AF-2421 Summary No pagination for 'Orders in Jeopardy' gadget.

Workaround Scroll down will appear if number of Orders in Jeopardy increases.



32 | Release Notes

AF-2379 Summary Sometimes background color of GANTT chart is lost when zoomed in at Millisecond level.

Workaround Background color coding can be viewed correctly in zoom level seconds and above.

AF-2373 Summary At higher zoom level typical icon might appear coming ahead of the section level bar.

Workaround Try viewing the Gantt at Millisecond level. You will find that the icon is placed correctly or see the tooltip by hovering over the typical end icon and section level bar. You will be able to find out the exact time for typical end and section level bar.

AF-2349 Summary When Orders are filtered based on Submitted Date using operators like <=, >=, the results are not correct.

Workaround None.

AF-2337 Summary Tooltip for attributes in the condition builder or template builder will show “
” instead of line feed.

Workaround None.

AF-2333 Summary The GANTT chart display is not appropriate when you try to access the GANTT chart for an execution plan with the CANCELLED status. This issue is blocked by AF-2426.

Workaround None.

AF-2303 Summary Complex plans with large number of plan items(200 odd) and mutiple dependencies among them are not orchestrated by Orchestrator.

Workaround None.

AF-2262 Summary The dependency between products in PCO sequence is being ignored when milestone dependency is in place in same planfragment.

Workaround None.

AF-2226 Summary FOM Configurator does not validate the input values for the configuration properties against the expected data type thereby allowing even strings for an integer valued properties such as timeout, HTTP port and so on.

Workaround None.



Known Issues | 33

AF-2162 Summary GetOrderExecutionPlan web service doesn't work for resubmitted orders with orderRef same as the order already submitted to OMS which was amended and then withdrawn.

Workaround None.

AF-2144 Summary The UDFs in the rollbackInventory request are not rolled back to previous values.

Workaround None.

AF-2066 Summary Sequencing is not maintained when conditional affinity is defined in the product model.FOM can generate multiple variations of order plans depending on the sequence of appearance of the order lines in the XML order structure when some products in the order lines are grouped through Affinity.

Workaround None.

AF-2033 Summary During UDF merging for affinity, the flavor of the merged UDFs is not copied into the affinity item when a) UDFs are different b) UDFs have same name but different values.

Workaround None.

AF-2008 Summary The updateInventoryItemRequest should update every information in the request, including the status. However, the status is not being updated.

Workaround None.

AF-1879 Summary Tomcat is not able to clear the referenced thread and memory when you try to shutdown the tomcat gracefully.

Workaround None.

AF-1864 Summary In case of order cancellation type of amendments, the merged plan in Orchestrator is not consistent in terms of number of dependencies in the plan item and the number of childID elements in it.

Workaround None.

AF-1669 Summary GetCustomerHierarchy doesnt fetch the Subscribed products for the Subscriber.

Workaround None.



34 | Release Notes

AF-1666 Summary When you submit an order in OMS with multiple UDFs having the same name(s) but different values, then GetOrderExecution Plan webservice does not return those different UDFs in the plan.

Workaround None.

AF-1642 Summary Not a regular scenario. Javascript error only appears when you perform maximize, minimize, and restore gadget actions in sequence in small duration of time.

Workaround None.

AF-1598 Summary The getCustomerImageForSubscriber should return all the details of the subscriber, including the assigned inventory. However, the assigned inventory is not returned in the response.

Workaround None.

AF-1559 Summary The GetSubscriberItems flag is ignored.

Workaround None.

AF-1558 Summary ItemSummary flag is not being handled.

Workaround None.

AF-1361 Summary OMS Sever will not start if EMS property isAuthorizationEnabled is set to true.Workaround Refer to SR_Id:1-DYAJ1J.

AF-1092 Summary Apache Ant based command line deployment utility fails to deploy/un-deploy the engines if any of the input parameters such as password contains '$' character.

Workaround Avoid '$' character in any of the input parameters for the deployment/un-deployment to work.

AF-922 Summary During plan generation, attaching the leaf node to the sequenced sibling’s leaf nodes results in missing the last sequenced sibling’s child.

Workaround None.



Known Issues | 35

AF-851 Summary GetOrders web service returns a schema validation error if OMS-generated response does not comply with corresponding schema.

Workaround Perform the following steps:

1. Set the schema validation to false.

2. Execute the GetOrders web service request again.

3. The response will have list of orders including the order with incorrect data.

4. Analyze the data for inconsistency. The inconsistency might be:

a. Some mandatory element might have gone into database and the response has the inconsistent data.

b. The ACTION element might have been submitted with incorrect value in older version.

AF-813 Summary Invalid rows are retrieved while filtering the orders based on the Submitted Date filter (between < , <=, >, >=).

Workaround None.

AF-524 Summary During plan generation, the leaf child is attached only to either one of the sequenced sibling items executing parallelly. For instance, a product model has three sibling products A,B and C. A has a sequence number 2 while B and C have sequence number 1. While fulfilling these three products, A has a dependency on only one of the products, B or C, instead of having dependency on both of them.

Workaround None.

AF-246 Summary The value of a user-defined characteristic in the product model cannot be overridden if the characteristic is passed with a new value in the order line.

Workaround Pass a UDF in the order line with the same name as the characteristic and the required value.

AF-98 Summary The SubmitOrder web service accepts orders for invalid Customers based on StartDate, EndDate, and Status.

Workaround None.

AF-97 Summary The SubmitOrder web service accepts order lines for Products, which are invalid based on StartDate, EndDate, and Status.

Workaround None.



36 | Release Notes

AF-96 Summary The GetOfferPrice web service is not responding with the correct price value of an offer.

Workaround None.



TIBCO® Fulfillment Order Management Release …2013/03/01 · TIBCO Fulfillment Order Management...

Documents

Transcript of TIBCO® Fulfillment Order Management Release …2013/03/01 · TIBCO Fulfillment Order Management...