Skip to content

[E-Documents Core] - Events for attaching E-Documents when using Digital Vouchers#7006

Open
GMatuleviciute wants to merge 4 commits intomicrosoft:mainfrom
GMatuleviciute:dev/aan/digitalvoucher
Open

[E-Documents Core] - Events for attaching E-Documents when using Digital Vouchers#7006
GMatuleviciute wants to merge 4 commits intomicrosoft:mainfrom
GMatuleviciute:dev/aan/digitalvoucher

Conversation

@GMatuleviciute
Copy link
Contributor

@GMatuleviciute GMatuleviciute commented Mar 5, 2026

This pull request does not have a related issue as it's part of the delivery for development agreed directly with @altotovi @Groenbech96

Implementation

These integration events are required for the Enforced Digital Vouchers app to subscribe to E-Document processing and attach digital voucher records at the correct points in the document lifecycle.

Events added

OnExportEDocumentAfterCreateEDocument in EDocExport.Codeunit.al — Raised after the e-document content has been generated and the success status determined, but before the service status is logged. This placement allows the Digital Vouchers subscriber to access the finalized document blob (TempBlob) and the mapped source document records, which are needed to create and associate a digital voucher with the exported e-document.

OnAfterUpdateToPostedPurchaseEDocument in EDocumentSubscribers.Codeunit.al — Raised after a received purchase e-document is updated to its posted state (document record ID, document number, type, and status are all set). This placement allows the Digital Vouchers subscriber to link the digital voucher to the final posted purchase document, since the posted document number and record ID are only available at this point.

Important

This Pull request related with microsoft/ALAppExtensions#29793

Fixes #

AndriusAndrulevicius and others added 3 commits February 24, 2026 11:23
Introduces new integration events to enable external handlers after creating an exported e-document and after updating a posted purchase e-document.
Enhances extensibility for partners and custom solutions by allowing additional logic to be executed at these key points.
@GMatuleviciute GMatuleviciute requested a review from a team as a code owner March 5, 2026 08:01
@github-actions github-actions bot added AL: Apps (W1) Add-on apps for W1 From Fork Pull request is coming from a fork labels Mar 5, 2026
@github-actions
Copy link

github-actions bot commented Mar 5, 2026

Could not find linked issues in the pull request description. Please make sure the pull request description contains a line that contains 'Fixes #' followed by the issue number being fixed. Use that pattern for every issue you want to link.

Adjusts the timing of the post-creation event to ensure it is called after the document and service statuses have been updated.
This change helps external handlers to access the latest status information, improving reliability for event subscribers.
@github-actions
Copy link

⚠️ Stale Status Check Deleted

The Pull Request Build workflow run for this PR was older than 72 hours and has been deleted.

📋 Why was it deleted?

Status checks that are too old may no longer reflect the current state of the target branch. To ensure this PR is validated against the latest code and passes up-to-date checks, a fresh build is required.


🔄 How to trigger a new status check:

  1. 📤 Push a new commit to the PR branch, or
  2. 🔁 Close and reopen the PR

This will automatically trigger a new Pull Request Build workflow run.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

AL: Apps (W1) Add-on apps for W1 From Fork Pull request is coming from a fork Integration GitHub request for Integration area

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants