Search
Minor enhancements for the Next® admins and specialists, February 2022
It is no secret that the primary target of our enhancements are the business users, or end users, of Next®. Still, providing ease of use, and increased productivity to those who administrate or configure Next® also make great sense.
For this release we have collected the following minor enhancements targeted the admins and specialists:
Enhancement | Issue | |
---|---|---|
Next® Enterprise Single Sign On using OAuth enhanced | ||
When you setup single sign up using OAuth, you now get more flexibility in selecting the user identifier. In addition to UPN, email, and Username from the IdP, you may now use custom attributes. | NEXT-4427 | |
Next® startup is optimized further | NEXT-4407 | |
In our continuous quest to secure that a normal startup of Next® can be completed in less than 15 minutes, we have optimized the process once more. |
||
Next® Servers running SSL and with custom extensions no longer need an extra restart during upgrade | NEXT-4413 | |
When upgrading to our new SSL setup, Next® with customer modules (MAM) needed a an extra restart during the upgrade. To make the upgrade even more seamless, this is no longer the case. | ||
Autocomplete on multi-value fields is made smarter | NEXT-4368 | |
You can now configure that autocomplete should only be done, if a specific controlling field is present and has a value. This allows you to gain more control of the autocompletion that takes place. | ||
Next® Transformation Engine enhanced with configuration | NEXT-4376 | |
The Next® transformation engine is now enabled for docker and kubernetes. Taking this one step further, the transformation engine now gets additional configuration parameters with each service request. | ||
All configuration elements require a description | NEXT-4430 | |
To secure a fully documented setup of Next®, we now require that all configuration elements come with a description text. We also encourage you to use the configuration notes, that are available throughout Next®. | ||
Invoice document data is kept up to date as postings and other details changes | NEXT-4425 | |
Certain header information on an invoice is derived from GL transactions and other details that may be updated during the processing of the invoice. Now Next® keeps this data up to date, so that an external order number or an internal voucher number that is added later, may still be used to locate the invoice. | ||
Next® IO gets to remove password from PDFs | NEXT-4396 | |
If you are so unfortunate to have password protected PDFs in Next®, we can now help you systematically export and re-archive the unprotected PDFs. You provide Next® IO with a list of possible passwords, and leave it to Next® to perform the process. | ||
Email capture with modern security using OAuth now supports also shared inboxes | NEXT-4317 | |
In the October '21 release we moved authentication for our email capture to OAuth. Now this also supports the capture from shared inboxes. | ||
Next® Companion is able to run with very restricted users access | NEXT-4400 | |
Some organizations choose to restrict users access to the Windows command line. Next® Companion no longer needs access to cmd.exe or rundll32.exe to function as designed. | ||
For the techies
This is pretty much technical in it's nature.
Additional information
For additional information , please refer to the online documentation.
Commercial terms and conditions
These new features and enhancements are available at no additional cost, to users with an active service plan. Any consultancy assistance will be invoiced.
Disclaimer
Despite our best efforts, we may be forced to change both content and expected delivery of future product updates without notice.
Details
Title:
Minor enhancements for the Next® admins and specialists
Type:
Enhanced features
Status:
Released
Release time:
February 2022
Affected products:
Next® Bank Statements
Next® Contracts
Next® Emails
Next® Enterprise Archive
Next® ExCustody
Next® Invoices
Next® Mailroom
Next® Processes
Audience:
Admin
Specialist
Classification:
Public
Responsible product manager:
Kim Hellum
Updated:
9.03.2022
By:
Kim Hellum