AMS now natively supports artifact storage in Subversion and Git repositories. See AMS Integration with Source Control Management Systems more information.

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.

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

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).

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

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

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

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

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

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.

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).

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.

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.