Known Issues
The table lists known issues in the version 4.0.0 of TIBCO Fulfillment Catalog.
Issue ID | Summary |
---|---|
AC-2354 | Summary: A "Cannot specify unrelated records in the same request." error is seen when validating on the HM screen.
Workaround: None. |
AC-2335 | Summary: In order to create a TIBCO Fulfillment Catalog enterprise using Configurator, it requires to populate values of the TIBCO MDM host and port details. If the server is configured to SSL only, then there is no option for the user to select a protocol to https.
Workaround: Create an enterprise using a native UI and manually import the metadata. |
AC-2318 | Summary: If accessing Offer and Price Designer using the Chrome browser, the current date does not get displayed when using the UI element date picker.
Workaround: Use other supported browsers. |
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: The dropdown box for the field Catalog Use does not work on the Internet Explorer browser.
Workaround: Use other supported browsers. |
AC-2027 | Summary: Event log pagination does not work in Postgres.
Workaround: None. |
AC-1874 | Summary: Browsers will not display the Template Instance appropriately.
Workaround: Increase the screen resolution, or reduce the tree width on the left, until the action menu appears in single line. |
AC-1857 | Summary: If you are accessing the Fulfillment Catalog GUI using any browser, except FireFox, to modify the record attributes on Hierarchy Management screen, you can open multiple pop up windows during the modification.
Workaround: Use other supported browsers. |
AC-1832 | Summary: An exception is seen if you add a milestone to a plan fragment using the Hierarchy Management canvas. The exception is specific to PostgreSQL.
Workaround: None. |
AC-1820 | Summary: For PostgreSQL, the Partial Import will not remove the deleted relationship in the target instance.
Workaround: None. |
AC-1815 | Summary: For PostgreSQL, 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 up the server. |
AC-1811 | Summary: Delta Export will not fetch any data if the Characteristic relationship is added.
Workaround: Add the relation in forward way instead of reverse way. |
AC-1780 | Summary: Plan Fragment record cannot be added to the Product repository using the ProductHasCustomPlanFragment relationship if you have not created the action records in the ACTION repository and if you have not provided a value for the ACTIONID field.
Workaround: Provide a valid and existing value for the relationship attribute ACTIONID. |
AC-1737 | Summary: Fulfillment Catalog allowed the display name of an enterprise to contain multi-byte characters. This will cause an issue because Fulfillment Catalog uses the same for Enterprise Internal Name as well, which will not be supported by MDM as MDM only supports ASCII.
Workaround: Do not use multi-byte characters for the display name of the enterprise. |
AC-1684 | Summary: Removing milestones and adding SLA to plan fragment from Hierarchy Management gives
pf_relationship.
Workaround: Delete the PLANFRAGMENT record and re-create with SLA data only. |
AC-1647 | Summary: Uploading image is not working on both Hierarchy Management and MDM screen.
Workaround: Save and Process the record. Once the record is processed then the image/document link starts working. The image/document link still works even if the same has been changed. |
AC-1221 | Summary: Applying invalid project tag name in a relationship throws an error upon validation for its reverse relationship.
Workaround: None. |
AC-369 | Summary: Graphical Edit screen allows to modify the record though
<access mode="view_record">.
Workaround: None. |