The following enhancements and fixes are included in this release. 

CIC Cockpit Enhancements

This release contains general enhancements and improvements, including infrastructure updates put in place to support future capabilities and development.

OFTP Endpoints

CIC now supports communications over OFTP, a protocol standard used worldwide, especially in Europe in the automobile industry. The addition of OFTP Endpoints can help ease the transition from on-premise solutions to Cleo's CIC Cloud Edition.  For more information, see OFTP Endpoint.

Fixes

Several issues have been addressed and fixed with this current release:

• Fixed an issue where a single message could be processed multiple times resulting in multiple Message Tiles with different Job IDs referring to a single message in CIC Cockpit.
• Fixed an issue where successfully transformed payloads were sent to incorrect Endpoints.
• Fixed an issue where some manually run Data Flows did not properly create or display Jobs in the Jobs list.
• Fixed an issue where a delay would occur when CIC was ensuring uniqueness of filenames during Job processing.
• Fixed an issue where, when some inbound payloads were not transmitted successfully, positive MDNs were still generated and sent back to the senders.
• Fixed an issue where CIC could create trouble tickets that did not contain the Job IDs that caused the issues. These tickets also contained an URL referencing the Job that did not work properly.
• Fixed an issue where a scheduled report would not return the messages or message details corresponding to the filtering criteria contained in the report definition.

CIC Studio/Engine Enhancements

This release contains several minor fixes for recent Production issues and includes infrastructure updates meant to improve general platform stability.

Prevent ticket creation by filtering error codes

Enhancements to REST Connectors and REST WS Consumers can help you prevent ticket generation in CIC Cockpit for certain scenarios in which failed processes don’t necessitate failed jobs. Additional parameters let you specify which HTTP errors codes shouldn't cause a job to fail, thus a ticket not created. See how to Prevent ticket creation in CIC Cockpit through Web Service Consumers and Connectors.

Improved ability for WS Consumer to retrieve HTTP response codes

CIC Studio now makes it easier to access HTTP response codes and messages when working with WS Consumer objects. This can be beneficial when building business logic around a WS Consumer that requires HTTP status codes. See Retrieving HTTP response details with a Web Service Consumer (REST).

Fixes

Several issues have been addressed and fixed with this current release:

• Improved sizing of the Connector Vault Creation Wizard.

• Fixed an issue in which certain parameters used for searching in earlier versions of the Studio Auditor were not available in later versions.

• Added a null check for cases when an authorization server does not return their access_token response with a new refresh token.
• Fixed an issue in which trying to access the MSD365 API via the Connector caused an error
  (InvocationTargetException).
• Fixed an issue in which wrong methods were used being used in cases where an XML Schema had elements or attributes in the same level with the same name but different cases. For example id vs ID.
• Added logic to allow Stored Procedures to run successfully when 'begin tran' and 'commit' are used in the SQL Statement.

CIC Agent Enhancements

The current release is 1.0.17. This release contains general enhancements and improvements, including infrastructure updates put in place to support future capabilities and development.

Multiple CIC Agents on a Single Server

You can install multiple CIC Agents on a single server. This allows you to use Access Points on that single machine for separate tenants, for example, stage and production. See Managing Access Points and Installing, Updating, and Uninstalling CIC Agents.