Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 15 Next »

This page contains a preview of the upcoming next release.

MySQL migration

  • Please ensure that the customer is migrating from MySQL 5.7 to the latest 8.* There are no breaking changes yet but 8.* is there for a while and offers some features that we may use (CTE, new regex implementation, performance improvements, improved JSON support)

CoreOne Admin UI

  • Each employment type now offers a flag to indicate whether or not users are able to create an employment with that employment type from within the organization management in the CoreOne Self-Service Portal. The default is false, so you might need to check your existing configuration.

  • While assigning a role or resource to various entities, you are now able to select the assignment context.

  • The new API V2 is now part of the health check page

CoreOne Application API V2

  • -

CoreOne Authentication Services

  • If the current LoA only contains an external identity provider, you can now initiate a direct redirect to that provider.

CoreOne Application Services

  • -

CoreOne Database Service

  • New readonly_email column was added on core_identity table. It will be updated for emails that are not configured with rexexp on core_identity_mail_prio_mapping table. For others - it will be updated once the UpdateIdentityTask has run or you can run your own script.

CoreOne Self Service Management Portal

  • It’s now possible to load companies from an external source that are associated with the current user. This allows users to register companies even quicker.

  • The activation of companies can be done depending on the signing rights that are stored in external sources. We currently support single and double signing rights.

CoreOne System Connector

  • A new SCIM System Connector has been implemented that allows you to provision entities using the SCIM standard

  • A new OpenLDAP System Connector has been implemented that allows you to provision entities into a OpenLDAP system

  • The Active Directory System Connector now can provision all account options to Active Directory.

CoreOne Universal Importer

  • BREAKING CHANGE: In the import configurations it’s now possible for data providers who uses credentials (currently LDAP (Active Directory and OpenLDAP) and SQL (MySQL and Oracle)) to get them from a target system. This allows it to omit the username and password from the import configuration so it doesn’t get serialized which in turn makes it safer to store it in the database or to transfer/share it.
    The connection parameter class changed so customer specific import configurations won’t build anymore and have to be adapted, see the box here below.

 Connection parameter changes

The old way with credentials which is still possible:

var connectionParams = new MsSqlConnectionParameters("10.10.11.80", "DEVMasterData", "dev_import", "n&Wt({f9C4x3", false);

The new way without credentials:

var connectionParams = new TargetSystemMsSqlConnectionParameters("10.10.11.80", "DEVMasterData", false, targetSystemId: 2);

Instead of providing the username and password, the new class TargetSystemMsSqlConnectionParameters takes parameters for the id of the target system and username and password will be taken from target system attribute values.

This is not a breaking change for running system as all the old deployed import configurations still work with this change

Be aware: Every parameter in the ConnectionParameter class has now to be called in the constructor when creating the object. Usually this is now done by using the object initializers. Customer projects won't build anymore if this is not adjusted

CoreOne Workflow Services

  • -

Workflow definitions changes:

Workflow Definition

Description

Source

LegalEntity_BeforeUpdate

  • Identifier property should be lowercase

  • company_name attribute can be null and workflow should check against that

  • company_name is a complex object so the code how to extract name was adjusted ( Activity that creates UserInteraction)

  • New fields on CreateInteraction Activity were used (Tag & TaggedIdentifier)

IMS-4939

CoreOne Workflow Administration Service

CoreOne Web Services

  • There is a new attribute tab on the Core Identity which allows you to override imported values.

Legacy Workflows

  • No labels