[Justas Zaksauskas (jzaksauskas)]

Original PR: microsoft/ALAppExtensions#29793 (closed due to migration)
This pull request does not have a related issue as it's part of the delivery for development agreed directly with Aleksandar Totovic (@altotovi) Magnus Hartvig Grønbech (@Groenbech96) ventselartur

Implementation

With this update enhanced automation for Digital Vouchers in sales and purchase document posting. When enabled, the system will automatically generate and attach E-Documents and related files to posted documents, streamlining document management and compliance.

Functional Changes

1. New Check Type Option

• The Check Type field in the Digital Voucher Entry Setup table has been extended to include a new option: E-Document.
• E-Document option is only valid when the Entry Type is set to Sales Document or Purchase Document.
• The E-Document check type can only be selected when Generate Automatically is set to TRUE.

2. Automated Document Attachment on Posting

When posting sales or purchase documents, if setup is set to use E-Documents the system will attach related E-Document files to the Incoming Document Files of the posted sales/purchase document.

Impact

Reduces manual effort in attaching compliance documents.
Ensures all relevant files are consistently linked to posted documents.

Important

This Pull request related with #7006

Fixes #

Fixes AB#639562

[github-actions]

Copilot PR Review

Iteration 1 · Outcome: completed

Knowledge source: https://github.com/microsoft/BCQuality@822cae1b2771ac25f665f73369f69093bd4fd630

Findings by domain

Findings split into Knowledge-backed (cite a BCQuality article) and Agent (the agent's own judgement, no matching BCQuality rule).

Domain	Findings	Knowledge-backed	Agent	Inline	Fallback
Style	2	2	0	2	0

Totals: 2 knowledge-backed · 0 agent findings.

Orchestrator pre-filter (13 file(s) excluded)

• layer-disabled (knowledge) : 13 file(s)

_{Findings produced by the Copilot CLI agent against BCQuality at 822cae1b2771ac25f665f73369f69093bd4fd630. Reply 👎 on any inline comment to flag false positives.}

[github-actions]

$\textbf{🟡\ Medium\ Severity\ —\ Data\ Modeling}$

The new E-Document invariant on Digital Voucher Entry Setup is enforced only when 'Check Type' or 'Generate Automatically' is validated. A user can still change an existing setup row's 'Entry Type' from Purchase/Sales Document to a journal entry type while 'Check Type' stays E-Document, leaving the row in an unsupported combination. That stores inconsistent setup data, and later journal posting will silently bypass the intended E-Document check because codeunit "Voucher E-Document Check" exits early for non-purchase entry types. Revalidate or clear the E-Document-specific fields when 'Entry Type' changes.

Line mapping was unavailable, so this was posted as an issue comment.

_{👍 useful · ❤️ especially valuable · 👎 wrong - reply with why · AL review agent v1.26.4}

[github-actions]

$\textbf{🟡\ Medium\ Severity\ —\ Style}$

Seven new Labels are declared inside procedure-local var blocks instead of each object's top-level var section: DigitalVoucherEntrySetup.Table.al (CheckTypeEDocErr, GenerateAutoMustBeEnabledErr), DigitalVoucherImpl.Codeunit.al (FileNameTok, EDocumentFileNameLbl), VoucherEDocumentCheck.Codeunit.al (NotPossibleToPostWithoutEDocumentErr), and EDocAttachmentTests.Codeunit.al (GenerateAutomaticallyErrorTok, NoIncomingDocumentTxt). BCQuality treats procedure-scoped Labels as fragile for XLIFF extraction and localization review; move these Labels to object scope and keep only references in the procedures.

Knowledge:

• microsoft/knowledge/style/labels-declared-at-object-scope.md

Line mapping was unavailable, so this was posted as an issue comment.

_{👍 useful · ❤️ especially valuable · 👎 wrong - reply with why · AL review agent v1.31.4}