This topic summarizes the history of significant changes in TIBCO® Artifact Management Server releases 1.0.1, including features, enhancements, and corrections.
TIBCO AMS 1.0.1 added the following updates and new features:
AMS now includes the option to add additional deployment descriptors via the Manage Deployment Descriptors menu.
AMS now supports canceling pending deployments via the > menu.
Functionality was changed as described in the new enhancements described in the previous section. This guide was updated to address these enhancements.
No features are deprecated in this release.
There are no known migration issues when upgrading from AMS 1.0 to AMS 1.0.1.
This section describes known limitations in the current release of the TIBCO Artifact Management Server. Each item includes a tracking number, description, and whenever possible, one or more workarounds.
| SB‑30256 | Cannot deploy rules using service name. | |
| Description | An issue prevents AMS from deploying decision table rules to a running decision table EventFlow module, when configured to push rules via a StreamBase Server's service name. | |
| Workaround | Deploy rules using the StreamBase Server's URI as described in Deploying Artifacts. | |
| SB‑30255 | Cannot deploy rules to StreamBase release 7.6.6. | |
| Description | An issue prevents AMS from deploying decision table rules to a decision table EventFlow module running StreamBase release 7.6.6. | |
| Workaround | From a running decision table EventFlow module in StreamBase, "pull" decision table rules in from AMS. See the StreamBase Authoring Guide per the TIBCO Streaming® documentation for more information. | |
| SB‑29540 | Copying and pasting rules not supported. | |
| Description | Using the keyboard combination Ctrl+C and Ctrl+V does not copy and paste decision table rules from corresponding table cells. | |
| Workaround | None. | |
This section describes resolved limitations in the current release of the TIBCO Artifact Management Server. Each item includes a tracking number and a description.
| Fixed in 1.0.1 | |
|---|---|
| Number | Resolution |
| SB‑30050 | In scenarios where a deployment was scheduled after the AMS server was restarted, the deployment would not execute. The AMS server now reschedules any deployments that were pending at the time of a server restart. |
| SB‑30120 | When adding columns in release 1.0, column names had to be unique in the decision table. Now, column names can be the same as long as one column name is assigned to an action column and the other to a condition column. |