Version 4.5 release notes

Navigation:  Reference chapter >

Version 4.5 release notes

Previous pageReturn to chapter overviewNext page

 

Repository Server

•The repository server can now be deployed as part of a cloud based solution that utilises an OpenID solution such as Identity Server to provide authentication (the previous deployment mode is still available, i.e. can configure the repository server to allow the old way of logging in).

•The "Login" and "Cancel" buttons on the splash form have switched locations to be more in line with other login forms out there.

•Repository server periodically sends an "IsAlive" message to each connected client to ensure that the client is still there, this resolves the issue where clients aren't removed from the server's session list (e.g. client crash, computer going to sleep etc.) preventing that user from logging in again later.

•The repository server now only starts the auto-saving timer as specified in the "AutoSaveInterval" configuration value when it detects a change to a repository. This prevents the continuous serialization of unchanged repositories to the file system.

•The repository server's installer was changed and it will now automatically start the IdiomServer service. This service had to be started manually in previous versions before the Decision Manager could be used for the first time.

 

Formula/UDO Pallet

•Fixed an issue that caused the decision model debugger effective date dialog to be defaulted to 2019-02-23.

•New CreateSubtree operator now allows users to create empty elements/attributes (that don't already exist) downward from a specified context. This operator has two modes "exclude repeating nodes" and "include repeating nodes", the latter of which will create a single instance of each repeating element that doesn't already exist).

Note: Due to this new operator, customized schemas are now embedded into deployed decision model DLL/JAR files when packaged by the decision manager/repository server. If users decide to only generate code and compile by themselves, they will have to include the customized schemas as embedded resources by themselves otherwise certain operators will not function correctly.

•The DecisionModelMetaData operator now has the following additional modes:

oRepository name

oPackage name

oBuild configuration

oChangeset number

Tables

•Table contents with null key values are now reported as a validation error.

•Saving table contents when there is a null key value is no longer allowed.

Decision Server Runtime

•The repository server is now a .NET Core based application that can be run on any OS that supports the same framework.

•The communications framework between the decision manager and repository server has been updated to use the gRPC framework.

•When deployed as part of a cloud based solution, the decision manager will obtain its list of available repository servers from a separate service according to the credentials of the user that logged in.

•Decision Server now includes an IDecisionModelInterrogator interface to allow users to find out information about a decision model (this can be accessed via the IDecisionServer interface, or directly by instantiating implementations of the interface). The default implementation included with Idiom.DecisionServer.dll uses standard .NET assembly loading to interrogate decision models - this means that loaded assemblies stay in memory and cannot be unloaded. A new Idiom.DecisionServer.Interrogation.dll library is also included that uses a 3rd party library (dnlib) to read assemblies without the use of the standard .NET assembly loading feature, hence allowing read assemblies to not linger in memory space once no longer required.

•The repository server installer has been updated, and now also supports parameterized silent installation.

 

Local and Production releases

•Repository pre/post build scripts can now be specified for production release.

•Production release settings are now modified from the Decision Manager client by System Administrator users that do not have a repository open (Tools -> Edit Production Release Settings). This editor is no longer available as a standalone tool deployed with the repository server.

•Added the ability to specify a build configuration during production release. This setting doesn't change the behaviour of the rules in any way, but instead simply allows the user to specify a desired/intended "configuration" that can also be used as a path variable. The list of available build configurations is provided via the repository server and can be customized.

•The LastReleaseDate, ProductionReleaseDate, Build Configuration, Repository, Decision Model and Production Release Version are recorded in the .dll/.jar file details.

 

Repository comparison

•Fixed an exception caused by comparing repositories that have modified formulas used by decisions/decision groups in decision models that contain no changes.

•Fixed an issue causing repository comparison to incorrectly match schemas that have similar nodes instead of against another schema of the same name - this was causing an exception when the comparison UI tried to display the results.

Repository audit history

•Users can now view limited change set history about a repository and its entities from the decision manager (if the history manager is enabled on the repository server). There are limitations on the current implementation due to the separate nature of repositories and the database entries themselves, e.g. deleting a repository then re-importing an older version of it will still have the history of the deleted repository shown with this feature.

•The repository server's audit history manager can now be configured to only retain a maximum number of recorded ReleaseXml column values per repository in the historic image table (older images past the specified number are nullified).

 

C# and Java interface

•[C#] The following information is now compiled (as constant values) into each decision model class under a static subclass called "Information":

oName (Decision Model name)

oRepositoryName

oImpl (package name)

oReleaseDateTime

oProductionReleaseVersion

oBuildConfiguration

oLicenseID

oDecisionManagerVersion

oIsControlDecisionModel

oChangeSetNumber

•[Java] Added the following information to the decision model JAR manifest:

oBuildConfiguration

oLicenseID

oIsControlDecisionModel