NX3 Core 3.7.0 Is HERE!

by Main Author

We are happy to share the release of NX3 Core 3.7.0 with you!

This release features the following improvements:

  • Improved versioning concept
  • Visibility of GDPR fields
  • VAT ID Validation
  • Platform Agreements

Improved versioning concept

With Core 3.7, NX3 supports a completely revised and improved versioning concept.

NX3 installations receive a unique version number that transparently reflects any changes also during development phase.

If more details are required, this version number can be resolved to determine the specific version number of each individual NX3 component.

Visibility of GDPR fields

Business objects can contain personal data.

These are now marked transparently in the user interface. In addition, there is a list and export function for all fields that contain personal data.

NX3 thus offers complete transparency of where personal data is stored in the system.

Of course this should not be shown to all users. Therefore, this is an admin function that can be easily activated for the corresponding user groups via authority.

VAT ID Validation

The VAT ID or valued added tax identification number is a unique number to identify a taxpayer (company or person with economic activity) or a non-taxable legal person who is registered for VAT purposes. Each EU country issues its own national identification number

NX3 now offers the possibility to have them automatically checked by the European Commission. This saves time and money. 

Furthermore, a manual check of the VAT ID by our customers’ experts is still possible.


Platform Agreements

Platform agreements in NX3 offer the possibility for a number of pre-formulated contractual terms, between the operator and the BusinessPartner.

Furthermore, the platform agreements offer the possibility to inform the users of a BusinessPartner about privacy agreements to give them the possibility to accept or refuse them. However, contrary to the terms of the contract, the user is allowed to work with the system as usual.

Examples for Platform Agreements are: 

  • Terms and Conditions
  • Privacy agreements
  • Terms of Use

Platform Agreements can be easily configured by our customers’ business users.

When a user logs in, he is informed in a dialog about the currently applicable platform agreements and asked for approval.

Depending on the configuration of the platform agreement Relevant for collaboration, the user has to accept the platform agreement to work with the system or it is not necessary to accept the agreement.


A column in the list of BusinessPartners shows whether the platform agreements have been accepted or not. In addition, there is a filter to restrict the desired amount.

A further highlight is the versioning of platform agreements. For example, if our customers’ general terms and conditions change, they can simply import a new version of the general terms and conditions. All relevant business partners are then automatically requested to confirm these.

This can also be done weeks before they come into force. NX3 ensures the validity from the relevant day.

Major Releases for NX3 Core 3.6 Is Scheduled for 02-2020

Wow! Just noticed that this will happen in 2020…
And here we go – NX3 Core 3.6 is fixed for early 2020!

Build and Tests are running

NX3 Core 3.6 will bring a lot of technical updates e.g. for the underling frameworks (thanks to all of them), optimizations and fixes for client and server platform.

We’ll keep you posted for the final release date!

Major Releases for NX3 Core 3.5.0 Is HERE!

We’re more than proud to inform you that our latest major Release for NX3 Core 3.5.0 is HERE!

Onboarding with different businesspartner roles

Onboarding was only supported for one concrete businesspartner role.  Onboarding of several different business partner roles was complicated and done as concrete implementation in project.

Since now it is possible to define multiple businesspartner roles for onboarding, fully supported by NX3.

Businesspartner lifecylce 2.0

A lifecycle for businesspartner was always part of NX3.  Following illustration describes such a lifecycle.



Since now lifecycles in NX3 are completely redesigned and packed with new features.

And whats really cool is the fact that you do not have to migrate “old” lifecycles to the redesigned feature because they also still work. You can decide from now on.

Transparent lifecycle decisions

It is always possible to see which businesspartner has which level in lifecycle.

Furthermore the history of reached levels in lifecycle is totally transparent.

It is also transparent why you maybe did not reach the next level.

Of course also versioning and audit information are visible.


Versioning of rules for lifecycle changes

Versioning of lifecycles are now supported. That means it is possible to change the gates for a specific level and update these changes. This could be done without restarting the application.

A new version of a lifecycle can be applied to all existing businesspartners in system so that their level is recalculated based on the new lifecycle version.

It is always transparent from which lifecycle version the actual level of a businesspartner was calculated.

Gates are defined by the common DMN Standard.

Simulation and reporting

A new version of a businesspartner lifecycle is not automatically activated so the businesspartners will not be recalculated on every version change.

To get more safety in decision making it is possible to simulate what would happen if a new lifecycle version would be activated.

NX3 calls this feature simulation and it creates a simple Excel Report which lists all business partners and changes of their level.

So it is always transparent which effects the activation of a new lifecycle version would have to your existing business.


From now it is possible to define data protection on field level of NX3 Entities for different actors. Based on criterias like assigned authorities or security groups it is possible to hide fields of NX3 Entities for specific users or security groups. It works similar to the well known specifications which hide complete entities in lists but on field level which is much more granular. Fields are not hidden in UI but the server will protect them and they will not be transferred to the client if user is not allowed to see them.

See below the details of same NX3 Entity. User A is allowed to see all fields but user B is only allowed to see some fields of the entity.

View for user A of NX3 Entity


View for user B of same NX3 Entity

Library updates

  • Several updates for libraries used in NX3

Country specific zipcode validation

Zipcodes have different policies or validation rules based on their countries.

From now NX3 supports this fact and offers country specific zipcode validation. Zipcodes entered by users will be validated based on policies of specific country.


  • Removed Bower as package manager for UI artifacts because support ends in next few month
  • Domain Events as building block for NX3 features
  • Several bugfixes and improvments on server and ui
  • Valuation model changed on server to avoid technical problems

Major Releases for NX3 Core 3.5.0 Is Scheduled for 05-2019

We’re more than proud to inform you that our latest major Release for NX3 Core 3.5.0 is planned for end of 05-2019 – and no, it’s not a joke on the first of april!

Tests are running…

NX3 Core 3.5.0 will bring a lot of enhancements, optimizations and fixes for client and server platform.

Major features to expect are for data privacy enhancements, optimizations for the frontend and security optimizations.

We’ll keep you posted for the final release date!

Major Releases NX3 Core 3.4.0 Is Here!

We’re more than proud to inform you that our latest major Release for NX3 Core 3.4.0 is here!

NX3 Core 3.4.0 will bring a lot of enhancements, optimizations and fixes for client and server platform.








What’s new?

  • Qualification & Verification process is completely new with a set of new features
  • More performance for specific UI elements
  • Clean and more easy dashboard layouts
  • Enhanced detail views
  • Some more


  • Several minor improvements


  • Updates and changes of several libraries



And we’re working on CORE 3.5 which is planned for mid-spring 2019!

Major Releases for NX3 Core 3.4.0 Is Planned for 11-2018

We’re more than proud to inform you that our latest major Release for NX3 Core 3.4.0 is planned for mid of 11-2018.

For now we’re finishing our lasts tests and documentation tasks.

NX3 Core 3.4.0 will bring a lot of enhancements, optimizations and fixes for client and server platform.

The major feature of this release will be the completely reworked Qualification process to generate better and validated information of objects within the NX3 Software.

Take a look at the first screens (for the moment in german language only).

We’ll keep you informed when the release is ready for production!

Major Releases for NX3 Core 3.3.0 Is Now Available

by Main Author

We’re proud to inform you of the availability of the latest major releases of version 3.3.0 for NX3 Core.

NX3 Core 3.3.0 is here with numerous improvements for client and server platform. Here are some of the highlights.


  • OAuth Service Refactoring to NX3
  • Enhanced Document Managemement Support with CMIS
  • New User Task Concept
  • Logging by the Framework
  • Improved Cluster Readiness in Caching and Searching
  • Improved NX3 Cloud with Docker (ELK Stack, Alfresco, Spring Boot Admin)
  • Integrated Online Help


  • Configurable Navigation
  • UI Design Improvments
  • Mapzen Integration
  • Performance Optimizations
  • More Typescript Integration

New Developer Guide

Update for the developer guide for NX3 Core 3.3.0.

Much more

There are much more smaller features and bugfixes in the release which aren’t mentioned here in the blogpost.