This release adds the Markdown Editor, manual code support in AI Agents, database-side primary keys, retryable transactions, and local GenioWeb integration with GenioHub. UI improvements include global list creation, dynamic confirmations, and better breadcrumb contrast. Several bug fixes improve filters, table navigation, image downloads, and translations.
Multiline text fields can now use the Markdown Editor, providing a safer, more user-friendly alternative to raw HTML fields and a full-featured replacement for the current HTML editor. The editor now supports multiple view modes: Editor, Editor & Preview, Preview, and Full Screen. Additional features can be enabled per field, including custom attributes, image support, and typographic replacements, giving full control over Markdown-to-HTML behavior. This update simplifies editing, improves content previewing, and ensures consistency across Markdown content.
AI Agents can now run manual code for complex workflows without redoing full logic. Use cases include writing multiple records, redirecting to specialized UI, and running advanced routines.
Primary keys can now be generated directly on the database side for "Guid", "Int", and "Varchar" columns, removing the need for manual sequence tables or round-trips. Supported on SQL Server and Postgres, "Int" and "Varchar" use database sequences, while "Guids" use newid(). Inserts that omit the PK column will use the default, and the OUTPUT clause can retrieve the generated key.
"Int" keys benefit most, "Varchars" are supported but should be deprecated, and "Guids" are unaffected. Primary keys are now available only after persistence, and generatePrimaryKey requires the column name. After enabling or disabling the option, reindex the database with /zero to reinitialize sequences.
The option in WebAdmin helps manage this transition and will be removed once all code is compatible with database-side keys.
Queries can now be retried automatically on transient failures like network issues, deadlocks, or temporary slowness. Previously, errors were returned immediately, requiring manual recovery.
Retryable processes must be idempotent and are intended for critical routines. Developers should separate routines into setup, execution, and return, with only the execution part retried. Long processes should be split into smaller batches to avoid repeating extensive operations.
GenioWeb can now be deployed locally and integrated with GenioHub, enabling distributed architecture and centralized governance. Departments can manage their own Genio versions independently while maintaining a central entry point through GenioHub. Code generation runs locally, reducing overhead on the central server and improving scalability. Authentication between GenioHub and local GenioWeb instances is handled via Azure OpenID, enabling secure Single Sign-On across different domains. Version control, license management, and user credential governance remain centralized through GenioHub, ensuring consistency and control across all environments.