Updated documentation to clearly state that parallel operation and conversion functions are in early alpha. These features are currently limited to selected testers and the Extension Pack remains in preview.
Updated pages:
]]>Added documentation for the new Liquibase 4 integration extension, enabling command execution within Visual Studio Code. Included details on the Extension Pack's current capabilities for YAML projects and feedback channels for development status.
Updated pages:
Added a warning regarding the 20 MB request body limit and 120-second timeout for speech-to-text operations. Guidance is provided on splitting long recordings or adjusting encoding to meet these constraints.
Updated pages:
Updated documentation to specify a 120-second request timeout and a 20 MB maximum request size across all AI models. These platform-wide limits apply regardless of model type. Users are advised to split large tasks or reduce input length to avoid timeouts caused by complex requests.
Updated pages:
Added documentation for the new URL and Filter Decoder feature in beta. This tool helps users decode ADITO URLs containing Base64-encoded filters, displaying them as readable JSON objects. It supports both full URLs and encoded filter strings to simplify troubleshooting and analysis.
Updated pages:
]]>Published details for the ADITO Code Preview extension, which allows developers to navigate YAML references directly within VS Code. The tool enables viewing file contents via hover previews and editing artifacts in-place using the Peek editor without leaving the current file.
Updated pages:
]]>Introduces the ADITO system database used for internal configuration and runtime data. It defines ASYS tables as internal-only components that must not be accessed directly. Users are instructed to use JDito API methods instead of direct table queries to ensure platform stability.
Updated pages:
]]>Adds documentation for the new ADITO Code Completion extension, which provides schema-aware assistance for YAML files and JDito processes. The guide covers installation, variable suggestions, and troubleshooting steps like restarting the TypeScript server.
Updated pages:
]]>Corrects version compatibility information by updating the supported range for Manager Customizing from 1.4.1 to 1.4.1 - 1.5.0 across multiple ADITO versions. This ensures accurate dependency mapping for upgrades and deployments.
Updated pages:
Corrected the Cloud-Manager customizing version for ADITO 2024.2.x from 1.4.0 to 1.4.1 in the versions and dependencies table to ensure accurate configuration alignment.
Updated pages:
Learn how to configure Visual Studio Code Copilot Chat to use the self-hosted adito-code model from the ADITO AI Runtime for enhanced code generation capabilities.
Updated pages:
]]>Simplified the versions overview table by removing obsolete service columns and clarifying the structure. The updated view focuses on core components like SolR, Zookeeper, and Cloud-Manager for better readability.
Updated pages:
Understand how RecordContainers minimize data retrieval by loading only necessary fields. This guide explains using field hints in JDitoRecordContainers to skip expensive processing and improve application performance.
Updated pages:
Updated anchor links within the entity model documentation to ensure accurate navigation between sections on accessing field values and implementing JDitoRecordContainer operations.
Updated pages:
Updated documentation to include Visual Studio Code Copilot Chat alongside OpenCode, Claude Code, and Codex. This guide explains how to configure these tools to use the self-hosted adito-code model, ensuring all code requests remain within your ADITO Cloud infrastructure in Germany for data sover...
Updated pages:
Updated the Error Code Lookup documentation to clarify that the available lookup data is based on the latest ADITO version. This ensures users understand which version of the system their error codes correspond to when troubleshooting.
Updated pages:
Consolidated and clarified the Entra configuration requirements for the Graph Mailserver and Mail Repository. The update details necessary Microsoft Graph permissions, specifically highlighting that 'Mail.ReadWrite' is required because the Mailbridge updates message flags during processing.
Updated pages:
]]>The legacy jditoScriptManagerNext preference has been removed. ScriptManagerNext is now the only option and has been the default for years. Existing preferences are automatically cleaned up upon opening projects in the new version.
Updated pages:
]]>Refreshed reference documentation for the API and Data Models sections. This update includes regenerated files to ensure accuracy with the latest platform changes and fixes broken links.
Updated pages:
Added default request parameters for adito-code, clarified its distinction from text-generation models, and included a new guide for building Retrieval-Augmented Generation (RAG) use cases.
Updated pages:
Updated xRM release notes to clarify module requirements, dependency versions, and functionality descriptions. Includes critical updates on email notifications, user creation scripts, and refactored search utilities.
Updated pages:
]]>Corrected markdown syntax to ensure figure captions display on a new line for better readability in the documentation.
Updated pages:
Version 2026.4.2 introduces breaking changes across xRM, AI, and Contact Management modules. Key updates include removing specific mail preferences, replacing calendar permission tools, and refactoring organization utility functions.
Updated pages:
]]>Clarified that parallel operations are experimental and intended for development only. Added warnings about potential file overwrites when transferring back to AOD and emphasized creating backups before conversion.
Updated pages:
Updated upgrade guide details for neonRowRecalculationMode. Field values are now reset before each row during data retrieval calls, with performance improvements made to redundant process executions independent of this setting.
Updated pages:
]]>Updated documentation to confirm support for Debian-based Linux systems like Ubuntu alongside Windows. Clarified that other distributions and macOS are currently unsupported.
Updated pages:
The Converter tool is now available on Windows and Debian-based Linux distributions like Ubuntu. It transforms projects into YAML structures in VS Code, though dependencies must be installed manually afterward.
Updated pages:
Added a comprehensive step-by-step guide for implementing JDitoRecordContainer. Includes database setup, context creation, view configuration, and code examples for content processing, insertions, updates, and deletions. Highlights the flexibility of data sources while noting that sorting, paging...
Updated pages:
]]>Updated version numbers for PDF-Preview, Content Analysis, and Text Analysis services to reflect optimized Docker images. While using newer versions is recommended for performance, it is not strictly required for compatibility.
Updated pages:
]]>Documented an issue where the Designer inconsistently resolves project-level model overrides. This can cause the UI to display incomplete models, use module-owned versions instead of project overrides, or sporadically show duplicate occurrences in the project tree.
Updated pages:
]]>Updated the description of known conversion issues when opening an AOD project. Clarified that views are placed without context because the converter cannot determine the original data model when the nodemodules directory is excluded.
Updated pages:
]]>Added documentation explaining a known issue where views created in AOD and assigned to a module's context data model end up in an incorrect path during AOD-to-YAML conversion. This occurs because the view reference points to the context while the view itself is treated as a separate data model d...
Updated pages:
]]>Introduced a new Development section in the main navigation. It groups technical reference documentation and interactive tools, including Viewtemplates and Layouts, Data Model API, JDito API, Dev Tools, and xRM Customization resources.
Updated pages:
The Dev Tools section has been reorganized for better navigation. The Error Code Lookup tool now supports resolving internal ADITO error codes using full codes, ID pairs, or log excerpts containing multiple codes.
Updated pages:
Updated guidance to emphasize addressing dependent Consumers by their specific ID during PATCH requests. This prevents attribute mixing and accidental overwrites of existing records.
Updated pages:
Component documentation images have been updated with clearer filenames and descriptions. Terminology for dropdowns, lookup fields, and multi-edit components has been refined for consistency across the guidelines.
Updated pages:
Explains the distinction between READ and VIEW permissions. READ controls data access, while VIEW controls element visibility. Tabs disappear only if contained content is hidden due to denied VIEW permissions, not merely lack of READ access.
Updated pages:
Updates configuration to use ANTHROPICAUTHTOKEN instead of ANTHROPICAPIKEY. This prevents authentication conflicts with personal Claude Code logins and skips the initial confirmation prompt, ensuring reliable connection to ADITO AI Runtime.
Updated pages:
]]>Introduces the adito-code model for data sovereignty. Guides users on configuring OpenCode, Claude Code, and Codex to route requests through ADITO Cloud infrastructure in Germany, keeping source code within your environment.
Updated pages:
Converted documentation images to the modern WebP format for better performance and fixed broken navigation anchors. These changes ensure faster page loading and reliable access to specific sections like Git naming conventions.
Updated pages:
Replaced all PNG screenshots in Viewtemplates documentation with optimized WebP files. This update improves load times across guides for charts, tables, and other UI components without changing visual content.
Updated pages:
Restructured the Designer troubleshooting guide to clearly define when to use the Known Issues page. Added detailed descriptions for specific issues like missing models in project overrides and tunnel address conflicts.
Updated pages:
ADITO model elements now support a documentation property to store technical or functional explanations directly on the model. Written in AsciiDoc format, this helps clarify purpose and behavior for complex entities like Entities, Fields, and Parameters.
Updated pages:
Avoid reserved words for identifiers to ensure portability. Use prepared statements for SQL safety and qualify column names with table names to prevent ambiguity. Guidelines also cover DATETIME vs TIMESTAMP usage and storing booleans as TINYINT.
Updated pages:
Starting with version 2025.0, specific field types used in Global Search may hit Solr's maxBooleanClauses limit due to term expansion. This update provides warnings and recommends alternative field types like TEXTNOSTOPWORDS or COMMUNICATION to resolve search issues.
Updated pages:
Removed references to the product roadmap and clarified that ADITO does not yet ship a dedicated agent framework. Users can now build basic agent loops in JDito using function calling and process execution without relying on future roadmap features.
Updated pages:
]]>Added a comprehensive guide on constructing AI agent loops in JDito today. The documentation explains how to combine the chat completions endpoint with tool use and process execution to enable models to decide and execute actions automatically.
Updated pages:
]]>