bcquality/custom/knowledge/patterns/cmfrt-use-confirmmanagement.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

15 lines
505 B
AL

codeunit 2045750 "CMFRT GD Deletion Handler"
{
procedure CMFRTGDDeletePOI(POICode: Code[20])
var
CMFRTGDPOI: Record "CMFRT GD POI";
ConfirmManagement: Codeunit "Confirm Management";
DeleteConfirmQst: Label 'Delete POI %1?', Comment = '%1 = POI Code';
begin
if not ConfirmManagement.GetResponseOrDefault(StrSubstNo(DeleteConfirmQst, POICode), false) then
exit;
if CMFRTGDPOI.Get(POICode) then
CMFRTGDPOI.Delete(true);
end;
}