Minor enhancements for the Next® admins and specialists, August 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 makes great sense.
For this release we have collected the following minor enhancements targeted the admins and specialists:
|REST API optimized to retrieve business log||NEXT-4716|
|With compliance becoming more vital by the day, we are happy to deliver optimized sorting and filtering for our REST API to be used when you retrieve business log entries. This allows you to document what ever has happened over time with each of your documents. When was it created, who has modified it. Who changed the confidentiality. And if you have in place, you can even report who has ever seen the document. This kind of documentation is especially helpful for companies under FDA approval, but also for others with a unified logging mechanism in place. If you do not have Security information and event management (SIEM) system in place, Power BI or Excel will do the job.|
|Automatic number series||NEXT-4657|
|Next® has always had a built in number generator for contract numbers. Custom projects in need of a unified ID have had to find their own solution. With this release, we have extended Next® with a built in Automatic number series management. This allows you to setup you own number series, with or without prefix and suffix. This makes it easier to build and maintain solutions going forward.|
|REST API for table data gets API Keys||NEXT-4751|
|The relatively new API for adding and updating table data in Next® now gets API keys as an alternative security mechanism. This makes it easier to update system data with a service user.|
|UI Integration made easer||NEXT-4710|
|When you integrate using URL links to predefined Search forms, you can now provide values for search criteria that are hidden from the end user. Maybe you would like an integrated search to display only active contracts, but the flag Active/Inactive should not be editable or even visible for the user. Previously such hidden parameters would be ignored, but not longer. This makes it easier to make advanced integration from other systems.|
|Point and click setup of list views||NEXT-4726|
|When you setup a List view (of documents or tasks), you no longer need to know the name of the fields you wish to add as a column. Type ahead and validation, makes it much easier and more secure to setup list views. No more remembering, no more copy/paste, and no more misspellings.|
|Not all field names are self explanatory. Being able to see the actual field type when you select it for a column in a Dataview makes it easier to select the right one. At the same time we have added the Copy, Export, and Import actions to the Dataviews setup in the Admin panel. Makes it easier to handle multiple environments for QA and production.||NEXT-4728|
|Next® Invoices Entry types can now be exported and imported||NEXT-4727|
To make initial implementation and ongoing maintenance easier, we have added Copy, Export, and Import actions to Entry types in the Next® admin panel. When you need to move new definitions from Q&A to Production, it is so much easier if you have Export/Import available.
|Match status in Next® Invoices for ASPECT4 is optimized||NEXT-4739|
|Unnecessary updates of Next® with match status from ASPECT4 has been eliminated.|
|Assignment policies in Next® Invoices automatically sets appropriate owner||NEXT-4698|
|When you use Automatic assignment policies to select your invoice approvers, Next® now automatically sets any assigned approver as a potential owner of the task. This takes some of the complexity out of using the assignment policies, and reduces the risk of making setups the behave unexpectedly.|
|More resilient handling of multi value fields||NEXT-4722|
|No matter if you add documents with multi value fields using REST or Document Capture, Next® now enforces the definitions from the item type. A first add with a single value, no longer defines the item as having a single value field.||NEXT-4721|
|External data on folders moved to template||NEXT-4747|
|In order to avoid confusion, the setup of access to external data services from a folder, has been moved to the Folder template setup|
|LDAP synchronization made more resilient to faulty user data||NEXT-4759|
|A defect or incomplete user record is no longer permitted to prevent the synchronization of other user data.|
|Next® Companion gets configurable temp folder||NEXT-4735|
|In order to cater for users with very restricted working disk space, you may now configure the path for the working files.|
|Next® Companion updated to .NET 6.0||NEXT-4736|
|As a part of our ongoing task to keep Next® up-to-date and secure, the Next® Companion has been upgraded from .NET 5.0 to .NET 6.0.|
|Fact types for rules are moved to system level||NEXT-4676|
|As we are beginning to use our rules based logic outside Next® Mailroom, we have moved the definition from archive level to system level. Fist implementation is our Next® Mailroom Lite - AKA Scan to Next® but many more - including conditional watermarks - are to come.|
For the techies
This is pretty much technical in it's nature.
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.
Despite our best efforts, we may be forced to change both content and expected delivery of future product updates without notice.
Minor enhancements for the Next® admins and specialists
Next® Bank Statements
Next® Enterprise Archive
Responsible product manager: