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.
13 lines
462 B
AL
13 lines
462 B
AL
// Two global procedures in one codeunit — mixed concerns, impossible to
|
|
// apply interface injection independently to each operation.
|
|
codeunit 2045710 "CMFRT BA Price Utilities"
|
|
{
|
|
procedure CMFRTBACreateSalesPrice(ItemNo: Code[20]; UnitPrice: Decimal)
|
|
begin
|
|
end;
|
|
|
|
// Second global entry point belongs in its own codeunit with its own interface.
|
|
procedure CMFRTBADeleteExpiredPrices(ItemNo: Code[20]; CutoffDate: Date)
|
|
begin
|
|
end;
|
|
}
|