As you might know we work hard on the next major update for NX3.
While we already migrated to new components and included tons of new features we’re not ready, yet.
So – in short words – we have no fixed date for the next release but we think this will be in early spring!
With the update for the next CORE Release we will re-work the roadmap for 2021/2022.
Stay healthy – we’ll keep you posted!
More than happy to share the release of NX3 Core 3.8.0 with you!
This release features the following improvements:
“PostgreSQL: The World’s Most Advanced Open Source Relational Database.
PostgreSQL is a powerful, open source object-relational database system with over 30 years of active development that has earned it a strong reputation for reliability, feature robustness, and performance.” [https://www.postgresql.org/]
During the last months we have made the experience that many of our new customers already use PostgresSQL in their existing system landscape. Existing customers are also thinking about a migration to PostgreSQL to save high license costs.
Based on this feedback, the NX3 team has been working on basic supporting PostgreSQL as a database in addition to Oracle and MySql or Maria DB. Within the next releases we will work on further optimizations for full supporting PostgreSQL.
NX3 stores our customers’ documents where they need them. Up to now, a CMIS interface was available for integration into the existing system landscape. Furthermore the possibility to store the documents on the filesystem exists.
With this release, two further storage options have been added to enable the storage of documents in the cloud and expand support of integration into existing system landscapes.
“Amazon Simple Storage Service (Amazon S3) is an object storage service that provides industry-leading scalability, data availability, security and performance” [https://aws.amazon.com/de/s3/] .
When hosting NX3 on AWS, AWS S3 offers the possibility to use a service that ensures the permanent availability of your data. AWS S3 offers an availability of 99,999999999 percent1 . Therefore the data are transmitted over at least three different availability zones are redundantly stored. This means that no more data is lost.
WebDAV (Web-based Distributed Authoring and Versioning) is a network protocol for delivering files over the Internet.
In addition to CMIS, WebDAV offers a further possibility for easy integration into existing document management systems of our customers.
Furthermore, WebDAV offers the possibility to use cloud services that support this protocol.
1 This information was provided by AWS. See https://aws.amazon.com/de/s3/faqs/#Durability_.26_Data_Protection for details.
On a fast track this time – CORE 3.8 is scheduled for 09-2020! This release will bring major improvements for our technical platform!
Stay tuned!
We are happy to share the release of NX3 Core 3.7.0 with you!
This release features the following improvements:
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.
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.
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 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:
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.
We are on the final way for NX3 3.7 which will bring a huge amont of changes for client and platform.
We’ll keep you posted for the final release date!
We’re more than proud to inform you that our latest major Release for NX3 Core 3.6.0 is HERE!
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!
We’re more than proud to inform you that our latest major Release for NX3 Core 3.5.0 is HERE!
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.
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.
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 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.
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
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.
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!
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.
Thanks!
And we’re working on CORE 3.5 which is planned for mid-spring 2019!