Release notes

v2021-05-14

Improvements

• UI decreased technical debt

• Decreased technical debt in all our environments (upgraded spring boot to latest version)

• Included new filter (on source system) during activation of the tenant

Bugs

• solved bug with list of Integration flows visible on deployment screens

v2021-04-30

Improvements

• UI decrease technical debt

• alerts improvements

• add response message to API when secret not found

• UI - Redirect to flow history with proper filter after clicking on number on dashboard

Bugs

• solve bug with logging across microservices

• solve bug with version list during deployment in portal

• solve bug with unexpected technical warnings on UI

v2021-04-02

Improvements

• Portal improvements
  • fix a few bugs
  • decreased technical debt

Features

• Automation of Tenant activation/deactivation service

Bug fixes

• solved bug with permissions on deployments (for reader role)

• return proper error message when secret not found

v2021-03-19

Improvements

• Portal improvements
  • fix a few bugs
  • decreased technical debt

Bug fixes

• solved bug related empty eventTypeVersion during deploy operation for MESSAGE_ENDPOINT trigger

v2021-03-05

Improvements

• Portal improvements
  • fix a few bugs
  • decreased technical debt

Features

• Add new field with deployment description

Bug fixes

• solved bug related to sending messages to Message Hub

v2021-02-19

Improvements

• UI improvements
• Add information about used configuration (deploymentId) to flow history

v2021-02-05

Improvements

• Add additional alerts for environments
• UI improvements
• Enable possibility to create multiple deployment for one integration flow for single tenant

v2021-01-22

Improvements

• Upgraded AKS version to 1.19.3
• Created alerts for environments
• Portal improvements
  • changed layout of the navigation menu
  • decreased technical debt
• Added version to portal

Features - Added support for multiple deployments during create and delete subscriptions in MH

Bug fixes - Added preventing execution of steps without runId

v2020-12-11

Improvements - Updated Message Hub Connector SDK Java to version 3.2 - Added storing fields TenantId and IntegrationFlowTenantId as exchange properties instead of headers - Portal - added spinner and block deploy button during deploy operation

Bug fixes - Solved problem with OOM in GMP

v2020-11-27

Improvements - Added validation to check if tenant exists during deploy operation (and save configuration)

Features - Portal: - Applied new design for view details of existing deployment screen - Applied new design and single tenant view on modify configuration - Limit the history for Integration Flows created by and for the current tenant (in single tenant view) - Added support for multiple deployments for HTTP_ENDPOINT trigger

v2020-11-13

Improvements - Added size limits to message headers - Updated Azure Kubernetes Service (AKS) to version 1.18.8

Features - Portal - Applied new design and single tenant view on deploy operation

Bug fixes - Removed case insensitivness for events during processing message from Message Hub - Fixed issue with corrupted data after ifMatch error

v2020-10-16

Improvements - Upgraded Application Insights to Preview.7

Features - Portal - Limited deployments list for Integration Flows to only those created by tenant (in single tenant view) - Applied new design on deployment details screen - Added limits of the message size for HTTP_ENDPOINT trigger

Bug fixes - Portal - Fixed issue with back button not working properly - Fixed issue with the invitations not being sent

v2020-10-02

Improvements - Update Azure Kubernetes Service (AKS) to version 1.17.9

Features - Portal - Applied new design and aligned with permissions on create secret - Applied new design and aligned with permission on tenant and secret list - Applied new design and aligned with permissions on secret version list - Unified list of deployments for single and multitenant views - Added validation that only admin tenant can have multitenant role - Added support for large message for HTTP_ENDPOINT trigger - Limited access to Integration Flows to only those created by tenant (in single tenant view)

Bug fixes - Fixed confirmation message for delete secret - Solved issue with OOM in Flow history

v2020-09-04

Improvements

• Updated Azure Kubernetes Service (AKS) to version 1.16.10

Features

• Portal

  • Adjusted dashboards for single tenant view
  • Applied new design on deployment list
  • Added filters panel on run lists in flow history
  • Applied new design on list of steps in flow history
  • Applied new design on step details in flow history

• Added support for event documents from message Hub

Bug fixes

• Fixed bug with timezone in user and access management

v2020-07-24

Improvements

• Changed time outs of the message processing from 20 seconds to 5 minutes
• Added paging on step list in flow history

Features

• Portal:

  • Applied new design on list of runs in flow history

Bug fixes

• Fixed issue with messages not being consumed from the Message Hub topic
• Added missing versioning in a content type header

v1.2

Features

User and access management:

• Introduced three roles:

ROLE: Owner

When you're assigned the role of Owner you have full access to the application. You can:

• manage the users and their roles.
• manage Integration Flow versions. (Design, test and publish new Integration Flow versions)
• manage deployments of Integration Flows. (Un/Deploy Integration Flow versions for tenant, maintain tenant-specific configuration for Integration Flows and maintain mapping tables)
• monitor Integration Flows,(access to the data on the number of erroneous runs of Integration Flows in Flow History and viewing metrics and alerts to these numbers)
• review the exceptions that were thrown and captured in Flow History for Integration Flows.
• read Flow History content
• manage of tenant secrets (client certificates) that are used in Integration Flows

ROLE: Contributor

When you're assigned the role of Contributor, you are able to manage Integration Flow versions. This means you can:

• design, test and publish new Integration Flow versions
• manage deployments for Integration Flows
• you can (un)deploy Integration Flow versions for tenant, maintain tenant-specific configuration for Integration Flows and maintain mapping tables
• monitor Integration Flows,(access to the data on the number of erroneous runs of Integration Flows in Flow History and viewing metrics and alerts to these numbers)
• review the exceptions that were thrown and captured in Flow History for Integration Flows
• read Flow History content
• manage of tenant secrets (client certificates) that are used in Integration Flows

ROLE: Reader

When the role of Reader is assigned to you, you are able to:

• check if all U4IK portal functionality is working, e.g. after deploying a new version of the portal

• view Integration Flow versions, Deployments, tenant secrets, Flow History content and dashboard metrics and alerts for Flow History and tenant secrets

• Add UI to manage tenants/users/user roles

  • Deactivate/Reactivate user
  • Change user roles (the user cannot modify himself)
  • Show tenant users
  • Send invitations
  • Approve/Reject access request
  • Deactivate/Reactivate tenant
  • Activate new tenant

Sensitive data in message body

To protect sensitive data in message, user can decide to not store message body in Integration Kit Flow history (new flag to not store message body for specified Integration Flow version). Data is only processed by GMP but users can not have access to the body of the message.

Message Hub Integration

• Create new trigger type MESSAGE_ENDPOINT
• Manage Message Hub subscription via U4IK portal
• Consume message from the Message Hub and process them in IK
• Send messages from external world to Message Hub

v1.1

Features

• Integration Flow management: View available Integration Flows with corresponding versions and upload a new version for an Integration Flow in U4IK portal
• Support for content enrichment functions: To make transformations that are applied within an Integration Flow reusable and generic, Mapping Tables can be applied via Content Enrichment functions. Each Mapping Table must be designed when creating the Integration Flow version. E.g. name, key columns and value columns must be defined with specific configuration property types so that @deployment time the values in rows can be validated. Mapping Table definitions can be applied for different use cases:
• Map single key to single value
• Map single key to multiple values
• Map combination of keys to a single value
• Map combination of keys to multiple values
• Map single key to list of values
• Map combination of keys to list of values
• Introduction of triggers: When the Integration Flow version is deployed for a tenant, trigger configuration can be filled in. The trigger type and corresponding security mechanism(s) must be configured. For now U4IK supports trigger type "HTTP_ENDPOINT" for synchronous Integration Flows. This trigger type supports following security mechanisms:

Security mechanisms	Deployment time
OIDC_AUTH	OIDC_AUTH MUST be used, IP_FILTER optional
ANY	One of the options is required (IP_FILTER satisfies), so cannot be public
ANY_AUTH	One of the AUTH options is required (IP_FILTER does not satisfy), so cannot be public
BASIC_AUTH, IP_FILTER	Both MUST be used, OIDC_AUTH cannot be used combined with BASIC_AUTH
	nothing required, all optional. Can be public endpoint

• Time-To-Live for Flow History data

v1.0

Initial release of Unit4 Integration Kit. U4IK v1.0 will be available as preview environment (ACC) and as production environment (PROD) in CSP in Azure. In an early adopter program for Healthcare LoB, a few customers will go in production with two synchronous Integration Flows.

Features

• Generic Message Processort (GMP): The scalable processing engine of U4IK is ready for synchronous request/response pattern.
• Integration Flow Management (IFM): Integration Flow versions can be designed in a text editor or an external environment that supports Camel-Spring XML format and can be published to the Integration Flow repository via the IntegrationFlowManagement API. An Integration Flow version must be delivered as a compressed zip file containing:
• Camel-Spring XML file which contains the routes of the Integration Flow
• Separate configuration metadata file containing configuration property and mapping table definitions
• All supporting files used in the Integration Flow (e.g. XSLTs, XSDs)
• U4IK Portal:
• Tenant Context Management (TCM): An Integration Flow version can be deployed for a tenant via U4IK portal, where the corresponding tenant-specific configuration values can be set during deployment. Azure API Management will be provisioned with tenant-specific secured http endpoint(s) for synchronous Integration Flows (request/response pattern). Integration Flows can be exposed as a resource to enable serverless integration logic for applications
• Tenant Secret Management (TSM): Client certificates can be registered as secrets on a tenant level, where each secret has to be provided with a corresponding unique alias for that tenant.
• Flow History Repository (FHR): For the purpose of proof of delivery and error tracking, runs of Integration Flows and all their corresponding steps are stored in so-called Flow History. All steps of an Integration Flow run can be viewed via U4IK portal.
• Domain events from IFM, TCM, TSM and FHR are stored in event stores. These events can later be forwarded to other event collectors.
• U4IK is provided with a role and permission scheme. Authentication via OpenID Connect and Unit4 Identity Services for both human involved and no human involved flows. Access tokens provided by U4IDS can be upgraded to contain the defined access rights (user role claims). Each role has predefined permissions on a per microservice level which are checked by every downstream microservice.
• Unit4’s Assigned Support Team has access to U4IK portal to be able to be able to offer “Integration Flows as a Service” to tenants. Unit4’s Assigned Support Team can access Flow History data (which may contain PII dependent on Integration Flow) for the purpose of sample-wise verification of successful runs, error-tracking in case of exceptions and to provide proof of delivery on Customer request. All these actions will be logged on a user level.