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.
29 lines
682 B
AL
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;
|
|
}
|