mirror of
https://github.com/microsoft/BCQuality.git
synced 2026-08-06 09:26:52 +01:00
afb1fa2883
- Introduced guidelines for using the "CMFRT" prefix in object names, fields, and procedures to avoid naming collisions and ensure clarity. - Established rules for object ID ranges to prevent conflicts with other extensions and maintain historical integrity. - Documented best practices and anti-patterns for various coding patterns, including case statements, interface injection, label usage, and validation methods. - Implemented a standards review skill to evaluate AL source changes against CMFRT company standards, ensuring compliance with naming, permissions, and architectural patterns.
14 lines
714 B
AL
14 lines
714 B
AL
// Subscriber calls the implementation codeunit DIRECTLY — bypasses the base
|
|
// table's entry point and all OnBefore/OnAfter integration events.
|
|
codeunit 2045720 "CMFRT BA Sales Subscribers"
|
|
{
|
|
[EventSubscriber(ObjectType::Codeunit, Codeunit::"Sales-Post", 'OnAfterPostSalesDoc', '', false, false)]
|
|
local procedure CMFRTBAOnAfterPostSalesDoc(var SalesHeader: Record "Sales Header")
|
|
var
|
|
SyncImpl: Codeunit "CMFRT BA SyncPostedDoc Impl";
|
|
begin
|
|
// Direct call to implementation codeunit — OnBefore/OnAfter events on the
|
|
// base table never fire, dependent extensions cannot intercept this operation.
|
|
SyncImpl.CMFRTBASyncPostedSalesDoc(SalesHeader."No.");
|
|
end;
|
|
}
|