Release 7.0 - Altenalptürm
There are plenty of new features and changes in the Altenalptürm release. One of the main features that we introduced is the concept of legal entities. Those entities can be part of the organizational unit structure and can be used to delegate and assign rights not only in the context of a user or a role, but also in the context of this legal entity.
CoreOne Admin UI
All the libraries and dependencies have been updated to the latest versions.
All the UI masks have been made aware of the new organizational unit types, especially the legal entities.
BREAKING CHANGE: Employments used to have an active flag. This has been extended to support additional states and we therefore removed the
Employment.Active
field from the String Expression Designer. If you have used this in the past, you can now use theEmployment.EmploymentState.Id
orEmployment.EmploymentState.Name
field instead.The datatype
date
can now be extended with a configuration where you can specify min and max ranges. This is especially useful if you are creating an attribute to be used as a birthday for example.
CoreOne Application API V2
The handling of drop down values has been improved.
Access to specific API endpoints can now be restricted with API scopes. This allows you to restrict certain clients from accessing part of the API regardless of the user rights.
CoreOne Authentication Services
All the libraries and dependencies have been updated to the latest versions.
There is a new flag on the application that enables you to restrict access to an application for users that have no role claim associated for that given application
You now can configure default role and resource assignments on the application. Upon the first access of a user to that application, the configured roles and resources will automatically assigned to them. This is a new way of assigning default rights to a user. You can also change this configuration later on and it will apply to all users that have used the given application.
You now can override the Welcome page of the Authentication Service or configure a static redirect
All check boxes are now focusable by a tab hit and therefore meet the WCAG standards
The fingerprint created for the clients device has been optimized to be more reliant and not trigger a
new device used
event if the minor version of the browser has changed
CoreOne Application Services
All the libraries and dependencies have been updated to the latest versions.
The organizational unit type has been extended. Besides the ability to group and organize different organizational units, you now also have the option to categorize them into legal entities, regular organizational unit and into positions.
We have introduced a delegation context for resource assignments. You now can specify in which context a resource will be assigned to a user. This can be in the context of the user, in the context of a different user or in the context of an organizational unit or legal entity. The same support was added to the CoreOne Authentication Service so that those context values can be deployed with the token.
There is a new event handler that allows you to execute a Next-Gen Workflow as a event handler
BREAKING CHANGE: There is a new template
\Templates\Parts\AdminUiLink.part
which hast to be adjusted with Url to AdminUi. It is used in approval mails.BREAKING CHANGE: There is a different serialization of DateTime in the templates. So old one was
<xsl:value-of select="SomeDateProperty/DateTime/DateString" />
New one is<xsl:value-of select="SomeDateProperty/DateTime/Local/DateString" />
or<xsl:value-of select="SomeDateProperty/DateTime/Utc/DateString" />
depending on if time should be in local timezone or in UTC.The assignment state delete pending of not yet valid resource assignments doesn't block the deprovisioning of identities and resource assignments anymore.
To prevent unexpected deprovisioning of identites it makes sense to disable the deprovision tasks feature for identites before an update to this version.
CoreOne High Availability
BREAKING CHANGE: If you run your environment in a high availability setup you and are planning on using the Next-Gen Workflows, you will need to provide a Redis and a RabbitMQ Cluster.
CoreOne Database Service
The
assembly_assembly
data table used to contain all the application assemblies used to execute the application service. This allowed customers to simply update the database and restart all application services in order to update the whole installation. Because this table was causing synchronization issues when hosted in a cluster we moved this data to file system. This means that now all the application services need to be updated with the installer.
CoreOne Self Service Management Portal
All the libraries and dependencies have been updated to the latest versions.
The configuration file is now stored as an encrypted configuration and can only be read and changed when in possession of the local machine key. All existing configurations will be encrypted automatically.
BREAKING CHANGE: The files to override the
footer
and theheader logo
have change toC:\ProgramData\itsense\Templates\SelfService\Features\Shared\Layout\_Footer.cshtml
C:\ProgramData\itsense\Templates\SelfService\Features\Shared\Layout\_Logo.cshtml
There is a new menu item that allows you to manage representatives and representative relationships
There is a new menu item that allows you to manage companies, their representatives and representative relationships
BREAKING CHANGE: There is a new application configuration file that lets you easily change the colour theme of the portal among other settings
The help and contact page have been merged to one page. It’s no longer possible to define help page URLs. Instead you now can simply override the entire page and add the content that is most suitable for your use case.
CoreOne SAP System Connector
BREAKING CHANGE: The handling of end dates have been corrected. An end date of 31.21.2021 in SAP did result in an valid to of 31.12.2021 00:00:00 in the CoreOne Suite and therefore the entry was terminated to early. We have fixed this so that the same SAP end date will result in an valid to of 31.21.2021 23:59:59.
This can lead to changes in already assigned role and resource assignments. Make sure to follow the following guide to detect any unwanted changes: https://itsense.atlassian.net/wiki/spaces/IKB/pages/1385267260
CoreOne Universal Importer
BREAKING CHANGE: The
is_position
flag of an organizational unit has been moved to the organizational unit type where there are now three different types: legal entity, organizational unit and position.BREAKING CHANGE: The
active
flag of an organizational unit has been moved to an organizational unit state where there are now four different states: active, inactive, deleted, activation pendingBREAKING CHANGE: The
active
flag of an employment has been moved to an employment state where there are now different states: active, inactive, activation pendingBREAKING CHANGE: The import will now compare the the source value to the serialized value and no longer to the used value. This might trigger your import threshold after the update once.
You have to account for those changes in your import configuration. Instead of mapping the is_position
property, you have to account for it in the organization_unit_type_id
field. Instead of setting active to true, you you have to set the state_id
to 1 and instead of setting active to false, you have to set the state_id
to 2. There are checks that will be performed upon the execution, so you will be notified if you missed any of those changes.
CoreOne Legacy Workflow Services
BREAKING CHANGE: The
is_position
flag of an organizational unit has been moved to the organizational unit type where there are now three different types: legal entity, organizational unit and position.BREAKING CHANGE: The
active
flag of an organizational unit has been moved to an organizational unit state where there are now four different states: active, inactive, deleted, activation pendingBREAKING CHANGE: The
active
flag of an employment has been moved to an employment state where there are now different states: active, inactive, activation pendingIMPORTANT CHANGE: We are starting to migrate all Workflows from the Microsoft .NET Workflow Foundation to a new Workflow Engine
All existing workflows are still available and will be supported in the upcoming releases.
New workflows will be handled with the new Workflow Engine that enables you to perform even more actions like awaiting user feedback and more.
The new workflow designer is now web-based which allows you to configure those workflows conveniently from a browser.
CoreOne Next-Gen Workflow Services
This service is completely new and is used to host the Next-Gen Workflows
CoreOne Next-Gen Workflow Administration Service
This service is completely new and is used to administrate all Next-Gen Workflows
© ITSENSE AG. Alle Rechte vorbehalten. ITSENSE und CoreOne sind eingetragene Marken der ITSENSE AG.