New Features in ADOIT 17.1
Welcome to ADOIT 17.1, an update to our Long Term Support (LTS) release, ADOIT 17.0.
ADOIT 17.1 introduces the new ADOIT Forms, enabling intuitive and streamlined data capture. In addition to this key feature, the update brings several additional enhancements and includes fixes for issues identified since the release of ADOIT 17.0 LTS.
New Features for All Users
ADOIT Forms: User-Friendly Forms
ADOIT Forms is a new, licensable add-on feature that allows everyone to contribute to the enterprise architecture! Simple forms help you and your colleagues intuitively capture ADOIT data – all without training and workshops.
Capture Objects, Update Data, Evaluate Objects
With ADOIT Forms, the following use cases, for example, can be handled:
As an Architect, I want to easily create forms for ADOIT and assign them to the responsible parties to keep the ADOIT repository complete and up-to-date.
As an Application Owner, I want a simple way to periodically or ad-hoc maintain data for my applications so that I can focus on my core tasks.
As an Expert/Employee, I want to report new required technologies with minimal effort so that they can be promptly reviewed by the responsible party for further use.
As a template designer, you can design new forms and send them to your colleagues without any programming knowledge. Once a form is completed, the data is transmitted to ADOIT via a REST interface and automatically evaluated there. This lowers the barriers to contributing to the enterprise architecture, making collaboration easier and more efficient.
Curious? Visit our Enterprise Architecture Management Blog to find out more about ADOIT Forms!
Workspaces: Simpler Permissions, Better Access
In ADOIT 17.1, we’ve reverted the changes introduced in ADOIT 17.0 that made workspaces accessible as objects in the Explorer across various scenarios. This implementation fell short of our vision to enhance workspace visibility and simplify permissions management.
With ADOIT 17.1, workspaces are back to being exclusively accessible within the "Workspaces" scenario. Behind the scenes, we’ve implemented key improvements to ensure seamless access: workspace members now retain their permissions even if their access to the main object group is restricted. This resolves the issues that prompted the original change and and simplifies your work at the same time.
Removed Features
This section lists features that have been removed from ADOIT 17.1.
Settings for Workspaces
As workspaces in ADOIT 17.1 are no longer accessible as objects in the Explorer, administrators can no longer define a default object group for newly created workspaces. The corresponding settings have been removed from the ADOIT Administration.
Migration from an Earlier Version of ADOIT to ADOIT 17.1
Changes to Software Requirements
Please note the following changes to the software requirements for running ADOIT when migrating from previous versions.
No longer supported:
Tomcat 8 and Tomcat 9
Java 8 and Java 11
Added support for:
Tomcat 10.1
Java 17
Upgrade ADOIT
The Installation Manual contains a number of migration guides that will help you upgrade ADOIT from an older version to version 17.0. Each guide contains all the steps that need to be taken, with everything explained in detail:
Migration from ADOIT 14.0 or Earlier to ADOIT 17.0 (ArchiMate Library)
If you are using ADOIT 14.0 or earlier with the ArchiMate Application Library, please contact your ADOIT consultant for assistance with the required steps.
Switch from Standard Library to ArchiMate Library
With ADOIT 16.0, the ADOIT Standard Application Library has been discontinued and is no longer supported. Are you using ADOIT 15.0/15.1 or earlier with the ADOIT Standard Application Library? To upgrade to ADOIT 17.1, you need to switch to the ArchiMate Application Library. Please contact your ADOIT consultant for assistance with the migration.
Install Hotfix
You are already using ADOIT 17.1 and want to install a hotfix? Here are step-by-step instructions: