Prev |  | Next

## New and Noteworthy in AMS 1.3.0

This topic summarizes the history of significant changes in TIBCO® Artifact Management Server release 1.3.0, including features, enhancements, and corrections.

## New Features

TIBCO AMS 1.3.0 adds the following updates and new features:

Source Control Management (SCM) Systems Now Supported

  AMS now natively supports artifact storage in Subversion and Git repositories. See AMS-SCM Integration more information.

Importing Decision Table Schemas Now Supported

  AMS now provides the ability to import a StreamBase Decision Table operator's schema to populate decision table artifacts in the AMS web client. See Adding a New Artifact into a Project for details.

Schema Editing Now Supported

  AMS now supports a new editor for business rule management in StreamBase decision table artifacts. See Managing Rules Using the Schema Editor for details.

Binary Artifact Content Can Now Be Filtered

  The list project artifacts and fetch artifact REST endpoints now have query parameters that control whether artifact content and/or metadata is returned by the AMS server (filtering is useful for not displaying base64-encoded content of binary artifacts, for example).

AMS Now Configurable to Restrict Service Names in Artifacts Deployments

  The AMS configuration file now has a `DeploymentServiceNames.filter` property used to restrict the StreamBase service names artifacts get deployed to. See AMS Configuration File Reference for more information.

Hiding Projects Functionality Now Added to Project Menu

  The new project menu option hides the project and its artifacts from the Workspace view. See Project Menu for more information.

Artifact of Plain Text Type Now Supported

  AMS now supports generic artifacts of plain text type, using the .txt extension.

Changes Now Comparable When Replacing Artifacts with Different Version

  When replacing an artifact using the Replace with > Upload File menu option, AMS displays the differences between the two files, prior to replacement.

New Cipher Command

  The ams-server --cipher command enciphers clear text information such as passwords, in the `ams.conf` file.

## Changes in Functionality

Functionality changes beyond those described above are shown here.

AMS Now Base64-encodes Only Imported Binary Artifacts

  Artifact content is now only Base64 encoded when the UTF-8 decoding fails. CSV files, for example, could potentially be edited with the AMS's simple text editor when they are not Base64-encoded.

Additional Flexibility Added for Artifact Names

  Multiple (as well as leading) dots are now allowed in non-TIBCO BusinessEvents artifact names. For artifacts added from BusinessEvents, the current naming restrictions remain in place (which AMS displays when encountered when adding artifacts).

Error Notification Enhanced to Include Details

  If the web client encounters an error, the resulting error dialog now includes a Details pane that will show additional information, with the option to copy this information to the clipboard.

REST API Enhanced

  Instead of automatically resulting in success when a Checked Out Artifact ID does not exist, the end-point now supports the following query argument: ignoreAlreadyDeletedArtifact.

## Deprecated Features

No features are deprecated in this release.

## Migration and Compatibility

There are no known migration issues when upgrading from AMS 1.x to AMS 1.3.0.

## Known Limitations

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.

Currently there are no known limitations.

## Closed Issues

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.3.0
Number | Resolution
--- | ---
SB‑43882 | The REST API was updated to fix an issue that caused PUT/artifacts/checkout to fail if the `projectId` property in the request was in the UUID format (with dashes).
SB‑42357 | This release fixes an issue that prevented the User Management page from displaying a current user's enabled/disabled state in some cases.
SB‑42355 | An issue prevented AMS from refreshing the artifact's lock state. This was fixed.

Prev | Up | Next
| Home |