| AC-3241
|
Summary: In the Offer and Price Designer, you cannot configure the offer type for a multi-container setup.
Workaround: Update the
fc_opd docker file by adding the following parameters as the ENTRYPOINT parameters:
- -Dfc.poType=PO,BUNDLE,SERVICE
- -Dfc.bpoType=BPO,HARDWARE
You can provide the
poType and
bpoType as required.
|
| AC-3240
|
Summary: An error message is displayed during the creation of an offer in the Offer and Price Designer if you add all the field values first and then add the KeyValue record at the end to the offer being created.
Workaround: Create an offer with the KeyValue first and then edit offer and add other fields. You can also create offer with other fields and then edit the offer with the KeyValue pair.
|
| AC-3230
|
Summary: The
About page has
Launched state listed in the
Offer status section. The launched state is still to be implemented.
Workaround: None
|
| AC-3209
|
Summary: Any record created from the Offer and Price Designer cannot be deleted using the
Bulk Delete operation.
Workaround: None
|
| AC-3205
|
Summary: If the Offer and Price Designer enterprise had only one offer in the
Rejected state, it is not displayed on the
Offer List page.
Workaround: None
|
| AC-3186
|
Summary: The text
TIBCO® Product and Service Catalog is cut on the
About screen.
Workaround: Resize the
About window.
|
| AC-3178
|
Summary: Workitems created before migration vanish from the inbox after you migrate from TIBCO® Fulfillment Catalog 4.1.0 to
TIBCO® Product and Service Catalog 5.0.0.
Workaround: In the inbox, select
ALL in the
State field.
|
| AC-3175
|
Summary: When uploading an image for creating a KeyValue, a null pointer error occurs on the
Hierarchy Management page.
Workaround: You can attach the document from the OPD enterprise.
|
| AC-3132
|
Summary: After you create TIBCO Fulfillment Catalog enterprise solution and try to import data (ZIP file) by using the TIBCO Fulfillment Catalog import data feature, an error occurs inconsistently. An error also occurs if you try to bulk delete the entries.
Workaround: Reimport the ZIP file using the TIBCO Fulfillment Catalog import data feature.
For the error that occurs during bulk delete, perform the process for bulk delete again.
|
| AC-3128
|
Summary: When creating an offer, switching between tabs results in the following error:
Non-matching for creation tag
Workaround: Switch to another tab only after the current task is completed.
|
| AC-3126
|
Summary: During validation of adding the
comprised of relationship, the following error message is displayed:
Cannot specify unrelated records in the same request
Workaround: None
|
| AC-3124
|
Summary: Documentation web help is not working for the TIBCO Fulfillment Catalog multicontainer setup.
Workaround: None
|
| AC-3107
|
Summary: The following error occurs when you start the TIBCO Fulfillment Catalog:
[io.undertow.request] (default task-16) UT005023: Exception handling request to /eml/Login: java.lang.NoClassDefFoundError: Could not initialize class com.tibco.mdm.admin.jmx.LoginStatsManager.
Workaround: Estimate and plan the replication required for TIBCO Fulfillment Catalog pod and update the
replicas parameter in
fc.json before creating the TIBCO Fulfillment Catalog deployment.
|
| AC-3105
|
Summary: The following error message is displayed in the TIBCO Fulfillment Catalog startup logs:
ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 52) WFLYCTL0013: Operation ("add") failed - address: ([
Workaround: None
|
| AC-3075
|
Summary: During delta publish, even the records that are not modified are published.
Workaround: None
|
| AC-2985
|
Summary: The following error message is displayed in the TIBCO Fulfillment Catalog error logs:
ERROR com.tibco.mdm.infrastructure.cache.as.CacheSizeUtility - Distributed and near caches allocated memory exceeded specified Memory
Workaround: None
|
| AC-2898
|
Summary: When a manufacture date for an offer is entered in the Offer and Price Designer and then published in the
TIBCO® Product and Service Catalog, the date is displayed in the following format: 2019-07-26T18:30:00.000Z.
Workaround: None
|
| AC-2879
|
Summary: Date format is not available when entering a date in TIBCO Fulfillment Catalog.
Workaround: When entering the date, ensure that you use the mm/dd/yyyy format.
|
| AC-2961
|
Summary: An error occurs during the importing of an exported .CSV file containing a KeyValue attachment.
Workaround: None
|
| AC-2852
|
Summary: Offer and Price Designer users cannot view the status of a deleted offer or rule until it is rejected or approved by the administrator. The administrator cannot see a request for deletion on the Offer and Price Designer user interface.
Workaround: Log in to TIBCO Fulfillment Catalog as an administrator and approve or reject the rule or offer deletion.
|
| AC-2842
|
Summary:Offers or rules deleted from the Offer and Price Designer are not deleted from TIBCO Fulfillment Catalog. They appear in the Pending Approval state.
Workaround: None
|
| AC-2679
|
Summary: On the
Characteristic,
Segment, or
Sales Channel tabs, modified offers are not updated with new or modified links.
Workaround: After making changes on the
Characteristic,
Segment, or
Sales Channel tabs, navigate to another tab before clicking
Submit. This workaround force updates the new and modified links.
|
| AC-2601
|
Summary: The unit of measurement cannot be viewed when the
Rules Editor page is opened in read-only mode.
Workaround: None
|
| AC-2354
|
Summary: When validating a record on the home page, the following error message is displayed:
Cannot specify unrelated records in the same request
Workaround: None
|
| AC-2211
|
Summary: When you search for products, the autocomplete mechanism only displays up to 20 entries, even if more products match the query.
Workaround: None
|
| AC-2042
|
Summary: In the Internet Explorer browser, the
Catalog Use drop-down list is not displayed.
Workaround: Use other supported browsers.
|
| AC-2027
|
Summary: Event log pagination does not work in PostgreSQL.
Workaround: None
|
| AC-1874
|
Summary: Template instances are not displayed correctly in any of the supported browsers.
Workaround: Increase the screen resolution or reduce the tree width on the left to ensure that the action menu appears on a single line.
|
| AC-1857
|
Summary: Multiple pop-up windows appear when modifying record attributes on the
Hierarchy Management page in any browser except Firefox.
Workaround: Use other supported browsers.
|
| AC-1832
|
Summary: For PostgreSQL database, an exception is thrown if you add a milestone to a plan fragment using the Hierarchy Management canvas.
Workaround: None
|
| AC-1815
|
Summary: For PostgreSQL, TIBCO Fulfillment Catalog installation changes file permissions on PostgreSQL data directory resulting in failure when starting the server.
Workaround: Change the file permission manually before starting the server.
|
| AC-1811
|
Summary: Delta Export does not fetch any data if the Characteristic relationship is added.
Workaround: Add the relation in the forward way instead of the reverse way.
|
| AC-1737
|
Summary: In TIBCO Fulfillment Catalog, the display name of an enterprise can contain multi-byte characters. This causes an issue when the same names are used as Enterprise Internal Name in applications such as TIBCO® MDM where only ASCII formats are supported.
Workaround: Do not use multi-byte characters for the display name of the enterprise.
|
| AC-1684
|
Summary: Removing milestones and adding SLA to planfragment from
Hierarchy Management gives
pf_relationship.
Workaround: Delete the PLANFRAGMENT record and re-create with SLA data only.
|
| AC-1647
|
Summary: You cannot upload images on the
Hierarchy Management and
TIBCO MDM pages.
Workaround: Save and then process the record. Once the record is processed, the image/document link starts working. The image/document link still works even if the record has been changed.
|
| AC-1221
|
Summary: Applying invalid project tag name in a relationship results in a validation error for its reverse relationship.
Workaround: None
|
| AC-369
|
Summary: On the
Graphical Edit page, you can modify the record by using
<access mode="view_record">.
Workaround: None
|
