This topic summarizes the history of significant changes in TIBCO® Artifact Management Server release 1.4.3, including features, enhancements, and corrections.
This release contains no new features. Including the issues resolved as shown below, the AMS release number was updated to align with TIBCO® Streaming release 10.4.3.
None.
None.
None.
None.
This section describes resolved limitations in the current release. Each item includes a tracking number and a description.
| Fixed in 1.4.3 | |
|---|---|
| Number | Resolution |
| SB‑46254 | The artifact publishing service no longer fails when publishing an artifact that was previously deleted. |
| SB‑46187 | Deploying artifacts could fail when the artifacts contained empty metadata. This was fixed. |
| SB‑46117 | This release corrects an issue that caused AMS to use the default deployment descriptor instead of a user-selected one. |
| SB‑46091 | Invalid JSON on a REST API request would result in an HTTP response status code of 500 without any content or error message in the response body. AMS now detects invalid JSON and returns a code of 400. The error message in the response body indicates a JSON error with a description of the error's cause. |
| SB‑45750 | In some cases, the web client would not refresh when added and committed artifacts were approved. This erroneously displayed two different records for the same artifact. This was resolved. |