June 2021 (21.0.7832)

Version 21.0.7928


June 2021 (21.0.7832)

Version 21.0.7928


Major Features

Added

  • Added support for Single Sign On.
  • User Management and Roles, including the ability to reset the admin password using the embedded web server.
  • PostgreSQL is now supported as a backend Application Database.
  • Audit Logs
  • The Cleanup Options now support the ability to archive to Amazon S3.
  • The cleanup routine now ensures that the Application Logs truncate after 100,000 records by default.
  • Added a new top level Settings page.

Changed

Admin API

Added

  • Added an export API Action for exporting arcflows.

Changed

  • Renamed the downloadFile API Action to receiveFile.
  • Changed the ConnectorId input to the certificates API Resource to be ConnectorIds since it accepts a comma separated list of ConnectorIds.
  • Replaced the importProfiles API Action with import.
  • Deprecated the Subfolder input to the files API in favor. A Subfolder header on messages should be used instead.
  • Removed the DeleteTransactions input to the archiveLogs API Action. The transactions API Resource may be used with an appropriate OData filter to accomplish the same result.
  • Removed the deleteLogs API Action. A DELETE request to the logs API Resource may be used instead.
  • Removed the deleteTransactions API Action. A DELETE request to the transactions API Resource may be used instead.
  • Removed the ExpirationDays property in the certificates API Resource.

Removed

  • Removed the refreshTransactions API Action.
  • Removed the restartFile API Action.

Connectors

Added

  • Added a PostgreSQL Connector
  • Added the ability to send the input file as binary data on the request in the REST Connector.
  • Added a Max Failed Records setting in the Advanced tab for Database Connectors in order to allow the connector to ignore a configurable number of insert failures without reporting an error.
  • The EmailReceive Connector now supports OAuth 2.0 as an authentication mechanism.

Changed

  • As mentioned in the Upgrade guide, file based connectors (like File, SFTP, etc.) now use a Subfolder header on messages to denote path information instead of subfolders of the Send or Receive folders.
  • The FTP and SFTP Connectors are now in the MFT category.
  • All connectors now support Log Subfolder Scheme and Sent Folder Scheme settings in order to prevent performance issues due to the accumulation of a large number of files or folders in a single folder.
  • The _message special item is now available in the After Receive event.
  • File content that is accessed from the After Receive event in connectors is now loaded from a temporary location on disk, and files will still be written to the Receive directory on disk even if the working copy is moved elsewhere. It is recommended to use the File Connector for cases like this going forward.
  • The XMLMap Connector will now enable the “Show Attributes” toggle automatically if attribute mappings are detected.
  • The CData Connector now supports v21 drivers instead of v20 drivers.
  • With the addition of the BaseURL setting, the PublicDomain setting is now deprecated.
  • The S3 Connector now supports connecting to other S3-like services, so the Wasabi Connector is now deprecated.
  • Connectors with more than one output folder now have a Receive folder on disk for each.
  • Removed the OverwriteLocal setting for file based connectors. A File Connector should be used instead.
  • The CData PostgreSQL driver now ships with the application instead of the PgSQL driver.
  • The API, CData, and Database Connectors now require a license for CData drivers in order to function. In cases where an individual connector exists for the data source, that connector may be used instead. For example, if the Salesforce driver is used in the CData Connector, it would require a license for the driver, but the Salesforce Connector would not. Please reach out to sales@arcesb.com to inquire about obtaining a license if necessary.

Miscellaneous

Added

  • Added an InstanceId column to all log tables in Application Database. This is useful in HA environments in order to determine which instance in the cluster produced the log entry.

Changed