TIBCO Fulfillment Catalog Release Notes · Release 3.0.0 ... The note icon indicates information...

TIBCO® Fulfillment Catalog ReleaseNotesSoftware Release 3.0.0July 2015

Important Information

SOME TIBCO SOFTWARE EMBEDS OR BUNDLES OTHER TIBCO SOFTWARE. USE OF SUCH EMBEDDEDOR BUNDLED TIBCO SOFTWARE IS SOLELY TO ENABLE THE FUNCTIONALITY (OR PROVIDE LIMITEDADD-ON FUNCTIONALITY) OF THE LICENSED TIBCO SOFTWARE. THE EMBEDDED OR BUNDLEDSOFTWARE IS NOT LICENSED TO BE USED OR ACCESSED BY ANY OTHER TIBCO SOFTWARE OR FORANY OTHER PURPOSE.

USE OF TIBCO SOFTWARE AND THIS DOCUMENT IS SUBJECT TO THE TERMS AND CONDITIONS OF ALICENSE AGREEMENT FOUND IN EITHER A SEPARATELY EXECUTED SOFTWARE LICENSE AGREEMENT,OR, IF THERE IS NO SUCH SEPARATE AGREEMENT, THE CLICKWRAP END USER LICENSE AGREEMENTWHICH IS DISPLAYED DURING DOWNLOAD OR INSTALLATION OF THE SOFTWARE (AND WHICH ISDUPLICATED IN LICENSE.PDF) OR IF THERE IS NO SUCH SOFTWARE LICENSE AGREEMENT ORCLICKWRAP END USER LICENSE AGREEMENT, THE LICENSE(S) LOCATED IN THE “LICENSE” FILE(S) OFTHE SOFTWARE. USE OF THIS DOCUMENT IS SUBJECT TO THOSE TERMS AND CONDITIONS, AND YOURUSE 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 SoftwareInc.

TIBCO, Two-Second Advantage, TIBCO ActiveMatrix BusinessWorks, TIBCO Runtime Agent, TIBCO Administrator,TIBCO Enterprise Message Service, and TIBCO BusinessEvents are either registered trademarks or trademarks ofTIBCO 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 SunMicrosystems, 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 respectiveowners and are mentioned for identification purposes only.

THIS SOFTWARE MAY BE AVAILABLE ON MULTIPLE OPERATING SYSTEMS. HOWEVER, NOT ALLOPERATING SYSTEM PLATFORMS FOR A SPECIFIC SOFTWARE VERSION ARE RELEASED AT THE SAMETIME. SEE THE README FILE FOR THE AVAILABILITY OF THIS SOFTWARE VERSION ON A SPECIFICOPERATING SYSTEM PLATFORM.

THIS DOCUMENT IS PROVIDED “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS ORIMPLIED, 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. CHANGESARE PERIODICALLYADDED TO THE INFORMATION HEREIN; THESE CHANGES WILL BE INCORPORATEDIN NEW EDITIONS OF THIS DOCUMENT. TIBCO SOFTWARE INC. MAY MAKE IMPROVEMENTS AND/ORCHANGES IN THE PRODUCT(S) AND/OR THE PROGRAM(S) DESCRIBED IN THIS DOCUMENT AT ANYTIME.

THE CONTENTS OF THIS DOCUMENT MAY BE MODIFIED AND/OR QUALIFIED, DIRECTLY OR INDIRECTLY,BY OTHER DOCUMENTATION WHICH ACCOMPANIES THIS SOFTWARE, INCLUDING BUT NOT LIMITEDTO ANY RELEASE NOTES AND "READ ME" FILES.

Copyright © 2010-2015 TIBCO Software Inc. ALL RIGHTS RESERVED.

TIBCO Software Inc. Confidential Information.

TIBCO® Fulfillment Catalog Release Notes

Contents

Preface..................................................................................................7Typographical Conventions......................................................................................................8

Connecting with TIBCO Resources........................................................................................10

Chapter 1 Release Notes.................................................................11New Features.........................................................................................................................12

Release 3.0.0..............................................................................................................12

Release 2.1.0..............................................................................................................13

Release 2.0.0..............................................................................................................13

Release 1.2.0..............................................................................................................14

Release 1.1.0..............................................................................................................14

Release 1.0.0..............................................................................................................14

Changes In Functionality........................................................................................................16

Release 3.0.0..............................................................................................................16

Release 2.1.0..............................................................................................................17

Release 2.0.0..............................................................................................................17

Release 1.2.0..............................................................................................................18

Release 1.1.0..............................................................................................................19

Release 1.0.0..............................................................................................................19

Deprecated And Removed Features......................................................................................20

Release 3.0.0..............................................................................................................20

Release 2.1.0..............................................................................................................20

Release 2.0.0..............................................................................................................20

Release 1.2.0..............................................................................................................20

Release 1.1.0..............................................................................................................20

Migration And Compatibility....................................................................................................21

Release 3.0.0..............................................................................................................21

Release 2.1.0..............................................................................................................21

Release 2.0.0..............................................................................................................21

Release 1.2.0..............................................................................................................21

Release 1.1.0..............................................................................................................22

Release 1.0.0..............................................................................................................22

Closed Issues.........................................................................................................................23

Known Issues.........................................................................................................................28


TOC | 5


6 | TOC

Preface

The preface contains information about documentation related to the current document, typographicalconventions, and information on how to contact TIBCO support.


Typographical Conventions

The following typographical conventions are used in this manual.

Table 1: General Typographical Conventions

UseConvention

Many TIBCO products are installed within the same home directory. This directoryis referenced in documentation as TIBCO_HOME. The value of TIBCO_HOME depends

TIBCO_HOME

on the operating system. For example, on Unix systems the default value is<user_home>/tibco.

Other TIBCO products are installed to an installation environment. A productinstalled into an installation environment does not access components in other

ENV_NAME

installation environments. Incompatible products and multiple instances of the sameproduct must be installed into different installation environments. An installationenvironment consists of the following properties:• Name Identifies the installation environment. This directory is referenced in

documentation as ENV_NAME.• Description Provides information about what the environment contains or is

used for.• Path The directory into which the product is installed. This directory is referenced

in documentation as ENV_NAME. The value of ENV_NAME depends on theoperating system. For example, on Unix systems the default value is<user_home>/tibco.

MQ_HOME is the environment variable where TIBCO MDM is installed. For example,/opt/tibco/mdm/8.3.

MQ_HOME

TIBCO Fulfillment Catalog installs into a directory inside MQ_HOME. This directoryis referenced in documentation as AC_HOME. The value of AC_HOME depends on

AC_HOME

MQ_COMMON_DIR the operating system. For example, on UNIX systems the default value is$MQ_HOME/plugins/ac/3.0.

All standard configuration files for workflow and data validation as well as allcustomization are stored in the MQ_COMMON_DIR directory.

Code font identifies commands, code examples, file names, path names, and outputdisplayed in a command window. For example:

code font

Use MyCommand to start the foo process.

Bold code font is used in the following ways:bold code font

• 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]


8 | Preface

UseConvention

Italic font is used in the following ways:italic font

• To indicate a document title. For example: See TIBCO Fulfillment Catalog User'sGuide.

• 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. Forexample: MyCommand pathname.

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

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

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


Preface | 9

Connecting with TIBCO Resources

How to Join TIBCOmmunity

TIBCOmmunity is an online destination for TIBCO customers, partners, and resident experts—a place toshare 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 Documentation

After you join TIBCOmmunity, you can access the documentation for all supported product versions here:

https://docs.tibco.com.

How to Contact TIBCO Support

For comments or problems with this manual or the software it addresses, please contact TIBCO Support asfollows:• 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 username and password. If you do not have a username, you can request one.


10 | Preface

http://www.tibcommunity.com

https://docs.tibco.com

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

https://support.tibco.com

Chapter

1Release Notes

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

Topics

• New Features• Changes In Functionality• Deprecated And Removed Features• Migration And Compatibility• Closed Issues• Known Issues


New Features

This section lists features added in the major releases of this product.

Release 3.0.0The following are the new features in the Fulfillment Catalog 3.0.0 release:

• Database Support

Fulfillment Catalog now supports the following databases:• Oracle 11g• Oracle 12c / 12c RAC• PostgreSQL 9.1.x

• New MDM Support

Fulfillment Catalog now supports and requires TIBCO MDM version 8.3.2 HF-05. To access FulfillmentCatalog you will have to install MDM 8.3.2 HF-05 version on your system.

• Compatibility with JBOSS app server

Fulfillment Catalog is now compatible with the JBOSS 7.1.x application server.

• New Repositories Added

The following new repositories have been added to support Offer and Price Engine changes:• CATEGORY• MIGRATION• REQUIRES_PRODUCT• RULE• RULECONDITION• RULEPARAMETER

• Optional Milestones

Optional Milestone functionality relax the condition of having mandatory child milestones record for theplanfragment record, by adding SLA attribute group to planfragment repository to capture SLA datawhen related milestone record does not exist.

• New Attribute to Product Repository

A new attribute has been added to the PRODUCT repository called RecordUse which contains the metadataof the record that describes whether the record is commercial, technical, or none.

• New Relationships to Product Repository

The following new relationships have been added to the PRODUCT repository:• Category

• ProductGovernedByRule

• ProductToMigrate

• Enforcement of Record Status

A new feature Enforcement of Record Status has been added that provides the following features:• At the time of creating a record or editing a record, assigns the record status field to ‘Testing’.• As a part of the workflow that confirms a record, update the recordstatus to ‘Active’.• As a part of the workflow that DELETES a record, update the recordstatus to ‘Inactive’.

• Exporting Blank Template


12 | Release Notes

A provision has been provided to export blank template, which the user can fill and use it for full or partialimport.

• Pre-created Enterprise

An enterprise with the following details is created and is ready for use after the FC Installation.

FC300Enterprise Name

sampleUser

euc!1dPassword

Release 2.1.0

The following are new features in this release:• Export FC Data - Full

Enables all repository and relationship instance data to be exported to CSV files. The CSV files are generatedfor only those repositories and relationships which have data and can be exported.

• Import FC Data - Full

Allows data to be imported into an enterprise. ZIP files, which may contain one or more data files (CSVformat), are accepted. The content of the ZIP file is validated against a pre-defined set of file names toavoid any invalid file.

• Export FC Data - Partial

Similar to Full Data Export but only selective data from all repositories and relationships are exported.The selection of data is based on the attribute ProjectTagName where user can select one or more tagnames. The file format is the same as Full Data Export.

• Import FC Data - Partial

Also known as Incremental Import. Enables data to be imported based on the snapshot concept. Determinesthe changes which have occurred from the last partial import process and invokes the appropriate recordedit (add/delete/update) process.

• Update/Resolve Relationship Tag

Helps in automating the tagging service for relationships. This feature is also referred to as 'resolvingrelationship tags' because it tries to resolve any conflict in the tagging of parent/child record. This is amanual activity and shall be exercised whenever tags are changed for parent/child record.

Release 2.0.0

The following are new features in this release:• Conditional Affinity Conditional affinity is a new affinity type that contains additional configuration

fields and rules that combine the capabilities of InLink and CrossLink in a single affinity type. Theimplementation is more flexible through the use of configuration fields and XPath expressions fordetermining the logic of the affinity grouping.

• Catalog Synchronization This is a process of importing Customer Facing Services (CFS) record type fromTIBCO Fulfillment Provisioning into TIBCO Fulfillment Catalog on demand.

• ProductDependsOn and ProductRequiredFor Relationships New relationship in the Product repositoryto allow for more flexible Product decomposition. The ProductDependsOn relationship allows businessusers to create top-level commercial Product Offers without explicitly defining sequencing. ExistingProductRequiredFor relationship has been modified to support source and target actions.


Release Notes | 13

• Custom Action Fulfillment Catalog 2.0.0 allows you to define the set of actions, maintained in the ACTIONrepository. You can now define any number of unique fulfillment actions. Until this release, only fourhard coded set of actions - Cease, Provide, Update, and Cancel were supported.

• Group Record The Group Record enables you to group record features for better modeling and productdesign. This is a design time feature. For the purpose of product modeling, the group record is NOT anactual saleable or actionable record. It is a container to express group rules.

• ActionID Relationship The new relationship attribute ActionID is added to the following Relationshipsof Product Repository to associate the custom actions:– Characteristic

– ProductComprisedOf

Release 1.2.0

The following are new features in this release:• Milestone Milestone is new repository to model all the milestones including START and END in a plan

fragment. This repository replaces the PlanFragmentSection repository in AC 1.1.0 to model the sectioninformation between two milestones of a plan fragment using a self relationship namelyMilestoneToMilestone. Also, the inter process milestones dependencies between the plan fragments canbe defined using another self relationship of this repository namely MilestoneDependsOn.

Release 1.1.0

The following are new features in this release:• Graphical Edit This new feature allows to edit the graphical representation of product models related

through a specific relationship in a specific repository.

• Manage Relationship A new feature is provided which allows the selection of multiple types of relationshipin just one interaction.

• Offline Catalog A new feature that enables the ActiveFulfillment application to fulfill the orders andreduces the dependency on the ActiveCatalog to be Online.

• Data Validations Basic data validations, including True/False dropdown selections, have been includedas part of the base metadata for the AC repositories.

• Metadata Cleanup Display names for some repositories and attributes have been simplified.

• Relationship Attribute Metadata Cleanup Relationship attributes have been rationalized per eachrepository instead of each repository having the same number of relationship attributes defined.

Release 1.0.0

The following are new features in this release:• Visual View To view the graphical representation of product models related through a specific relationship

in a specific repository.

• Manage Relationship To add, remove, and group relationships for product models. You can search forproducts.

• Record Count Utility A command-line utility to get the count of active records in ActiveCatalog.

• Bulk Model Publisher To publish full model to a predefined TIBCO Enterprise Messaging Service topic.The new workflow wfin26bulkmodelpublisherv1.xml definition is created in ActiveCatalog to publishthe product, customer, and segment model.

• Single Record Model Publisher To publish a single record to a predefined TIBCO Enterprise MessagingService topic.


14 | Release Notes

The modified wfin26producteditapprovalv3.xml and wfin26productaddapprovalv3.xml workflows areprovided to publish a single record.


Release Notes | 15

Changes In Functionality

This section lists changes in functionality in the major releases of this product.

Release 3.0.0The following are the changes to existing features in the Fulfillment Catalog 3.0.0 release:

• Hierarchy Management

The Hierarchy Management utility has changed and the changed utility addresses all limitations of itsprevious version alongwith few new additions:• Enabling the utility for every repository and relationship.• Options to maintain multiple relationships tree at same time (though in different canvas).• Allowing drill-down to nth level of relationship.• Completely new user experience.• Easy information on user interface.• Add new record and use it on the canvas.• When user adds a new record type, the corresponding image can be dropped into the image directory.

This image would then start popping up on the screen.• Cashing-in data at client side, which results in improved performance of the overall utility.

• Fulfillment Catalog User Interface Menu Update

All Fulfillment Catalog related functionalities are now accessible via a new menu called "FulfillmentCatalog Operations".

• Enhancements to Import or Export

Export FC Data and Import FC Data have the following enhancements:– Separate menu for Full or Partial Export is now consolidated into a single menu. The same is applicable

for Import as well.– Additional option to export a blank template. This blank template can be used to populate data and

then use for import into FC.– Can be triggered through GUI without having to manually create dummy records. The feature

implements the mandatory dummy record creation and this was not provided earlier.– Is scalable as any new REPOSITORY, RELATIONSHIP, or ATTRIBUTE can be included with few

configuration changes.– Can also be triggered through a webservice with few changes in their respective workflows.– The exported ZIP file, in case of Export, can be downloaded through Event Log screen.

• Publish Model Enhancement

Bulk Model Publish feature has undergone multiple changes. Some changes are attributed to the additionalsupport required for new engines like Offer and Pricing Engine (OPE) and other changes are to improvethe usability of the features. The changes can be classified as follows:• Performance• Screen changes• Offline file changes• Workflow changes• Download option for offline files

PRICE and DISCOUNT repositories have been added to the existing list of models which can be generatedand published.

Users can publish the metadata of the repository for which the publish model has been triggered.


16 | Release Notes

The publishing of the record is based on the Catalog Use. The valid values for catalog use are 'Commercial','Technical' and 'All'.

• Installer and Configuration Changes

The Universal Installer now takes care of certain postinstallation activities and configurations like:• Merging FC Resources• Application Server Setup• Merging Configuration Files• Installation with Oracle• Installation with PostgreSQL• Pre creation of Sample Enterprise

For detailed information on the Installation and Configuration changes, see "Post Installation Tasks" topicand "Configurator" topic in the TIBCO Fulfillment Catalo Installation and Configuration Guide.

• Relationship Attribute Update

The relationship attribute ProjectTagName of every existing relationship has been updated and the Lengthhas been set to 4000 from 256.

• Catalog Validation Update

A new validation rule is added for ProductComprisedOf relationships in PRODUCT repository. A parentrecord with RecordUse="Technical" can only have a child with RecordUse in ("Technical", "All"). However,the reverse is not true. The formula for a valid ProductComprisedOf relationship would be as follows:• If (parent/RecordUse = "Technical") then (child/RecordUse in ("Technical", "All"))• If (parent/RecordUse = "Commercial") then (child/RecordUse in ("Commercial", "Technical", "All"))• If (parent/RecordUse = "All") then (child/RecordUse in ("Commercial", "Technical", "All"))

• Transformation (Stylesheet) Update

Style sheet mpfromcatalogitemtobulkproductmodelv1.xsl is modified to export SINGLEUSE as a newCharacteristic. This additional Characteristic is expected to be used by OMS.

Release 2.1.0

The following are changes in functionality in this release:• Hierarchy and Relationship Management

The graphical user interface has been updated to improve the user experience and the performance.

• Added a new relationship attribute called SequenceDirection in the ProductDependsOn relationship

The valid values of this attribute are either 'AFTER' or 'BEFORE'. This attribute will be paired with providedvalues of SourceAction and TargetAction. For each SourceAction and TargetAction, there will be a valuedefined for the sequenceDirection attribute.– A 'BEFORE' sequence direction will create a dependency of the target product on the source product.– An 'AFTER' sequencing direction will create a dependency of the source product on the target product.

This is the default setting.

If no value is provided in the sequenceDirection attribute, the attribute defaults to 'AFTER," and thefunctionality works as it did before the introduction of sequenceDirection relationship attribute. Thisallows backward compatibility. Depending on the value defined in the sequenceDirection attribute willcreate a dependency of the target product on the source product or it will create a dependency of thesource product on the target product.

Release 2.0.0

The following are changes in functionality in this release:


Release Notes | 17

• TIBCO Fulfillment Catalog introduces a new Hierarchy View screen, which provides TIBCO FulfillmentCatalog's graphical representation of records in the PRODUCT repository that are related through aProductComprisedOf relationship. The Hierarchy View screen allows you to add, modify, handle recordsand relationship between them.

• A new ACTION repository is added.

• A new ActionID relationship attribute is added to the following relationships of the Product repositoryto associate the custom actions.

• The following new relationships are added to the PRODUCT repository:– ProductDependsOn

– ProductHasCustomPlanFramgment

• Product model schema is modified in TIBCO Fulfillment Catalog 2.0.0. New relationship attributes areadded to the following relationships:– ProductRequiredFor

– Characteristic

– ProductComprisedOf

– ProductHasProvidePlanFragment

– ProductHasUpdatePlanFragment

– ProductHasCancelPlanFragment

– ProductHasCeasePlanFragment

The product model schema ProductModel.xsd is located in the $AC_HOME/schema/models directory.

• A new attribute Owner is added to the Product repository. This can be used to identify the source of data.For example, when integrating Fulfillment Catalog with Fulfillment Provisioning, the data imported fromFulfillment Provisioning will have the value as ’FP’. This product model will have the new Owner element.

• The lastModifiedOn element is now made optional in the Product Model schema. This is done due tooffline model loading issue, and it mandates to modify the element value to the latest value, otherwisemodel will not be loaded. Therefor, a product model generated by Fulfillment Catalog 2.0.0 will not havethe lastModifiedOn element.

• The PlanFragment model schema is modified in Fulfillment Catalog 2.0.0. The display name of the schemaelement PLANFRAGMENTTYPE is modified as OWNER. A new record_type attribute is introducedinthe Planfragment repository. The Planfragment model schema PlanFragmentModel.xsd is located inthe $AC_HOME/schema/models directory. Therefore, the Planfragment model has two new elements -OWNER and RECORD_TYPE with dropped existing element PLANFRAGMENTTYPE.

• The Wfin26bulkmodelpublisherv1.xml workflow is modified to add new relationships and activity topublish the PRODUCT and ACTION models.

• The following maps are modified to generate updated models:– The mpfromcatalogitemtobulkproductmodelv1.xsl file.– The mpfromcatalogitemtobulkplanfragmentmodelv1.xsl file.

A new map mpfromcatalogitemtoactionmodelv1.xsl is created to publish the ACTION model.

• Validation files are midified to provide the basic validation while creating or modifying record. Thelocation of the rule base file for each repository is:$MQ_COMMON_DIR/<ENTERPRISE_NAME>/catalog/master/<catalogid>/cat alogvalidation.xml.

Release 1.2.0

The following are changes in functionality in this release:• The relationship attributes for ProductRequiredFor relationship have been added in TIBCO ActiveCatalog

1.2.0. These attributes are similar to ProductComprisedOf relationship attributes and are published in thesame way.


18 | Release Notes

• Product model schema has been modified in TIBCO ActiveCatalog 1.2.0. to introduce intermediatemilestone feature. To model intermediate milestone in product model, relationships(ProductHasCancelPlanFragment, ProductHasCeasePlanFragment, ProductHasProvidePlanFragment,ProductHasUpdatePlanFragment) are created. While creating and publishing product record, when youassociate plan fragment relationship record with product, information appears in 'plan' element accordingto the Product Schema other wise planFragments, affinityPlanFragments, affinityType element will bepublished. The product model schema ProductModel.xsd is located at the $AC_HOME/schema/modelslocation.

• The Graphical Edit User Interface now uses meta-data through Collaborative Information Manager webservice for displaying record and relationship attributes.

Release 1.1.0

There are no changes in functionality in this release.

Release 1.0.0

There are no changes in functionality in this release.


Release Notes | 19

Deprecated And Removed Features

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

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

Release 3.0.0The following features have been deprecated or removed from the Fulfillment Catalog 3.0.0 release:

Deprecated

None.

Removed

"Hierarchy View" and "Hierarchy Edit" options in the toolbar on "Browse and Search Screen" has beenconsolidated into one option called "Hierarchy Management".

Relationship Management - The Manage Relationship option that allowed you to modify multiple relationshipsfrom the same page has been removed, as "Hierarchy Management" has been improved to include allrepositories and all relationships.

Release 2.1.0

None

Release 2.0.0

Removed Features:

No features are removed in this release.

Deprecated Features:

The Silverlight, which was used to display the Graphical View, is not supported in TIBCO Fulfillment Catalog2.0.0. The Silverlight is replaced with the GWT technology.

Release 1.2.0

Removed Features• PLANFRAGMENTSECTION repository has been removed in TIBCO ActiveCatalog 1.2.0.

• GroupOptinal attribute has been removed from the Product repository metadata in TIBCO ActiveCatalog1.2.0.

Release 1.1.0

Deprecated Features

TIBCO ActiveCatalog no longer supports single record publish.


20 | Release Notes

Migration And Compatibility

This section lists migration and compatibility in the major releases of this product.

Release 3.0.0Complete steps on migrating from TIBCO Fulfillment Catalog 2.1.0 HF-02 to TIBCO Fulfillment Catalog 3.0.0are outlined in the "Fulfillment Catalog Migration" chapter in the TIBCO Fulfillment Catalog Installation Guide.

For a successful migration, some preparations need to be done followed by the actual migration. There arefew important steps that should be followed sequentially. The steps are as follows:• Migration of MDM 8.2.1 to MDM 8.3.2 HF-05• Installation of Fulfillment Catalog 3.0.0• Backing up files• Rulebase Configuration• Migration of Fulfillment Catalog 2.1.0 HF-02 to 3.0.0• Post Migration Tasks

For complete details, see "Fulfillment Catalog Migration" chapter in the TIBCO Fulfillment Catalog InstallationGuide.

Release 2.1.0

Complete steps on migrating from TIBCO Fulfillment Catalog 2.0.0 hotfix 1 to TIBCO Fulfillment Catalog2.1.0 are outlined in the "Fulfillment Catalog Migration" chapter in the TIBCO Fulfillment Catalog InstallationGuide.• Before migrating to TIBCO Fulfillment Catalog 2.1.0, you must prepare your environment by upgrading

Collaborative Information Manager and installing TIBCO Fulfillment Catalog 2.1.0.

• Then, migrate enterprise data by upgrading the existing enterprise.• Finally, verify that the migration was successful.

Release 2.0.0• Before upgrading to TIBCO Fulfillment Catalog 2.0.0, you must apply TIBCO Collaborative Information

Manager 8.2.1 Hotfix13.

• The ACTION repository is added in the list of catalog repositories. Migration scripts have been providedto update Fulfillment Catalog 2.0.0 metadata to 2.0.0. For more information on these scripts, refer to TIBCOFulfillment Catalog Installation and Configuration.

• TIBCO Fulfillment Catalog 2.0.0 is compatible with Fulfillment Order Management 2.0.0.

• PlanFragment schema is modified in Fulfillment Catalog 2.0.0. To migrate offline plan fragment datamodel from ActiveCatalog 1.2.0 to Fulfillment Catalog 2.0.0, a migration utility is provided. The locationof the migration utility is $AC_HOME/samples.

Release 1.2.0• Before upgrading to TIBCO ActiveCatalog 1.2.0, you must apply TIBCO Collaborative Information Manager

8.1.0 Hotfix5.

• PlanFragmentSection repository has been replaced by Milestone repository. Migration scripts have beenprovided to update TIBCO ActiveCatalog 1.1.0 metadata to 1.2.0. For more information on these scripts,refer to TIBCO ActiveCatalog Installation and Configuration. The data migration from 1.1.0 to 1.2.0 is notsupported in TIBCO ActiveCatalog 1.2.0.


Release Notes | 21

• ActiveCatalog 1.2.0 is compatible with ActiveFulfillment 1.2.0.

Release 1.1.0• Before upgrading to TIBCO ActiveCatalog 1.1, you must apply TIBCO Collaborative Information Manager

8.1.0 Hotfix2.

• Migration scripts are provided to update TIBCO ActiveCatalog 1.0 metadata to 1.1. For more informationon these scripts, refer to TIBCO ActiveCatalog Installation and Configuration.

Release 1.0.0

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


22 | Release Notes

Closed Issues

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

Table 2: Closed Issues

SummaryKeyClosed inRelease

When extending the validation rulebase for the PRODUCT repository, afterchanges to the rulebase, it was necessary to select Save and Process twice toactually save a Product record.

AC-16873.0.0

When there were multiple milestones depends on dependencies, the sameone was received multiple times in the publish product xml.

AC-15693.0.0

The length of ProjectTagName column was not sufficient and the importfailed if the csv file had long value for the ProjectTagName.

AC-14823.0.0

If a project tag was requested to be completely removed, the tag had to beremoved from all repositories, including PROJECTTAG as well.

AC-14693.0.0

The modified records were not related to “TagNames.csv”.AC-14673.0.0

Records without tags were not being removed.AC-14663.0.0

Tag(s) that should not be added to PROJECTTAG repository if it was notpresent in TagNames.csv. PROJECTTAG repository should follow samebehavior as applicable to other repositories.

AC-14653.0.0

If a project tag was requested to be completely removed, the tag had to beremoved from all repositories, including PROJECTTAG as well.

Tag(s) that should not be added to PROJECTTAG repository if it was notpresent in TagNames.csv. PROJECTTAG repository should follow samebehavior as applicable to other repositories.

AC-14643.0.0

If user provided value for the owner field in the offline models, the publishedowner tag was empty instead of the user added value.

AC-14593.0.0

Partial import and Partial Export functionality was not working properly.AC-14393.0.0

The sequence of the use case diagrams, in the FC User Guide, for partialexport of FC data and partial import of FC data was incorrect.

AC-14373.0.0

An OutOfMemory Error was seen during bulkModelPublish.AC-14363.0.0

Fulfillment Catalog allows to manually add more than once the same ProjectTag to a relationship.

AC-14323.0.0


Release Notes | 23


The version information was not displaying in the About page after applyinghotfix 01.

AC-14313.0.0

For the Hierarchy management feature validation was throwing "ERRORCAT-1356: Duplicate Error: Record (E-) exists." when record ID was modified.

AC-13333.0.0

Two event IDs were displayed for Import event logs.AC-13313.0.0

For group records the corresponding attributes tab was not seen.AC-13303.0.0

During migration the validation did not throw any error when the StartDatewas greater than the EndDate.

AC-13293.0.0

Validation did not throw any error for incorrect ACTIONID in relationshipattribute of PCO.

AC-13283.0.0

The Full Import feature was behaving erratically and was importing incorrectdata.

AC-13203.0.0

FC_DUMMY_XXX was required as mandatory record even with valid datapresent in the enterprise.

AC-13083.0.0

Migration: After save and process when user right clicks any record fromthe left hand panel, the menu options are disabled.

AC-12883.0.0

Validation did not throw any error for incorrect ACTIONID in relationshipattribute of PCO.

AC-12833.0.0

Migration: Validation does not throw any error for StartDate greater thanEndDate.

AC-12813.0.0

The Attribute tab was not displayed for a Group record.AC-12643.0.0

A script error is thrown when the user navigates to the Browse and Searchscreen.

AC-12463.0.0

A script error was displayed when the user navigates to the HierarchyManagement screen.

AC-11973.0.0

When importing records with the 'Load Data Source and Import Records'functionality, two event IDs were displayed.

AC-11543.0.0

Display names are not displayed on the Relationship Management screen inthe 'Available Records' or 'Related Records' lists.

AC-11363.0.0


24 | Release Notes


Validation throws an invalid duplicate error message (ERROR CAT-1356)when a record ID was modified.

AC-10563.0.0

A provision for SequenceDirection was required in the PDO relationship.AC-9023.0.0

Fulfillment Catalog was not publishing all ProductDependsOn attributes.AC-7873.0.0

The field length validation rules, across products, had to be synchronized.AC-6813.0.0

SequenceDirection missing in the PDO relationship.AC-11132.1.0

A ProductComprisedOf characteristic cannot be configured twice in a Productwith different Actions on the same relationship.

AC-11112.1.0

The Provide sequence field is removed from the Segment repository.AC-7362.0.0

The Optional field was missing from the ProductComprisedOf relationship.The Optional field is now available under the GROUPINFO attribute group.

AC-7352.0.0

Relationship Attributes did not map for the Milestone Repository.AC-7342.0.0

The DB installation step failed due to incompatible data.AC-7332.0.0

The acpostinstaller.jar file path was pointing to the wrong folder(ActiveCatalog 1.1 lib folder) in the mergexml.sh file.

AC-7322.0.0

On the Manage Relationships screen, clicking the More Actions -> ShowHistory link displayed the following error: GEN-7010: Null parameter Product

AC-2222.0.0

Version Number passed to method showProductHistory of classProductHistoryLogServlet. Program error.

The StartDate and EndDate with any value could not be set to null on theManage Relationship screen.

AC-1972.0.0

The default price types defined in ActiveCatalog catalog validation do notmatch the price types implemented in ActiveFulfillment. For instance, the

AC-5391.2.0

price types in ActiveCatalog drop-down are displayed in the upper case,such as RECURRING and ONE TIME, whereas the implementation for pricingin ActiveFulfillment requires these fields as Recurring and One-Time.

Incomplete data in the product model when published related to the fulldetails required for pricing to work. Specifically, it does not publish theDURATION_UOM value.

AC-5381.2.0

The message to install Silverlight 3 is displayed when using the ManageRelationship or Graphical Edit for the first time.

AC-5261.2.0


Release Notes | 25


Update fails for all those relationships, which share the same PARENT orCHILD.

AC-5071.2.0

Exporting the records fail in a workflow with the following error message:FATAL ERROR FETCH: java.lang.InstantiationException: java.lang.Booleanexceptions.

AC-5041.2.0

Resource security constraints are not applicable to Graphical Edit.AC-5001.2.0

The Graphical Edit view in ActiveCatalog 1.1.0 was missing the followingattributes: GroupID, StartDate, EndDate

AC-4981.2.0

On Graphical Edit screen, saving multiple relationships together throws thevalidation error if some of the relationships have an invalid data. After you

AC-4731.2.0

correct the invalid relationships and save again, you get the following errormessage: SCV-11038: Data unchanged, request ignored.

On the Graphical View screen, Validate button does not work on validatingRelationship Attributes.

AC-4361.2.0

Java script error shown on graphical edit screen, if there is a read only orhide attribute and user tries to modify different attributes, and clicks SaveAnd Process.

AC-3681.2.0

Graphical Edit is not compliant with CIM rule base. For example, somevalidations enforced through rule base may not work correctly with GraphicalEdit.

AC-3511.2.0

New attribute added did not display in the Modify record pop-up.AC-3031.2.0

When you modify Relationship of three or more child records to a singleparent then all of your changes might not be saved.

AC-2871.2.0

Record query Web service request returns with SOAP fault when HTML tagsare present in an attribute.

AC-2501.2.0

If a new enterprise is created using ActiveCatalog configurator, Relationshipattribute GroupOptional data type is shown as string instead of Boolean.

AC-2401.0.1

On the Manage Relationship page, not able to enter dates with single digitsfor the related records.

AC-2361.0.1

Unable to add attribute to PRODUCTCHARACTERISTIC repository.AC-2341.0.1

PRODUCTCHARACTERISTIC has a field with incorrect display name asDate Type instead of Data Type.

AC-2331.0.1


26 | Release Notes


Silverlight web service query not sending the exact attribute in the requestresulting incorrect result in the response.

AC-2321.0.1

Classification box is blank for repositories without classification.AC-2011.0.1

Relationship attributes field level validations.AC-1951.0.1


Release Notes | 27

Known Issues

The table in this section lists known issues in the releases.

Table 3: Known Issues

SummaryChangeRequest ID

Summary: The product cannot be dragged into the canvas after performing a search using theSimilar Search option.

Workaround: Cancel the search. This will load the complete set. Now narrow down to therecord and drag-drop.

AC-1742

Summary: FC allowed the display name of an enterpise to contain multi-byte characters. Thiswill cause an issue because FC uses the same for Enterprise Internal Name as well, which willnot be supported by MDM as MDM only supports ASCII.

Workaround: Do not use multi-byte characters for the display name of the enterprise.

AC-1737

Summary: For the flag ValidateOrderLineUDFRange of OPE Range value should be in followingformat:<ns0:simpleRule> <ns0:name>RANGE_VALUE</ns0:name>

AC-1734

<ns0:ruleSetOutcome>true</ns0:ruleSetOutcome></ns0:simpleRule>

Currently it is in following format:<ns0:rangeValue>true</ns0:rangeValue>

Workaround: You can customize$MQ_HOME\common\<ENTERPRISE_NAME>\maps\mpfromcatalogitemtobulkproductmodelv1.xsl

to include this tag by adding below snippet for [REL_NAME ='Characteristic']:<ns0:simpleRule> <ns0:name> <xsl:value-of select=""RANGE_VALUE""/> </ns0:name> <ns0:ruleSetOutcome> <xsl:value-of select="./CRANGEVALUE"/> </ns0:ruleSetOutcome></ns0:simpleRule>

Summary: When using Hierarchy management, sometimes, adding a relationship gives anerror "Cannot specify unrelated records in the same request" upon validation.

AC-1730

Workaround: None.

Summary: While modifying Parent record, Record Status of the child record remains in ACTIVEstatus.

AC-1726

Workaround: None.

Summary: Hierarchy Management records cannot be saved for the repositories which doesnot have any relationship. Records can not be saved for the repositories like PROJECTTAG,ACTION which does not have any relationship.

AC-1708

Workaround: None.


28 | Release Notes

SummaryChangeRequest ID

Summary: Removing milestones and adding SLA to planfragment from Hierarchy Managementgives "pf_relationship".

AC-1684

Workaround: Delete the PLANFRAGMENT record and re-create with SLA data only.

Summary: Uploading image is not working on both Hierarchy Management and MDM screen.AC-1647

Workaround: Save and Process the record. Once the record is processed then theimage/document link starts working. The image/document link still works even if the samehas been changed.

Summary: Applying invalid project tag name in a relationship throws an error upon validationfor its reverse relationship.

AC-1221

Workaround: None.

Summary: Getting "ERROR There should be planframent associated with Product. EitherProductHas(Provide/Update/Cease/Cancel/Custom)PlanFragment record should be createdor Plan attribute should be defined" for validation

AC-1057

Workaround: None.

Summary: Graphical Edit screen allows to modify the record though <accessmode="view_record">

AC-369

Workaround: None.


Release Notes | 29

TIBCO Fulfillment Catalog Release Notes · Release 3.0.0 ... The note icon indicates information...

Documents

Transcript of TIBCO Fulfillment Catalog Release Notes · Release 3.0.0 ... The note icon indicates information...