- Next® release
- January 2022 - release
- June 2022 - release
- Already released
- December 2021 - release
- November 2021 - release
- October 2021 - release
- August 2021 - release
- July 2021 - release
- June 2021 - release
- May 2021 - release
- March 2021 - release
- February 2021 - release
- January 2021 - release
- December 2020 - release
- November 2020 - release
- October 2020 - release
- August 2020 - release
- July 2020 - release
- June 2020 - release
- May 2020 - release
- April 2020 - release
- February 2020 - release
- January 2020 - release
- December 2019 - release
- Not yet allocated
- Terms and phrases
- Next® release
Global Metadata Repository in Next®
Next® implementations come in many sizes, from an entry level Next® Contracts with only 5 different document types, to a massive Next® Enterprise Archive, with 1.000+ document types.
To cater better for both, we now introduce the concept of a Global Metadata Repository. A single unified catalog, where every piece of data related to documents and processes is described globally, once and for all.
Until now, every single document type related to customers had its own definition of a 'Customer Number'. Hopefully definitions that were similar, but with no way to guarantee just that. Now, 'Customer Number' is defined and described once - in the Global Metadata Repository, and simply selected whenever you define a new document type.
The Global Metadata Repository is a major step towards increased standardization
This new feature will save you a lot of time in setting up Next®, and will allow us to distribute even more best practice setups.
The Global Metadata Repository will be extended to define also complex metadata:
- A complete address
- A complete General Ledger Posting
Also with a later release, Next® will distinguish between
- Next® Standard Metadata
- Customizable Next® Standard Metadata
- Custom Metadata.
This allows us to add new features more easily to established Next® setups. A nice to have feature when you run Next® by your self, and a must have for our Next® as a Service offering.
You will also see a clean up in the terminology used:
- String becomes Text
- Decimal and Long and becomes 'Number
- Scale becomes Decimals
- Description becomes Label
- An additional Short label is added for list headers.
- An optional translation key for both of the above will allow Next® to automatically display labels and headers in the users language
- A new Description text area is added to provide a detailed description, in addition to the generic configuration hints coming to all elements.
- A new multi value Scope, allows us to group fields Next® Contracts, Supplier, etc.
At the same time you will be able to subset your list of field definitions on most of the above criteria.
Finally, we intend to be able to define standard list and validation services already in the Metadata Repository, making it even easier to setup new features and documents in Next®.
For the techies
When the initial version (May'21) is installed, Next® will automatically create new definitions to match the current item type setup. We encourage you to clean up your metadata definitions. Good metadata hygiene pays off in the long run.
Commercial terms and conditions
This new feature is 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.
Global Metadata repository in Next®
Next® Bank Statements
Next® Enterprise Archive
Responsible product manager: