bcquality/custom/knowledge/naming/cmfrt-naming-prefix.good.al
BeytullahCengiz88 c72c0ad685 Add CMFRT coding standards documentation and examples
- Introduced guidelines for "one codeunit one global function" architecture to enforce single responsibility in AL code.
- Added best practices and anti-patterns for adding parameters via overloads to maintain backward compatibility.
- Documented the importance of never deleting members in AL and always marking them as obsolete.
- Established the requirement for OnBefore and OnAfter integration events for global procedures to enhance extensibility.
- Defined naming conventions for CMFRT objects, including prefixes and object ID ranges to avoid conflicts.
- Implemented patterns for case statements to ensure all cases are handled, including the necessity of an else clause.
- Introduced the interface injection pattern to allow pluggable operations in table-level code.
- Recommended using Confirm Management for user confirmations to improve testability.
- Established a three-permission set pattern for security to ensure proper access control.
- Created a review skill for CMFRT AL standards to automate compliance checks against established guidelines.
2026-07-02 13:12:09 +00:00

29 lines
682 B
AL

// Objects use "CMFRT <ABBR> <Name>" with spaces.
pageextension 2045661 "CMFRT GD Job" extends "Job Card"
{
}
// Fields use "CMFRT <ABBR> <FieldName>" with spaces.
tableextension 2045660 "CMFRT GD Job Ext" extends Job
{
fields
{
field(2045081; "CMFRT GD POI ID"; Guid)
{
DataClassification = CustomerContent;
Caption = 'POI ID';
}
}
}
// Procedures use CMFRT<ABBR><ProcedureName> — concatenated, no spaces.
codeunit 2045700 "CMFRT GD Job Mgmt"
{
procedure CMFRTGDLinkJobToPOI(JobNo: Code[20]; POIId: Guid)
begin
end;
local procedure CMFRTGDValidatePOIExists(POIId: Guid): Boolean
begin
end;
}