Skip to main content

What's New v4.0

This topic provides an overview of the more important changes in iCore Integration Suite v4.00.

Updated technical requirements

The technical requirements for iCIS has changed with the release of v4.00:

  • iCIS now requires MS SQL Server 2012 or later.
  • The Web Administrator client requires Internet Explorer 11 or later.

For more information, refer to the complete technical requirements for iCIS available on the iCore website.

Secure data transport via AS2

iCore Integration Suite now supports communication using the AS2 protocol. If you want to use AS2 functionality, we recommend using the AS2 Communication package which can be downloaded from the iCore member pages. The package includes Components based on the new AS2 Workflow activities. Note that if you want to be able to receive incoming AS2 messages and AS2 MDNs, you also need to install and run the new iCore AS2 Server Application.

Data protection

The purpose of Data protection is to limit access to – and protect – sensitive attribute data in an iCore system. Selected Node/Partner/Setting attributes that contain sensitive data are labelled as protected by setting a property on the attribute called Protected to True. Once this is done, the protected entity can only be viewed and modified by iCore Users with the appropriate authorization.

There is also a second layer of security which means that protected values are stored in encrypted form in the iCore database. Exporting protected values requires that the export file is also encrypted.

When installing iCIS v4.00 (or upgrading to this version), a new User called SecAdm is added to the iCore system. SecAdm is the security User that is used to control what restricted operations other Users are allowed to perform (i.e. viewing and modifying protected entities). The SecAdm is provided with a default password, and we strongly recommend changing this password as soon as your system has been updated to v4.00.

For more information, see Data protection.

Publishing and consuming REST APIs


This is a preview release of the feature and we do not guarantee backwards compatibility in future versions of iCIS. If you create solutions based on the feature, you may need to modify them manually when upgrading iCIS.

You can use the new Web API entity to publish REST APIs. Web APIs are defined in the Web API editor, and can then be hosted in a Workflow using the Execute Web API definition activity. By default, the Web API includes functionality for publishing a description based on the OpenAPI specification (formerly known as Swagger).

The Web service client entity (formerly Web service definition) has been updated to support both SOAP and REST based web services. For import of REST APIs, iCIS supports the OpenAPI specification.


Some of the changes listed below will affect backwards compatibility and may require actions. Note that this can also be true for some service packs that contain new functionality.

For more information, see Backwards Compatibility.


RegExp Object

You can now choose whether you want to use .NET or ATL syntax for regular expressions. Which syntax format is used is decided by the Syntax parameter on the StartMatch method:

  • Set the parameter to Standard to use .NET syntax (this is the default setting).
  • Set the parameter to Legacy to use ATL syntax.

If you set the parameter to Legacy, note that the expression is translated into .NET syntax at runtime.

New managed implementations

  • RegExp Object
  • WSMQ Message Object
  • WSMQ Queue Object

With the release of iCIS v4.00, native implementation of rewritten Script functionality is no longer included in the installation and cannot be used for fail-back.

Obsolete Scripts, functions and objects

  • Cryptography objects
  • Mail object / Mail Message Object, methods:
    • Encrypt
    • Decrypt

FTP Server Object

  • A new property (ConcurrentConnections) specifies the number of concurrent connections opened to the server when receiving files.

Support for UUEncoding
Functions for encoding and decoding using UUEncode have been added. The available functions are:

  • UUEncode
  • UUDecode
  • CheckUUEncodingMarkers


SFTP activities

  • SFTP Reader: Property 'Upload block size' has been removed.
  • SFTP Writer: Property 'Download block size' has been removed.


Clean-up Tracking

The activity has been updated resulting in significantly improved performance and new tuning options.


If you are using the activity in existing Workflows, you need to edit the new activity arguments. If you are using the Daily maintenance functionality in the Common package – download and install the latest version of the package.

Create FTP Connection Configuration activity

A new argument (Concurrent connections), specifies the number of concurrent connections opened to the server when receiving files.

AS2 activities

New activites for working with AS2 (Applicability Statement 2) have been added. Note that the activities are not added to the toolbox in the Workflow Designer by default, but must be added manually. We recommend using the AS2 communication package (see "Secure data transport via AS2" below), which can be downloaded from iCore Tech.

Web service definition The name of this entity has been changed to Web service client.


The type iCore.Public.Entities.IWebServiceDefinition has been renamed to iCore.Public.Entities.IWebServiceClient. This is a breaking change which may require that you manually update Workflows or Adapterflows that use this type in code expressions.


Attached machinesA new entity that provides information about all computers that are attached to an iCore system. For more information, see Attached machines.

See Also

Backwards compatibility