Release Date: 04 May 2026
Release Summary
- A new dynamic field picker has been added to the email template editor, allowing users to insert merge fields via a
{triggered dropdown or a side panel — eliminating manual typing of placeholders. - All public AL procedures have been documented with XML doc comments, improving developer onboarding and code clarity.
- AL keywords have been normalised from UPPERCASE to PascalCase throughout the codebase, bringing the app in line with Microsoft's AL coding standard.
New Feature
E-mail Templates
Dynamic Email Fields — Enhanced Template Editor with Field Picker.+
Writing email templates just got a lot easier. Previously, inserting dynamic field placeholders like {Document.No.} or {Customer.Name} required typing them manually, which was error-prone and hard to discover.
The email template editor now includes two ways to insert dynamic fields:
{triggered dropdown — Type{anywhere in the email body to open a searchable, grouped dropdown listing all available fields from the relevant tables (Document, Customer/Vendor, Company, Signature). Navigate with the keyboard or search by name.- Field picker side panel — A persistent panel on the right side of the editor shows all available fields in collapsible groups. Search and double-click to insert a field at the cursor position.
The subject line has also been moved inside the editor control, giving it the same { triggered dropdown behaviour and avoiding layout limitations that previously prevented dropdowns from working in a separate field.
Available fields are resolved dynamically based on the department type (Sales, Purchase, or Warehouse), so only relevant fields are shown for each template context.
📖 How-to guide: Write an HTML email body using dynamic email fields and the field picker
Refactors
General
Document all public procedures with XML doc comments.+
All public procedures and methods across the codebase have been documented with XML doc comments. Each procedure now includes a <summary> description, <param> entries for its parameters, and a <returns> tag where applicable.
This makes the code self-documenting: developers get meaningful hover information in IntelliSense, onboarding new team members is faster, and automated code review tools can give more relevant feedback. The change has no impact on app behaviour at runtime.
Normalise UPPERCASE AL keywords to PascalCase.+
All AL keywords throughout the codebase have been normalised from legacy UPPERCASE style (e.g. IF, BEGIN, END, SETRANGE) to the PascalCase standard prescribed by Microsoft's AL style guide (e.g. if, begin, end, SetRange).
This is a cosmetic change only — AL is case-insensitive, so there is no impact on runtime behaviour. The normalisation eliminates mixed-casing noise in code reviews and ensures the app fully complies with the Abakion AL Coding Standard going forward.