Known Issues
The following issues exist in this release of TIBCO® Product and Service Catalog powered by TIBCO EBX®.
Key | Summary and Workaround | |||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
PSCEBX-579 |
Summary: When you perform a Delta Publish, the changes made in Plan Fragment for a product bundle are never exported or published. Workaround: None. |
|||||||||||||||
PSCEBX-578 |
Summary: When you perform a Delta Export, the changes made in Plan Fragment for a product bundle are never exported or published. Workaround: None. |
|||||||||||||||
PSCEBX-576 |
Summary: When using Delta Publish, the child record changes are not sent to the published parent file. Currently, this has been handled for the Workaround: None. |
|||||||||||||||
PSCEBX-575 |
Summary: The Delta Publish does not work for the following scenarios:
Workaround: None. |
|||||||||||||||
PSCEBX-559 |
Summary: When deploying through Helm charts, the EMS activation property is not available in the Workaround: None. |
|||||||||||||||
PSCEBX-558 |
Summary: An error is generated when you try to deploy on Google Kubernetes Engine (GKE) through Helm charts. Workaround:
|
|||||||||||||||
PSCEBX-557 |
Summary: Invalid Product record is published and the product.xml file does not contain affinity values or the relationship values with a PlanFragment. Workaround: None. |
|||||||||||||||
PSCEBX-556 |
Summary: You cannot import product records with the Rel_ProductHasPlanFragment(Update/Cease/Cancel/Provide) relationship. Workaround: None. |
|||||||||||||||
PSCEBX-550 |
Summary: The constraint rule "constraintForValidSections" is violated on the UI and does not work as expected. Workaround: None. |
|||||||||||||||
PSCEBX-523 |
Summary: A circular dependency exists in forming parent-child relationships in TIBCO® Product and Service Catalog powered by TIBCO EBX®. For example, product Workaround: None. |
|||||||||||||||
PSCEBX-521 |
Summary: Both records are rejected when importing two different project tag records with the same project tag name. Workaround: None. |
|||||||||||||||
PSCEBX-512 |
Summary: The import records are not rejected when the Affinity (Cancel, Cease, Provide, Update) is not attached to the product records. Workaround: None. |
|||||||||||||||
PSCEBX-500 |
Summary: A single parent file record is expected in the delta publish, which is not published. Workaround: None. |
|||||||||||||||
PSCEBX-460 |
Summary: When a file is imported with an improper CSV name, the required error messages are not displayed on the UI. Workaround: None. |
|||||||||||||||
PSCEBX-459 |
Summary: The Delete Records.csv and Delete Relationships.csv files are not exported along with the Delta Export. Workaround: None. |
|||||||||||||||
PSCEBX-451 |
Summary: When a record is deleted from the repository, no error message is displayed. Workaround: None. |
|||||||||||||||
PSCEBX-450 |
Summary: On the Allowance tab of the UI, when you import a new version of the image and then detach it, the original image is shown as useless and it cannot be reattached. Workaround: None. |
|||||||||||||||
PSCEBX-368 |
Summary: The OPD is not available in TIBCO® Product and Service Catalog powered by TIBCO EBX®. Workaround: None. |
|||||||||||||||
PSCEBX-364 |
Summary: Before performing the Delta export, the user can view the exported results on a web browser page instead of executing the actual export. This is not useful to read a huge record without any search functionality. Workaround: None. |
|||||||||||||||
PSCEBX-363 |
Summary: Partial import feature is missing in TIBCO® Product and Service Catalog powered by TIBCO EBX®. Workaround: None. |
|||||||||||||||
PSCEBX-341 |
Summary: Import of all the records fails if the length of even one record exceeds the value in the maxlength value field. Workaround: Correct the value in the maxlength value field. |
|||||||||||||||
PSCEBX-313 |
Summary: A valid relationship of a record is rejected due to an invalid relationship with another record. Workaround: None. |
|||||||||||||||
PSCEBX-305 |
Summary: While creating or modifying a product, if you attach planfragment in the field from the Affinity Group tab then you cannot add or modify the relationship using the Planfragment Relationship tab and conversely. This issue is for the constraintForNoPlan product rule. The following Relationships are impacted:
Workaround: None. |
|||||||||||||||
PSCEBX-273 |
Summary: Records are created without any validation error even when two different plan fragments are given as attribute values. Workaround: None. |
|||||||||||||||
PSCEBX-256 |
Summary: The condition relationship and condition group attributes are not published along with the rule data. Workaround: None. |
|||||||||||||||
PSCEBX-216 |
Summary: Publish workflow modification is required to remove any dependency of one table publishing on another. Workaround: None. |
|||||||||||||||
PSCEBX-204 |
Summary: Publishing data on JMS topics fails with error if TIBCO Enterprise Message Service™ is restarted during the publishing process. Workaround: Restart the Tomcat Application Server. |
|||||||||||||||
PSCEBX-138 |
Summary: Named versions are not created on performing Full Publish of records. Workaround: None. |