What's new - iCIS On-Prem v4.4.1

This topic provides an overview of the more significant changes in the "on-premise" release of iCore Integration Suite v4.4.1.

Workflows

Support for creating Web API definitions targeting ASP.NET Core 2.1, NSwag 13, and Open API v3

Web API definitions can now be created for different target host versions:

• Version 1 (Legacy) is the old version, which uses ASP.NET Core 2.0 and NSwag 11. We do not recommend creating new Web API definitions targeting this version.
• Version 2 (Latest) is the new (default) version, which uses ASP.NET Core 2.1 and NSwag 11. This version supports generation of Open API v3 definitions.

You can upgrade Web APIs built on the old versions to the new versions, but you need to make manual changes to the Web API code or they will not function properly.

For more information, see:

• Web API overview

Support for client security configuration in SOAP web service workflow activities

Workflow activities for consuming SOAP web services now support client security configuration using the new argument Credentials. A new Workflow activity "Create SOAP Client Security Configuration" for creating the security configuration is available.

For more information, see:

• Web services
• Create SOAP Client Security Configuration

Support for HTTPS hosting of WebAPI definitions

The WebAPI host now supports HTTPS hosting which can be configured in the "Execute Web API Definition" Workflow activity.

For more information, see:

• Execute Web API definition

Authentication with Azure AD

Simplified login configuration for Azure AD users

It is now possible for Azure AD users to log in to the Administrator site and iCore system(s) with only an Authorization provider configured on the site/system. Previously, two provider configurations were required (OIDC provider and Authorization provider). When Azure AD is used as Authorization provider, the authentication with OAuth 2.0 is performed automatically before authorization in Azure AD.

For more information, see:

• Authorization provider configuration

Script

Support for file and Base64 certificates in Script objects

Script objects are no longer limited to using certificates installed in the Windows certificate store. You can now also use the following methods to set certificates from a file or from a Base64 string:

• SetCertificateFromFile
• SetCertificateFromBase64String

As a consequence, the existing method SetCertificate has been renamed to SetCertificateFromStore.

For more information, see:

• HTTP Client Object
• SMTP Object
• POP3 Object

Web service client

Support for OpenAPI Specification v3.0.0

Web service clients created with REST now support OpenAPI Specification v3.0.0.

Deprecated and removed tools

iCoreTrig.exe

The 'iCoreTrig.exe' application is no longer available.

Adapterflow activities

• DB2 activities are no longer available.
• TIBCO EMS activities are no longer available.

PowerShell cmdlets

• Get-iCorePaths cmdlet is deprecated and will be removed in future versions of iCore Integration Suite.
• Get-iCoreEntity cmdlet for retrieving tracking entity types (Node, Job, Envent and LogEntry) is deprecated and will be removed in future versions of iCore Integration Suite. - Some functionality in Get-iCoreEntity cmdlet is deprecated and will be removed in future versions of iCore Integration Suite. It will no longer be possible to retrieve tracking entities (Nodes, Jobs, Events or Log entries).
• Switch ReturnEntity on cmdlet Get-ExportableiCoreEntity is deprecated and will be removed in future versions of iCore Integration Suite.